<?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 T3rminat0r on Medium]]></title>
        <description><![CDATA[Stories by T3rminat0r on Medium]]></description>
        <link>https://medium.com/@T3rmint0r_01?source=rss-4f8df3eca4c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vqGbRMssxXVnfyjBj5qeaQ.jpeg</url>
            <title>Stories by T3rminat0r on Medium</title>
            <link>https://medium.com/@T3rmint0r_01?source=rss-4f8df3eca4c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:02:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@T3rmint0r_01/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[The Biggest Reason Beginners Don’t Find Bugs Has Nothing to Do with Bug Hunting]]></title>
            <link>https://medium.com/@T3rmint0r_01/the-biggest-reason-beginners-dont-find-bugs-has-nothing-to-do-with-bug-hunting-f0e7abd55dc7?source=rss-4f8df3eca4c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0e7abd55dc7</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[T3rminat0r]]></dc:creator>
            <pubDate>Sat, 25 Jul 2026 16:56:40 GMT</pubDate>
            <atom:updated>2026-07-25T16:56:40.347Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k_bEu6E7I57FafRuPUb5Aw.png" /></figure><p>When I started learning bug hunting, I thought the hardest part would be finding vulnerabilities.</p><p>After spending the last few months practicing, making mistakes, and learning from them, I realized I was asking the wrong question.</p><p>Instead of asking:</p><blockquote><strong><em>“Why am I not finding bugs?</em></strong></blockquote><p>I should have been asking:</p><blockquote><strong><em>“Do I really understand this application?”</em></strong></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F17900380376959797190&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fnahdog-gif-17900380376959797190&amp;image=https%3A%2F%2Fmedia.tenor.com%2F-GrtHNEPx8YAAAAN%2Fnahdog.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5a2ede0c9de7f7de01a93c663268e26d/href">https://medium.com/media/5a2ede0c9de7f7de01a93c663268e26d/href</a></iframe><p>I’m not a top bug hunter, and I’m not writing this as someone who has hundreds of bug bounty reports. I’m writing this as someone who’s been exactly where most beginners are today — trying payload after payload, switching programs, watching other people post write-ups, and wondering why nothing was working.</p><p>These are a few lessons I wish someone had told me when I started.</p><h3>1. Don’t let money become your only goal</h3><p>Let’s be honest.</p><p>Most of us get into bug hunting because we hear about bug bounties. Seeing people earn thousands of dollars from a single report is exciting.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F10687007590642998367&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fmoney-gif-10687007590642998367&amp;image=https%3A%2F%2Fmedia.tenor.com%2FlE_gyBAt3F8AAAAN%2Fmoney.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b1ca1c0c465e243677255a845c0308e5/href">https://medium.com/media/b1ca1c0c465e243677255a845c0308e5/href</a></iframe><p>There’s nothing wrong with wanting that.</p><p>The problem starts when money becomes the only objective.</p><p>When you’re only thinking about rewards, you begin rushing through applications. You skip understanding features because you’re already thinking about the next payload or the next target.</p><p>You stop asking:</p><ul><li>Why does this feature exist?</li><li>How is it implemented?</li><li>What assumptions is the developer making?</li></ul><p>Instead, you start asking:</p><blockquote><em>“Where should I inject this payload?”</em></blockquote><p>That mindset rarely works.</p><p>Bug hunting rewards curiosity far more than speed.</p><p>If your focus is learning, you’ll naturally become better at finding vulnerabilities.</p><p>The money is a consequence of your skill not the other way around.</p><h3>2. Choose programs with a familiar tech stack</h3><p>One of the biggest mistakes I made was testing applications built with technologies I barely understood.</p><p>If you’re comfortable with React, Flask, Node.js, Spring Boot, Laravel, Django, or any other framework, start there.</p><p>Knowing how developers usually implement authentication, APIs, file uploads, role management, sessions, or routing gives you a huge advantage.</p><p>You begin to think like the developer.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F16644513012642585936&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fok-gif-16644513012642585936&amp;image=https%3A%2F%2Fmedia.tenor.com%2F5v0wZgntnVAAAAAN%2Fok.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f6d4ce4896090bf0374e0a4337b7a83/href">https://medium.com/media/9f6d4ce4896090bf0374e0a4337b7a83/href</a></iframe><p>And once you understand how something is supposed to work, it’s much easier to imagine how it could fail.</p><p>Understanding implementation is often more valuable than memorizing hundreds of payloads.</p><h3>3. Stop testing randomly. Follow a methodology.</h3><p>Many beginners start by clicking random buttons and trying payloads they found online.</p><p>Sometimes you get lucky.</p><p>Most of the time, you don’t.</p><p>A checklist is much more than a list of payloads.</p><p>It’s a systematic way of exploring an application.</p><p>For every feature, ask yourself questions like:</p><ul><li>Can this be accessed without authentication?</li><li>What happens if I change this parameter?</li><li>Is authorization properly enforced?</li><li>Can I upload unexpected file types?</li><li>Is input validated on both the client and the server?</li><li>Does this API trust user-controlled data?</li></ul><p>A good methodology helps you think consistently. Luck becomes less important because your process becomes stronger.</p><p>Some Good Checklists</p><ul><li><a href="https://alike-lantern-72d.notion.site/Web-Application-Penetration-Testing-Checklist-4792d95add7d4ffd85dd50a5f50659c6">Web Application Penetration Testing Checklist | Notion</a></li><li><a href="https://hariprasaanth.notion.site/WEB-APPLICATION-PENTESTING-CHECKLIST-0f02d8074b9d4af7b12b8da2d46ac998">WEB APPLICATION PENTESTING CHECKLIST | Notion</a></li><li><a href="https://github.com/0xmaximus/Galaxy-Bugbounty-Checklist/tree/main">GitHub - 0xmaximus/Galaxy-Bugbounty-Checklist: Tips and Tutorials for Bug Bounty and also Penetration Tests.</a></li></ul><h3>4. Stay with one program longer than you think</h3><p>This is probably the advice I wish I had heard sooner.Many beginners switch targets every day.</p><p>“No bugs today? Let’s try another program.”</p><p>A week later: “No luck here either. Time to switch again.”</p><p>The problem is that real understanding takes time.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F24236576&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fkapha-gif-24236576&amp;image=https%3A%2F%2Fmedia.tenor.com%2Fr8mHQsu7RfYAAAAN%2Fkapha.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/dff67940f939dfdc426694c6661fbfeb/href">https://medium.com/media/dff67940f939dfdc426694c6661fbfeb/href</a></iframe><p>The first day, you’re just figuring out what the application does.</p><p>The second day, you’re understanding the workflows.</p><p>The third day, you’re noticing implementation details.</p><p>Weeks later, you begin seeing assumptions and edge cases that you completely missed in the beginning.That’s where interesting vulnerabilities often come from.</p><p>Social media makes it look like everyone is finding bugs every week.</p><p>What it doesn’t show are the countless hours spent understanding the application before that report was ever submitted.</p><p>Mastery comes from depth, not constant switching.</p><h3>5. Don’t fall into the AI trap</h3><p>This is something I see more and more.</p><p>People say:</p><blockquote>“Just use AI.”<br> “Claude Code will find the bugs for you.”</blockquote><p>AI is an incredible tool.</p><p>Experienced bug hunters use it to understand unfamiliar code, summarize documentation, brainstorm attack scenarios, review implementations, and automate repetitive work.</p><p>But many beginners misunderstand its role.</p><p>They believe AI will find bugs for them.</p><p>That’s the trap.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F14391700870307646435&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fai-user-no-thanks-i-use-llamo-gif-14391700870307646435&amp;image=https%3A%2F%2Fmedia.tenor.com%2Fx7mXsOheC-MAAAAN%2Fai-user-no-thanks-i-use.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a250630059de9b95eb3989ea4671186b/href">https://medium.com/media/a250630059de9b95eb3989ea4671186b/href</a></iframe><p>Without understanding the application yourself, AI usually gives generic testing ideas.</p><p>You spend hours trying them. Nothing works.</p><p>Eventually you start questioning yourself.</p><p>“Why am I still not finding bugs?”</p><p>The issue isn’t AI.</p><p>The issue is expecting AI to replace understanding.</p><p>Use AI after you’ve explored the application yourself.</p><p>Ask it to challenge your assumptions.</p><p>Ask it what you’ve missed.</p><p>Ask it to explain code you don’t understand.</p><p>Let AI amplify your thinking — not replace it.</p><h3>Bug hunting is really about understanding</h3><p>I’ve slowly realized that bug hunting isn’t a game of payloads.</p><p>It’s a game of curiosity.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F17157483&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fyep-yes-yeah-yas-nods-gif-17157483&amp;image=https%3A%2F%2Fmedia.tenor.com%2FUAkX0aMB_f0AAAAN%2Fyep-yes.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/d2fe2bc8bc01da7e22d1894908318c45/href">https://medium.com/media/d2fe2bc8bc01da7e22d1894908318c45/href</a></iframe><p>Every feature in an application exists because a developer made a series of decisions.</p><p>Your job isn’t to memorize attacks.</p><p>Your job is to understand those decisions well enough to recognize when an assumption can be broken.</p><p>That’s why experienced bug hunters often seem to find bugs in places beginners never even think to look.</p><p>It’s not because they know a secret payload.</p><p>It’s because they understand applications at a much deeper level.</p><p>The vulnerability is simply the result of that understanding.</p><p>So if you’re a beginner who’s feeling frustrated because you haven’t found your first bug yet, don’t measure your progress only by reports.</p><p>Measure it by how much better you understand the applications you’re testing today compared to last month.</p><p>Because eventually, those two paths meet.</p><p>The better your understanding becomes, the more likely your first valid report becomes.</p><p>Keep learning.</p><p>Stay patient.</p><p>The bugs will come :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0e7abd55dc7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Windows Authenticates Users : A Beginner-Friendly Guide]]></title>
            <link>https://medium.com/@T3rmint0r_01/how-windows-authenticates-users-a-beginner-friendly-guide-018254ccd045?source=rss-4f8df3eca4c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/018254ccd045</guid>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[passwords]]></category>
            <category><![CDATA[windows]]></category>
            <dc:creator><![CDATA[T3rminat0r]]></dc:creator>
            <pubDate>Sun, 03 Aug 2025 08:25:12 GMT</pubDate>
            <atom:updated>2025-08-03T09:06:09.113Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Happens When You Log In ? Windows Authentication Explained</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CBQ_FpcWalt_rG25ZZIFXw.jpeg" /></figure><p>Ever wondered what really happens behind the scenes when you log into your Windows machine?<br>Authentication isn’t just about entering a password — it’s a critical security process that decides whether you’re allowed in or not. From personal laptops to enterprise networks, Windows relies on specific methods to verify your identity.</p><p>As I dove deeper into my cybersecurity journey, I became curious:</p><p>How does Windows actually authenticate users?</p><p>In this beginner-friendly post, I’ll break down the three core methods used by Windows — LM, NTLM, and Kerberos — in the simplest way possible, so you can finally understand what’s happening every time you log in.</p><blockquote>What is Authentication ??</blockquote><blockquote>Authentication is the process of confirming that someone (a user, device, or system) is who they say they are.</blockquote><p>In Windows, when you log in, the system asks:</p><p>System &gt; “Can I trust that this user is really Amanda(username)?”</p><p>To answer this, it uses different authentication protocols.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*wkR8jehl5yPHCdnV2hEUKA.png" /><figcaption><strong>Windows Login Screen</strong></figcaption></figure><p>📂 Types of Authentication in Windows</p><p>Let’s look at the three major methods used by Windows to authenticate users:</p><p><strong>1.</strong> <strong>LM (LAN Manager) Authentication </strong>— Old &amp; Broken</p><p>What it is :</p><ul><li>One of the earliest Windows authentication methods.</li><li>Converts your password to uppercase, splits it, and hashes it using weak encryption (DES - Encryption Algorithm).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*SRPG2Ba4dV_Gql9EiXgttQ.png" /><figcaption><strong>LM HASHING PROCESS</strong></figcaption></figure><p>Why it’s bad:</p><ul><li>Easy to crack — tools can break LM hashes in seconds.</li><li>It was mainly used in Windows 95/98/NT , old versions and is now disabled by default.</li></ul><p>Still used?</p><p>Almost never in modern systems.</p><p>2.<strong> NTLM (NT LAN Manager) Authentication </strong>— Still Hanging On</p><p>What it is:</p><ul><li>Replaced LM ; more secure but still old.</li><li>Uses a challenge-response system to avoid sending the actual password.</li><li>The password is hashed (into an NTLM hash) and compared during login.</li></ul><p>Where it’s used:</p><ul><li>Local logins (non-domain systems)</li><li>Fallback method when Kerberos isn’t available</li><li>Remote logins using SMB, RDP, etc.</li></ul><p>Security issues:</p><ul><li>Can be abused in Pass-the-Hash and NTLM relay attacks.</li><li>Still present in many networks today.</li><li>Usually MD5 hashing algorithm used.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*TWcCOKblXkdaQpJXI7LkzA.png" /><figcaption>NTLM HASHING PROCESS</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*-12AoQMX-6Eds3-YQ2Kllw.png" /><figcaption><strong>Working Of NTLM Authentication</strong></figcaption></figure><p><strong>3. Kerberos Authentication</strong> — Ticket to the Domain</p><p>What it is:</p><ul><li>The default method in Active Directory environments.</li><li>Based on a ticketing system.</li><li>Instead of exchanging passwords, you get a Ticket Granting Ticket (TGT) from the Key Distribution Center (KDC).</li></ul><p>Why it’s better:</p><ul><li>Password never travels over the network.</li><li>Supports mutual authentication.</li><li>More secure and faster than NTLM.</li></ul><p>Still vulnerable?</p><ul><li>Yes. Attacks like Kerberoasting, Pass-the-Ticket, and Overpass-the-Hash target it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*RBAyPp6Jr7tkXFGhv3iTsg.png" /><figcaption><strong>Working of Kerberos Authentication</strong></figcaption></figure><h4><strong><em>SECURITY ACCOUNTS MANAGER(SAM)</em></strong></h4><p><em>SAM is a database within the Windows system that stores user passwords in a hashed format. This is mainly used for local accounts on a system that’s not connected to a domain.</em></p><p>Example: Hash Format in Windows (From SAM Dump)</p><p>In what format hashes are stored?</p><blockquote>Administrator:500:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0:::</blockquote><p>Here ,</p><p>Username - Administrator.</p><p>RID (Relative Identifier) — 500.</p><p>LM hash — aad3b435b51404eeaad3b435b51404ee.</p><p>NTLM hash — 31d6cfe0d16ae931b73c59d7e0c089c0.</p><p>Thankyou.</p><p>### Image Credits:<br>- NTLM overview image: <a href="https://lab.wallarm.com/what/what-is-ntlm/">Wallarm</a> s<br>- Kerberos diagram: <a href="https://www.sqltabletalk.com/?p=742">SQL Table Talk</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=018254ccd045" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>