bugoverflow retweeted
Let’s set the record straight: @lcfr_hax was the first to discover php2shell and develop a working exploit. See his August 5 tweet: nitter.gq/lcfr_hax/status/208503…
His work convinced the PHP Foundation to invest in fixing this entire bug class. He then worked around the clock to review, test, and retest the patches.
bugoverflow retweeted
Whoever created this, huge respect.
webhacklist.com/
bugoverflow retweeted
Thank you @Bugcrowd @inspectiv @Hacker0x01 ❤️🔥
This video is for those who think their life can’t change from where they are.
bugoverflow retweeted
I started Bug bounty back in December 2022, took me almost 1.5 years to get my first bounty in March 2024 of 3 digits, then a 4 digit bounty in May 2024.
Now here we are in September 2026 to get a 5 digit bounty.
We have come a long way my people.
bugoverflow retweeted
⚡ Advanced Bug Bounty Tip
One of the biggest time sinks in bug bounty is manually reviewing JavaScript.
Instead of reading hundreds of files, automate the discovery phase.
I built Mass PII & Secret Finder to do exactly that:
🔍 Features:
• Crawls the entire target
• Discovers JS files (chunks, sourcemaps & dynamic imports)
• Extracts hidden API endpoints
• Detects 90+ secret & PII patterns
• Finds hardcoded JWTs, API keys, cloud credentials, emails, tokens & more
The tool doesn't find bugs for you.
It finds the places where bugs are most likely to exist, so you can focus on validation and exploitation instead of endless manual review.
🚀 Mass PII & Secret Finder: github.com/kanishk-dadhich/R…
#BugBounty #AppSec #CyberSecurity #InfoSec #Recon #JavaScript #OSINT #BugBountyTips
bugoverflow retweeted
GitHub - uphiago/recon-skills: 144 offensive security skills for recon and pentest. Field-validated techniques from 600+ targets across 45+ sectors. Updated with web enum, email sec, google dorks, cloud IAM, WordPress full compromise chains. · GitHub github.com/uphiago/recon-ski…
bugoverflow retweeted
made a tool that maps every HackerOne bug bounty program to its github repos (116+ programs).
github.com/actuallyclover/so…
#bugbounty #tools #opensource
bugoverflow retweeted
AMA by an ex-H1 triager.
An interesting read.
reddit.com/r/bugbounty/comme…
h/t @zseano
bugoverflow retweeted
If you use Nuclei for bug bounty or recon, this repo is a goldmine.
Source: github.com/emadshanab/Nuclei…
It aggregates hundreds of public/custom Nuclei template repos in one place:
• CVEs
• SSRF
• SSTI
• XSS
• Takeovers
• WAF detections
• Fuzzing templates
• API checks
• and much more.
A very useful resource for expanding your custom scanning workflow and discovering community templates you probably missed. 🔥
#bugbounty #cybersecurity #appsec #infosec #nuclei #hacking
bugoverflow retweeted
SQL Injection without these special chars [' "()\/%*&\`] possible?
Yep, me and @or4nge16hehe did it.
Using only: [ a-z, 0-9, dot, @+- ]
Write-up soon
#BugBounty #infosec
bugoverflow retweeted
i'm taking a pause from hacking to resume building bugbountyhunter.com. i regret closing it down and I shouldn't of done it. everything will be back online EXACTLY as it was very soon and i've got some big plans for the future. and yes, that includes zseano methodology v2 ;)
bugoverflow retweeted
Decided to do a write up after a very long time if anyone’s interested let me know 👀👀
Will Drop in sometimes, the issue is still open so probably will wait sometime.
All the endpoint, Param and Backend details are not real for the security reasons 🥸
bugoverflow retweeted
ًWrite-up is now available
you can read it here
medium.com/@youssefmohamedsa…
Follow Me to Stay updated with more Findings
bugoverflow retweeted
Just dropped Part 1 of my Recon series on Medium 🚀
I’ll be sharing my methodology + tips & tricks that helped me find real bugs and earn $$$$$
link: medium.com/@NeM0x00/the-art-…
More parts coming.
#bugbountytips #bugbounty #bughunting
bugoverflow retweeted
Spending so much time on a single program ( 3 months, 1-2yrs, name it e.t.c ), will teach you far more techniques than focusing on random programs...
How has this helped me ? I've been on a program for 6 months now, the couple of weeks I realized that some assets are running behind a known CMS ( called "Directus" ), which is vulnerable to info leak & arbitrary file overwrite, I sent all reports in and they'll got accepted... the interesting part of this is that every assets of the target, with the prefix "cms.", is vulnerable..
The more time you spend on your target or understanding your target, the more the attack surfaces, the more the vulnerabilities.
bugoverflow retweeted
I Saved Injective's $500M. They Pay Me $50K.
I like hunting bugs on @immunefi . I'm decent at it.
- #1 — Attackathon | Stacks
- #2 — Attackathon | Stacks II
- #1 — Attackathon | XRPL Lending Protocol
- 1 Critical and 1 High from bug bounties (not counting this one)
Life was good. Then I found a Critical vulnerability in @injective .
This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk.
I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity.
Then — silence. For 3 months. No follow up. No technical discussion. Nothing.
A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either.
I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten.
I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve.
Full Technical Report: github.com/injective-wall-of…
