security researcher 🪩 18 yo hacker

Joined February 2025
hexa retweeted
Lazarus group has been paid ~1.6B in bug bounties last year
79
159
45
2,632
328,130
Replying to @BugcrowdSupport
@BugcrowdSupport I’m seeking an update regarding 3 vulnerability reports that have been pending for over a year My support ticket has also been open for several months and was previously escalated to the CEM/Program Owner,but there has still been no substantive update @Bugcrowd
9
2
2
53
3,999
Thank you @Bugcrowd @inspectiv @Hacker0x01 ❤️‍🔥 This video is for those who think their life can’t change from where they are.
196
141
23
2,870
126,934
FREE $200 IN AI CREDITS Agent Router is giving new users $200 in free API credits. Current models to try out: gpt-5.6-sol, claude-opus-5, claude-opus-4-8. Eligibility: >Your GitHub account must have been created before 2025 How to claim it: Visit agentrouter.org/register?aff… -Sign up with GitHub -Don’t use the Gmail or username sign-in options That’s all. I tested the credits with my Hermes agent and successfully ran GPT-5.6 Sol. Don’t miss this opportunity if you qualify.
328
100
103
1,097
410,193
Just launched VULNEX – my new website!A clean library with ready payloads, vulnerability testing techniques, useful commands, Google Dorks, and resources for Bug Bounty & Cybersecurity.Everything neatly organized for easy use.Check it out: vulnex.vercel.app/Hope #BugBounty
2
21
2
91
4,104
I’ve noticed that most new folks who reach out for guidance in bug bounty feel overwhelmed early on trying to learn everything at once. That often leads to half-baked knowledge across multiple areas and slower overall progress. Here's what I recommend instead 👇 1/ Pick one vulnerability type and go all in. Master the ins and outs of that category - how it works, how it breaks, real-world examples, and ways to find it. Once you’ve got depth in one area, the rest will follow naturally. 2/ To put this into perspective, here’s a snapshot of the types of issues I’ve reported over the last 5 years - gradually expanding focus as I grew more confident: 2020: • Local cache issues • Rate limit issues on Login • Session invalidation • MFA bypass 2021: • Rate limit • MFA bypass • CSRF • IDOR • RBAC 2022: • CSRF • IDOR • RBAC • XSS • Business logic • Info disclosure 2023: • Everything from 2022 + • BBP automation • Cache deception • DoS Issues • Subdomain takeover • Auth bypass / misconfig • SQLi • SSRF • RCE 2024: • Everything from 2023 + • AI-related issues • Vhost misconfigurations 2025: • Everything from 2024 + • Many more new things that I will talk about soon :) 3/ There are more, of course, but this covers most of what’s worked well for me. The key takeaway: you don’t need to know everything. Play to your strengths. Stay consistent. And let your scope expand naturally. Hope this helps someone starting out 💪
15
78
3
399
25,764
hexa retweeted
It's Sunday tune in to get a giveaway on our server ✅ You can stand a chance to win a 1 month nitro or $10 discord.gg/theenchantedfores… @owerrisfirstson @keenn_eth
1
1
55
Good night guys Did I engage you today?
37
1
45
442
hexa retweeted
Tech_baby
@Tech_babbyJul 6
Start small but don’t stay small.
4
5
29
2,444
🚨FREE Bug Bounty Advanced Hunting Course 🚨 Learn Bug Bounty and earn money 📲 Topics Covered - Introduction to Bug Bounty -Information Gathering -Setting Up Labs -Introduction to Burp Suite -SQL Injection -Web Application Vulnerabilities -Cross-Site Scripting (XSS) -Header Injection & Other Attacks -Client-Side Attacks -Brute Forcing -Security Misconfigurations -Insecure CORS -File Inclusion Vulnerabilities -Server-Side Request Forgery (SSRF) -Insecure Captcha -Automating VAPT & Bug Hunting -Documenting & Reporting Bugs -And more … 🔗 To get the Link - 🙌 Follow 🙌 Like & Retweet 🙌 Reply "money" 🚀 I will DM the link to everyone
514
338
8
911
79,378
Time for a critical vulnerability discovery story. 📖 Gather around folks. Based on a true story - some details changed for anonymity. A pentester (let's call him Jerry) was testing a critical application, it was controlling a gigantic water processing plant for a major global city. He sat down on the first day of testing and was greeted with a custom SSO sign-in page. He fired up Burp Suite, enabled interception, and walked through the login flow. He got most of the way through the SSO flow without seeing anything overly suspicious. The login looks as though it has been successful, but he notices one last POST request pop up in proxy intercept before he's redirected to /dashboard. It's being sent to /login and it just has a JSON body {"user_id":"pentest@example[.].com"}. No password, no auth token, just an email. He switches "pentest@" to "admin@" and is greeted with full admin privileges. All before morning tea. After some further testing, he realised that you didn't even need the SSO flow, anyone could just send a POST request with the email of the user they wish to authenticate as, and the response would contain be a session token for that user. 👌 The moral of the story: sometimes, the most critical vulnerabilities are so obvious that most people don't even bother to check for them. 80% of pentesting is just validating assumptions!
3
20
163
10,422