Excited to share that I've been invited to participate in a HackerOne Live Hacking Event in Berlin.
This will be my first HackerOne LHE, and I'm looking forward to learning from talented hackers and meeting the community in person — assuming my visa application goes smoothly😄.
Bug Bounty Tool:
NoMore403 is a tool for bypassing 403 restrictions through smart techniques and adaptive request manipulation.
https://t.co/K3Abcr1Q9N
Alright so to end 2025 I am going to post something that people have been requesting for quite some time.. As alot know, I have made over $1 million dollars from SSRF vulnerabilities alone. #ssrftips Below I will provide some information on some of the ways that I beat the blacklists/deny lists and cashed in. Any method I post below has worked for me personally in the past. I am not claiming that any of these ways are 'my' discoveries, and in no way am I trying to claim other's work as my own. Simply answering a question that gets asked of me almost daily. #bugbounty #bugbountytips #togetherwehitharder #ittakesacrowd #hackers #hacking #NewYearsEveBountyTips
So lets get into it:
Encoding:
Everyone knows (or should know) about the ability to encode IP addresses. What alot of people dont know is that you can combine encoding types on a single IP. SO instead of encoding the entire IP, encode single octets etc.
Example: Changing the Metadata IP to: 0251.254.169.254 this octal encodes the 1st octet only, leaving the rest of the IP the same. This is the exact method that allowed for my $180,000 from the Yahoo Bug Bounty Program in Oct 2018
Redirects:
Alot of SSRF vulnerable functionality will follow redirects. What many people dont consider is multiple redirects. Never stop at just one. I have found many instances where an SSRF followed all redirects, and would properly block the final redirect to the target internal service (internal ip/metadata server). DO NOT STOP AT 1 REDIRECT! Instead of a single redirect, setup a simple php redirect script that will redirect the request back to the same end point multiple times before finally sending to the target IP/host. I have had many instances in the past where the target properly checks the response of the first 1,2, 3 ....6 redirects then magically on the 7th it no longer performs any valdiation and allows you to hit the metadata. I can't explain why this happens, but its happened enough that this is one of the very first things i test for when it comes to SSRF testing.
TOCTOU:
This is one of my fav's because it almost always can be used to bypass the initial fixes for an SSRF vulnerability. TOCTOU stands for: Time of Check Time of Use. When you pass a url to an SSRF vuln end point, the backend will take the host of this, resolve it (if its not already an IP), check against the allow/block list, then take action. Many frameworks will not cache the DNS lookup response that happens during the initial validation phase. When they forget to do this, having a subdomain properly setup for a TOCTOU check can allow for tricking their checks to allow for hitting banned resources.
How it works: Server resolves https://t.co/aKo0eb63ft to 1.1.1.1 and does their checks to make sure its not a blocked IP. After passing these checks the domain is passed to the function that will actually make the call. If the server did not cache the previous response, it will then resolve the host again as part of the flow to make the request. If you have a properly setup nameserver for this attack, then the instance they make the 1st DNS call, your server quickly changes the DNS entry and points it to the target IP (Metadata/Internal), so that when it gets to the function that makes the request, it resolves the host again and makes the request.
HTTP 2 vs HTTP/1.1 vs HTTP/1.0 vs HTTP/0.9
Several have had success with this in the past. And again, I am not sure why this works sometimes. But if the request is using HTTP/2 and blocks your attempt, try and change it to an older version. I have had success with each of the above at least once (most of the time on Yahoo, but others as well).
Simple/more common things:
dns rebinding, create a hostname on your domain pointing to localhost or an internal IP.
simplify the IP. example: 127.0.0.1 is blocked, so try 127.1, or 0.0.0.0, 0 etc.
Theres tons of other ways that you can get creative and do things like this. This post is just sharing some of the more fun/more unique ways that I have had success in the past. This is not ment to be an exhaustive list of things to try, and is only ment to start your brain working to come up with weird/random/fun ways to beat the black lists.
If you like the information, drop a like/comment/follow and let me know which of the above you have tried in the past, or are looking forward to trying out in 2026. If you end up having success with these, let me know as well!
Tired of junk headers or having to scroll in burp logs?
You can use:
https://t.co/gz0n81hNgk
nothing fancy, gpt coded python extension
only prettified body no scroll
#bugbounty#bugbountytips
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 💪
#Bugbountytip#bugbountytips
Install JS Miner extension over Burp
After crawling all endpoints
Click on the target ==> Extensions > Js Miner > Run All Passive scans
I got a result [Js Miner] Dependency Confusion
The package is unclaimed over NPM
Next step
Create an account on NPM
Then install the NPM in Linux
~ npm login
~ mkdir (Package Name)
~ cd package name
~ npm init -y
~ npm publish --access public
And I claimed the package
Next Step: I edit the package.json file to the RCE
POC https://t.co/vfFinyoUaM
And in the end, I got a nice P1 😍
This amazing man @m359ah , taught me 6 months ago about understanding and exploiting the Dependency Confusion, so big thanks to him ♥
#bugbounty
Happy Hunting ♥
After going through all the comments and questions about setting up IDN domains and using Punycode based emails, I finally made a video that covers everything step by step. I’m confident this will help many of you land some serious bounties!
https://t.co/EcGMaLGlbP
I just found a WAF bypass for Akamai and Cloudflare:
<address onscrollsnapchange=window['ev'+'a'+(['l','b','c'][0])](window['a'+'to'+(['b','c','d'][0])]('YWxlcnQob3JpZ2luKQ==')); style=overflow-y:hidden;scroll-snap-type:x><div style=scroll-snap-align:center>1337</div></address>
IP whitelisting is fundamentally broken. At @assetnote, we've successfully bypassed network controls by routing traffic through a specific location (cloud provider, geo-location). Today, we're releasing Newtowner, to help test for this issue: https://t.co/X3dkMz9gwK
Hello fellow hackers,
I decided to create a GitHub repo that contains different varieties of security-related articles such as bug bounty, penetration testing, etc from @Medium.
Link: https://t.co/216ab5NaMn
[1/3]
Motivation & reason 👇
#BugBounty#infosec#bugbountytips