Here We go .
Write-up For Critical Bug is now available you can read it here 🔥
https://t.co/nU8S1dNlGZ
Show me some support & Follow Me to Stay updated with more Findings
Most people don’t realize how little real competition there is in bug hunting.
A huge part of the younger generation is focused on gaming, while others spend most of their time scrolling Instagram, TikTok and similar platforms. Even within tech, a lot of people are tied up in web development, chasing projects, clients or frontend trends.
And now with AI in the picture, many beginners get discouraged before they even start, thinking everything is already saturated or automated.
But the reality is very different. The field is still wide open.
If you stay consistent, actually learn the fundamentals and put in real effort, you’re already ahead of most people. The barrier to entry is much lower than it looks, and very few people are willing to go deep enough to stand out. That’s where the opportunity is.
Take advantage of it. Build your skills. Stay focused. This space can genuinely change your life if you take it seriously.
Much like Amass, a lot of people don't use Nmap to its full potential. Here's a bunch of tips on how I use actually use Nmap.
If you get something out of this article, share it!
https://t.co/QzobV6hYhe
I get tagged from beginners on how to start. If you’re a complete beginner, you need to understand how HTTP works, period. Let go of the tools and exploits and read the RFC. https://t.co/79v4SBHvzp. This is a must.
conteúdos que leio que melhoraram MUITO meu bug Bounty/Pentest
melhores reports reunidos por um hacker ref no Brasil:
https://t.co/2Ku47OC4ZB
pensamento MUITO fora da caixa, absurdo:
https://t.co/qNyecj4mHw
roadmap e dicas:
https://t.co/pgW0oQCQXz (https://t.co/wbn9xudryT)
Few days ago I got $4500 for an IDOR in a program and I made an EXACT vulnerable challenge on that, it requires understanding the application's architecture and having a hacker's intuition. Instead of fuzzing blindly, focus on how the app works, go go:
https://t.co/daVHK9g9xb
Want to learn AI / LLM Security Assessment? Don't have the money for a training?
Here are 🎯SEVENTY ONE🎯 FREE LLM security labs that we have curated for you!
Like and share! (Link Below)
<3 from @arcanuminfosec
A $3,250 OAuth Crit. This was so basic, surprising how no one found it on the main site.
The team recognized it and fixed it in 24hrs.
Taking my time to finish the writeup. For now, you can read my:
$2,000 web cache deception: https://t.co/CAxfKAC0eP
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!