<?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 Minio Haxer on Medium]]></title>
        <description><![CDATA[Stories by Minio Haxer on Medium]]></description>
        <link>https://medium.com/@syedshorox27?source=rss-5ef2fd08e1d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qnPJszGfOG2xvOCs84IUIQ@2x.jpeg</url>
            <title>Stories by Minio Haxer on Medium</title>
            <link>https://medium.com/@syedshorox27?source=rss-5ef2fd08e1d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:44:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@syedshorox27/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[From Gmail to Gmàil: A Punycode Path to Account Takeover]]></title>
            <link>https://medium.com/@syedshorox27/from-gmail-to-gm%C3%A0il-a-punycode-path-to-account-takeover-88896264acdb?source=rss-5ef2fd08e1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/88896264acdb</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[account-takeover]]></category>
            <dc:creator><![CDATA[Minio Haxer]]></dc:creator>
            <pubDate>Tue, 02 Sep 2025 10:14:34 GMT</pubDate>
            <atom:updated>2025-09-02T10:14:34.396Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E2oeuuQjX_bDJMTUeC2FYQ.png" /></figure><blockquote>Ever notice how one little dot or accent on a letter can change a whole word? Like café vs. cafe — same thing, right? Well, turns out, on the internet those little accents can cause some <em>seriously big problems</em>.</blockquote><p>Internationalized Domain Name (IDN) Homograph Attacks exploit characters from different languages that <strong>look identical to humans but are totally different to computers</strong>. Think Latin “a” vs Cyrillic “à”. Same vibe to your eyes, but two different beasts under the hood.</p><p>This is where <strong>Punycode</strong> steps in. It’s the way computers squish Unicode characters into ASCII so systems can handle them. For example:</p><pre>Unicode: gmàil.com<br>Punycode: xn--gml-9na.com</pre><p>Now imagine what happens when an app forgets to tell the difference. That’s where my little adventure began.</p><h3>My Real-Life Scenario</h3><p>Recently, while poking around a website’s signup and password reset flow (as one does), I discovered a sneaky way to hijack an account. Let me break it down.</p><h3>The “Normal” Signup</h3><p>I registered on a website using Burp Collaborator as my fake inbox:</p><pre>XYZ@gmail.com.8dmmx76z1b7u5xyw1kvwyojex53wrnfc.oastify.com</pre><p>Totally normal… okay, maybe not <em>totally</em>, but the app accepted it. So far, so good.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgIYvSYhd4xZ8l6fYNs0wQ.png" /></figure><h3>The Forgot Password Adventure</h3><p>I logged out and hit the <strong>“Forgot Password”</strong> button. I entered the same email. But this time, my hacker brain whispered:</p><blockquote><em>“What if Gmail… but make it </em>fancy<em>?”</em></blockquote><h3>Meet My Stylish “à”</h3><p>I intercepted the request in Burp and changed:</p><pre>@gmail.com</pre><p>to:</p><pre>@gmàil.com</pre><p>See it? No? Exactly. One tiny accent. To humans it’s Gmail, to computers it’s… chaos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHMB40nulDG1C1bhMdhH2g.png" /></figure><h3>Step 4: When Burp Collaborator Became Santa Claus</h3><p>Seconds later, my Collaborator server delivered a gift: 🎁<br> 👉 The <strong>password reset link</strong>.</p><p>I clicked it, reset the password, and… congratulations to me. I had just taken over the account. All thanks to an accent mark that looks like it belongs in a coffee shop menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yymW8W4qm3Nc0A5YnV-qVg.png" /></figure><h3>Step 5: The Aftermath (a.k.a. “Wait, That Worked?”)</h3><ul><li>I could log in.</li><li>I could reset passwords.</li><li>I could have locked out the real user (if this wasn’t my own account).</li></ul><p>Basically, I tricked the system into sending <em>me</em> the keys to the castle because it couldn’t tell the difference between an “a” and an “à”.</p><h3>Why This Is Actually Serious (No Joke Now)</h3><ul><li><strong>Account Takeover:</strong> Full control of user accounts.</li><li><strong>No Clicks Needed:</strong> Unlike phishing, victims don’t even interact.</li><li><strong>Lockouts:</strong> Real users get locked out of their own accounts.</li><li><strong>Data Theft:</strong> Payments, PII, admin privileges… all exposed.</li></ul><h3>Bonus Tricks</h3><ul><li><strong>Local-Part Mischief:</strong> Use ṡhoroxhaxer@gmail.com instead of shoroxhaxer@gmail.com. Looks same-ish, still deadly.</li><li><strong>2FA Hijack:</strong> Register victim@gmáil.com, set up your own 2FA, then use <em>your</em> code to bypass theirs. That’s like stealing someone’s house keys <em>and</em> their security system.</li></ul><h3>Mitigation (For Devs Who Don’t Want Grey Hairs)</h3><ul><li>Only accept ASCII in emails (unless you’re 100% sure you need Unicode).</li><li>Normalize inputs — treat a and à consistently.</li><li>Reject suspicious punycode domains (xn--stuff) unless explicitly required.</li><li>Apply the same logic everywhere (signup, login, reset).</li></ul><h3>Conclusion</h3><p>No zero-day. No malware. Just me being petty with Unicode.</p><blockquote>Sometimes, security isn’t about breaking firewalls — it’s about giving one letter a silly hat and watching the system collapse.</blockquote><p>So next time you see an email with an extra squiggle or accent… maybe don’t ignore it. That accent might just be plotting world domination.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88896264acdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a Simple .git/config Check Earned Me €1000]]></title>
            <link>https://medium.com/@syedshorox27/how-a-simple-git-config-check-earned-me-1000-23699662a134?source=rss-5ef2fd08e1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/23699662a134</guid>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Minio Haxer]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 23:44:16 GMT</pubDate>
            <atom:updated>2025-08-05T05:39:33.833Z</atom:updated>
            <content:encoded><![CDATA[<h3>How a Simple .git/config Check Earned Me €1000</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E2oeuuQjX_bDJMTUeC2FYQ.png" /></figure><h3>🕵️‍♂️ “Oops, You Left Your .git Open!&quot; – How I Stumbled Upon a €1000 Bounty by Accident</h3><blockquote>“Why break in when the front door is already open?”</blockquote><h3>🚀 Intro — The Day I Met a Leaky Git Repo</h3><p>One fine evening, as I was sipping my coffee and mindlessly probing random websites (like every other bored bug bounty hunter), I accidentally hit <strong>gold</strong> — or more accurately, I hit /.git/config and it said <strong>&quot;Download me!&quot;</strong> like a clingy ex.</p><p>What happened next earned me a <strong>$1000 bounty</strong>, some self-esteem, and an even bigger addiction to recon. So sit back, grab your laptop, and let me walk you through this journey — from <strong>“hmm, let me check this”</strong> to <strong>“Boom! Full source code in my pocket.”</strong></p><h3>🔍 Step 1: Recon Like a Stalker (But Ethical)</h3><p>It all started with some passive recon. You don’t need fancy tools here. Just a browser and a bit of curiosity.</p><p>I visited:</p><pre>https://victim.com/.git/config</pre><p>And guess what?<br> 💥 <strong>HTTP 200 OK</strong> — and boom, it downloaded a config file!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*kChfaavhpN4ZPPUcD7crXA.png" /></figure><p>Most beginners don’t realize this, but <strong>if </strong><strong>.git/config is accessible</strong>, it likely means the <strong>entire </strong><strong>.git folder is public</strong>. That’s like leaving your diary on the street with a sign that says “pls don’t read.”</p><h3>⚙️ Step 2: “git clone but make it cursed” — Using GitDumper</h3><p>Now that I knew .git/ was exposed, I pulled out my weapon — <a href="https://github.com/internetwache/GitTools/tree/master/Dumper">git-dumper</a>.</p><h4>🧪 The command:</h4><pre>./git_dumper.py https://victim.com/.git/ /tmp/victim-source</pre><p>It started dumping like my ex after 2 years of silence.<br>A few seconds later… I had the <strong>entire Git history and source code</strong>.</p><p>I felt like Tony Stark when he saw his suit fly for the first time. 😎</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*s2Xyz8HEWbAjmPsZHBqApA.png" /></figure><h3>🧠 Step 3: Let’s See What You Hid, Dev</h3><p>Once dumped, I ran this:</p><pre>cd /tmp/victim-source<br>git log</pre><p>And boy oh boy — API keys, secrets, database creds, internal endpoints… the devs weren’t shy in committing secrets to version control. One file literally had:</p><pre>db_password = &quot;SuperSecret123&quot;</pre><p>I’m not saying this is bad practice…<br><strong>But this is bad practice.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*dzd8gGwCySqYIRtUuCLNpQ.png" /></figure><h3>🎯 Impact — Why This Is Serious</h3><p>When .git/ is exposed:</p><ul><li>You can reconstruct the entire source code</li><li>Find old files, deleted secrets, comments</li><li>Steal database credentials, API keys, access tokens</li><li>Understand internal logic for further attacks</li></ul><p><strong>This is no joke.</strong> I could’ve weaponized the app, but I reported it instead (because karma is real and bug bounty is better 😉).</p><h3>💰 Step 4: Report It, Sleep, Wake Up Rich</h3><p>I submitted the report with:</p><ul><li>A short summary of the issue</li><li>Steps to reproduce (including the .git/config test)</li><li>Full evidence of the extracted repo</li><li>The juicy credentials I found (responsibly blurred)</li></ul><p>✅ Few hours later:<br> “Thanks for reporting! Here’s €1000 🎉”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5AbH4J9ZpRgvdCtiUDPpfA.png" /></figure><h3>🛡️ Fix? It’s Simple, Devs!</h3><p>If you’re reading this and you’re a developer:</p><p><strong>don’t push your </strong><strong>.git to prod</strong> at all. Seriously.</p><h3>🧠 Final Thoughts — Keep It Ethical, Keep It Fun</h3><p>This wasn’t a high-tech, Hollywood-style hack. It was just:</p><ul><li>Curiosity</li><li>Basic recon</li><li>A bit of knowledge</li><li>And a dash of luck</li></ul><p>And yet, it landed me <strong>$1000</strong>. That’s the beauty of bug bounty: sometimes all you need to do is check if the door is unlocked.</p><p>So go forth, recon warriors. Hunt ethically. Get that bag. And remember…</p><blockquote><em>🔐 “If it’s public, it’s probably a problem.”</em></blockquote><p>Stay safe, stay curious!<br> — <em>YourFriendlyNeighborhoodPentester</em></p><p>#BugBounty #WebSecurity #Hacking #CyberSecurity #PenetrationTesting #InfoSec #SecurityResearch #EthicalHacking #RedTeam #BugBountyTips #CTF #OWASP #WebAppSecurity #SecurityVulnerabilities #HackThePlanet #BugHunters</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23699662a134" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SSRF via Host Header Injection — A Prank Gone Vulnerable]]></title>
            <link>https://medium.com/@syedshorox27/ssrf-via-host-header-injection-a-prank-gone-vulnerable-52eb514f664d?source=rss-5ef2fd08e1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/52eb514f664d</guid>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <dc:creator><![CDATA[Minio Haxer]]></dc:creator>
            <pubDate>Wed, 30 Jul 2025 00:03:53 GMT</pubDate>
            <atom:updated>2025-07-30T00:03:53.051Z</atom:updated>
            <content:encoded><![CDATA[<h3>SSRF via Host Header Injection — A Prank Gone Vulnerable</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E2oeuuQjX_bDJMTUeC2FYQ.png" /></figure><h3>🕵️‍♂️ How I Made a Server Talk to Me (Host Header Injection to SSRF) 🎯💣</h3><p><em>When I told the server to call me back, and it actually did…</em> 😏</p><blockquote><em>“Knock knock.”<br> “Who’s there?”<br> “You… but inside your own network.”<br> — </em>SSRF, probably</blockquote><h3>💡 What the Heck is SSRF?</h3><p><strong>Server-Side Request Forgery (SSRF)</strong> is like a digital prank: you convince a vulnerable server to make requests <strong>on your behalf</strong> — to internal systems, third-party servers, or even back to itself.</p><p>Imagine telling someone inside a secure building:</p><blockquote><em>“Hey, can you go knock on that door?”<br> And they just do it. No questions asked. 🤷‍♂️</em></blockquote><h3>🏁 Where It All Began</h3><p>While poking around the application at https://example.com,<br>I noticed something <em>a little too friendly</em> about how the server handled headers.</p><p>So naturally, I thought…</p><blockquote><em>What if I pretend to be someone I’m not?<br> And what if the server actually believes me?</em></blockquote><h3>🐞 The Vulnerability: Host Header Injection</h3><p>Most apps use the Host header to determine routing. But if the app trusts <strong>any host header</strong> — or worse, accepts <strong>X-Forwarded-Host</strong> without validation — it&#39;s game on.</p><p>So I added a sneaky line into my Burp Suite request:</p><pre>X-Forwarded-Host: zy1fjueqyy9fujf7bcf6ynn5uw0nodc2.oastify.com</pre><p><strong>And guess what?</strong><br> The server accepted it like an obedient intern. 🙃</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RB26NRm0VGcdV7_qY7G69g.png" /></figure><h3>🧪 The Setup: Here’s the full HTTP request I sent:</h3><pre>GET / HTTP/1.1<br>Host: example.com<br>X-Forwarded-Host: zy1fjueqyy9fujf7bcf6ynn5uw0nodc2.oastify.com<br>User-Agent: YourFriendlyNeighborhoodPentester</pre><p>Then I sat back, opened Burp Collaborator, and waited like…</p><h3>😱 The Response (from the server, not my ex)</h3><p>BOOM! 🎉<br>Both <strong>DNS</strong> and <strong>HTTP</strong> interactions hit my *.oastify.com domain.</p><p>That means the server was like:</p><blockquote><em>“Okay bro, calling your domain now. What do you want?”</em></blockquote><p>This was <strong>confirmed SSRF</strong> — triggered via <strong>Host header injection</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*70s6zSzbAIBVJieJVdIwdw.png" /></figure><h3>🎯 Real-World Impact</h3><p>If I can make the server call my domain, I can also ask it to:</p><ul><li>Access internal systems like <a href="http://127.0.0.1:8000/">http://127.0.0.1:8000</a></li><li>Grab AWS instance metadata via <a href="http://169.254.169.254/latest/meta-data">http://169.254.169.254/latest/meta-data</a></li><li>Scan internal services</li><li>Chain it into <strong>RCE</strong>, <strong>data leakage</strong>, or <strong>privilege escalation</strong></li></ul><p>Basically: 💀</p><h3>🧰 Tools I Used</h3><p>I also tried the legendary <a href="https://github.com/swisskyrepo/SSRFmap"><strong>SSRFmap</strong></a>:</p><pre>python3 ssrfmap.py -r request.txt -p X-Forwarded-Host -m readfiles,portscan --ssl</pre><p>But it whined like:</p><pre>[ERROR]: No injection point found! (use -p)</pre><p>Classic tools-being-dramatic behavior. So I went manual — and it paid off!</p><h3>🛡️ How to Fix It (for Devs)</h3><ol><li><strong>Do not trust user-controlled headers</strong> (Host, X-Forwarded-Host, X-Forwarded-For, etc.)</li><li>Use a strict <strong>allowlist</strong> for valid hostnames.</li><li>If you rely on headers for routing, use a secure reverse proxy that sanitizes them.</li><li>Reject or filter suspicious requests before they touch your internal logic.</li><li>Monitor unexpected outbound traffic — you never know when your app becomes a middleman in someone else’s mischief.</li></ol><h3>🧠 Final Thoughts</h3><p>What seemed like a boring header turned into a full-blown <strong>SSRF exploit</strong>. All because the server didn’t verify who it was talking to.</p><p>Host Header Injection is like giving someone a fake return address — and they blindly send you their secrets.</p><p>And SSRF? It’s that “guy inside the building” who doesn’t ask questions, just makes phone calls — and maybe even sends files 🤫.</p><h3>💬 Gotchas, LOLs, and Lessons</h3><ul><li>Don’t always rely on tools. Your brain and Burp Suite are a deadly combo 💥</li><li>If you’re not getting hits in Burp Collaborator, try <strong>redirects</strong> or <strong>iframes</strong></li><li>Always monitor both DNS and HTTP interactions — sometimes the server’s just being sneaky, like my friend <a href="https://medium.com/u/20ae7253d293">Shazilrao</a>🐍<br> Just kidding 😄 — he’s not sneaky (most of the time). He’s actually a sharp bug hunter and pentester! You can check out his blog too — full of cool tricks and techniques that’ll make your Burp smile.</li></ul><blockquote><a href="https://medium.com/@shazilrao620/from-image-upload-to-account-takeover-chaining-upload-storage-and-cors-issues-in-a-real-pentest-de5ac9862c31">https://medium.com/@shazilrao620/from-image-upload-to-account-takeover-chaining-upload-storage-and-cors-issues-in-a-real-pentest-de5ac9862c31</a></blockquote><h3>🫶 Like What You Read?</h3><p>Let’s connect on <a href="https://www.linkedin.com/in/syed-hasan-26a07b232/">LinkedIn</a>, or shout out in the comments!</p><p>And remember:</p><blockquote><em>With great SSRF comes great </em><strong><em>liability disclosure forms</em></strong><em> 📝<br> (and sometimes bounty 💰)</em></blockquote><p>Stay safe, stay curious!<br> — <em>YourFriendlyNeighborhoodPentester</em></p><p>#BugBounty #WebSecurity #SSRF #HostHeaderInjection #Hacking #CyberSecurity #PenetrationTesting #InfoSec #SecurityResearch #EthicalHacking #RedTeam #BugBountyTips #CTF #OWASP #WebAppSecurity #SecurityVulnerabilities #HackThePlanet #BugHunters</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52eb514f664d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2500$ From Login Bypassed & MFA Using a Race Condition + JWT Leak]]></title>
            <link>https://medium.com/@syedshorox27/25000-from-login-bypassed-mfa-using-a-race-condition-jwt-leak-6139fcc22573?source=rss-5ef2fd08e1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6139fcc22573</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bounty-program]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Minio Haxer]]></dc:creator>
            <pubDate>Tue, 15 Jul 2025 19:39:12 GMT</pubDate>
            <atom:updated>2025-07-15T23:12:45.986Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E2oeuuQjX_bDJMTUeC2FYQ.png" /></figure><h3>How I Bypassed Login &amp; MFA Using a Race Condition + JWT Leak</h3><blockquote><em>What happens when you race 50+ login requests at once? Sometimes, magic.</em></blockquote><p>Hey hackers 👋 — this post is a fun deep dive into a critical authentication vulnerability I discovered during a recent security test. It combines one of my favorite web bugs (race condition) with a juicy JWT leak and ends in full account takeover — even with MFA enabled. Yep. Let’s get into it.</p><h3>🧪 The Setup: Good Login Security (At First Glance)</h3><p>So I was testing this app’s login page. Pretty standard stuff: enter your email and password, and if you’re lucky (and legit), it shoots back a JWT and asks for a 6-digit OTP (Multi-Factor Authentication). Simple, right?</p><p>To their credit, the devs had implemented account lockout — after 5–6 incorrect login attempts, the account would lock for 10 minutes. Nice!</p><p>But of course… I had other plans. 😈</p><h3>🎯 Target: Beat the Lockout With Speed (Race Condition)</h3><p>I figured if I could send multiple login attempts simultaneously, I might be able to squeeze a correct password in before the lockout logic kicks in.</p><h3>So I did this:</h3><ul><li>Created a list of password attempts (including the correct one 😉)</li><li>Loaded up <strong>50+ requests</strong> in <strong>Burp Repeater</strong></li><li>Launched them all at once like a packet flood</li></ul><p>And guess what?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L1QJJ_kH6pDsu1jqYTwUKA.png" /></figure><blockquote><em>💥 </em><strong><em>BOOM</em></strong><em> — The server sent back a </em><strong><em>valid JWT</em></strong><em>, even though it should’ve locked me out.</em></blockquote><p>So the lockout check wasn’t atomic. The race was won by the correct password before the server tallied up the failures.</p><h3>🔓 The Surprise: JWT Had a Hidden Auth Code 👀</h3><p>Now here’s where it gets spicy.</p><p>The JWT looked something like this:</p><pre>{<br>  &quot;token&quot;: &quot;eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...&quot;,<br>  &quot;scope&quot;:&quot;read&quot;,<br>  &quot;token_type&quot;:&quot;AuthCode&quot;,<br>  &quot;expires_in&quot;:900<br>}</pre><p>Wait… what’s authCode? 🤔</p><p>After decoding the JWT, I saw what the authCode is and wondered why it’s included there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AOoVkxCSdptjGT0N4SF8Pw.png" /></figure><p>So I thought:</p><blockquote><em>What if I submit </em><strong><em>any random OTP</em></strong><em> with this valid JWT?</em></blockquote><p>I tried it… and…</p><blockquote><em>✅ </em><strong><em>It worked.</em></strong><em> I was logged in.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lPSyys_eOySbt1GRiZMxdg.png" /></figure><p>OTP <strong>bypassed | </strong>MFA <strong>defeated | </strong>Account <strong>compromised</strong>.</p><h3>💡 Why This Happens</h3><ul><li>Login and lockout logic wasn’t atomic (race won by correct password)</li><li>JWT was issued <strong>before</strong> verifying OTP</li><li>OTP validation was too trusting — the authCode leaked in JWT gave away the answer</li></ul><h3>🔥 The Impact</h3><ul><li>Full login and MFA bypass</li><li>No CAPTCHA or throttling to stop race</li><li>Accounts <strong>without MFA enabled</strong> would be 100% compromised</li><li>Even MFA-protected accounts could be broken into by abusing the leaked authCode</li></ul><h3>✅ Final Thoughts</h3><p>This was one of those bugs that just <em>shouldn’t happen</em>. But it does — and when it does, it’s awesome (and terrifying).</p><p>Security isn’t just about blocking bad input — it’s also about handling timing, trust, and sequencing properly.</p><p>I responsibly reported the bug, got it patched, and now I’m sharing it with you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*HD-z6BTshHbrIFYhAcy5vw.png" /></figure><p>Stay curious, stay ethical, and keep breaking things (safely).</p><p>Happy hacking! 🐱‍💻</p><p>#bugbounty #websecurity #jwt #racecondition #mfa #infosec #cybersecurity #redteam</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6139fcc22573" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>