<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Javascript on </title>
    <link>https://anashamidi.com/tags/javascript/</link>
    <description>Recent content in Javascript on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 10 Jan 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://anashamidi.com/tags/javascript/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Bugs &amp; JS: A Closer Look at JavaScript for Successful Bug Hunting</title>
      <link>https://anashamidi.com/posts/javascript-for-bug-hunting/</link>
      <pubDate>Wed, 10 Jan 2024 00:00:00 +0000</pubDate>
      <guid>https://anashamidi.com/posts/javascript-for-bug-hunting/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Good Day!&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Remember when I first started bug hunting? I used to think looking into JS files was unnecessary — would I really find bugs in files everyone can see? But after some reading, I realized I was missing out on a lot. So I want to share some resources, tools, tutorials, and other ways to dig deeper into JavaScript analysis.&lt;/p&gt;&#xA;&lt;h2 id=&#34;resources-and-tools&#34;&gt;Resources and Tools&lt;/h2&gt;&#xA;&lt;p&gt;Diving into JS files can be very rewarding. It lets you uncover hidden functionality, credentials, API keys, paths, and more — especially valuable for finding client-side vulnerabilities like XSS.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
