HackenProof

6.3K posts

HackenProof banner
HackenProof

HackenProof

@HackenProof

Expert web3 bug bounty and crowdsourced audit platform with 350 programs and over 22 million in bounty DS: https://t.co/yl9Srpv70J

Start bug bounty journey → Katılım Mayıs 2018
2.2K Takip Edilen38.1K Takipçiler
Sabitlenmiş Tweet
HackenProof
HackenProof@HackenProof·
Security is a public good — and now the community can help fund it. We’re proud that HackenProof is part of the Ethereum Security QF Round by @thedaofund, hosted on @Giveth — a 500 ETH matching pool supporting people and projects working to make Ethereum and its L2 ecosystem safer. Quadratic funding means it’s not only about how much is donated, but also how many people support a project. So even a $1 donation can help strengthen the signal behind HackenProof. By supporting HackenProof, you support bug bounty research, whitehat hackers, and continuous security work across Ethereum and L2s. Donate by May 14: qf.giveth.io/project/open-s… Repost to help more people support Ethereum security. #HackenProof #EthereumSecurity #BugBounty #QuadraticFunding #Web3Security
HackenProof tweet media
English
0
2
27
1.5K
HackenProof
HackenProof@HackenProof·
Spot the Bug 🧠 Merkle reward claiming Two bugs in this one. Can you find both?👇
HackenProof tweet media
English
23
6
65
4.8K
HackenProof
HackenProof@HackenProof·
The minimum share protection had one flaw. It blocked supply between 1 and MIN_SHARES. It didn't block supply dropping to exactly 0. Full breakdown on the HackenProof blog: hackenproof.com/blog/for-hacke…
English
0
2
7
476
HackenProof
HackenProof@HackenProof·
The attack chain: 🔸 100 ETH sent → unvested, invisible to totalAssets() 🔸 Last user exits → totalSupply() drops to 0 🔸 Dust deposit → shares minted 1:1 🔸 Vesting completes → totalAssets() jumps 🔸 Attacker redeems → full yield stolen
English
1
1
9
735
HackenProof
HackenProof@HackenProof·
Most pentesters overlook the gap between actual balance and accounting balance. In ERC4626 vaults with linear vesting, that gap can become an attack surface. A dust deposit → major reward capture. Here’s how 👇
HackenProof tweet media
English
3
4
24
1.2K
Sainath More
Sainath More@sainathm501·
Another one on the board $250 bounty this time. Small steps, but consistent progress in Web3 security. Same me. Just more learning, more patience, more consistency. This journey is just getting started. More coming..... @HackenProof
Sainath More tweet media
English
5
0
50
671
PERK
PERK@PERK_FUND·
Our team needs to speak to somebody @HackenProof immediately. We found a vulnerability that puts millions of dollars of funds at risk. Time is of the essence!!!!
English
9
18
45
4.1K
HackenProof
HackenProof@HackenProof·
What is the best social media for bug bounty hunters community?
English
20
2
59
4.7K
🧪 cryptoleks
🧪 cryptoleks@durdom_evm·
@HackenProof github, hackerone forums, and twitter are where the actual discussions happen. reddit's r/bugbounty is decent for beginners but the serious hunters coordinate elsewhere
English
1
0
6
359
0Zeta
0Zeta@0zSchnack·
There’s quite a memorable story behind one of the vulnerabilities. Almost three years ago, I first looked at this codebase. I still remember the strange gut feeling I had while trying to wrap my head around one particular component. I spent days looking for a flaw, some slight deviation from the intended behavior, but came up empty. Still, I couldn’t quite let it go. Over the following years, I kept occasionally coming back to the same file, mostly during holidays: reading line after line, hand-crafting payloads, writing fuzzers, running automated scans, and later consulting my favorite AI agents, all of which tried to convince me the logic was bulletproof. Not only did I not find any vulnerability, I didn’t even find a non-security-relevant bug. But that feeling of suspicion never went away. After getting home from a New Year’s party in the early hours of January 1, 2026, and not quite ready to call it a night, I decided to give it one more shot. For some reason, it finally clicked, and I spotted a very subtle interaction I had overlooked for years. 137 hours later, on very little sleep, I submitted the final piece of the working PoC. The hunt for the one that almost got away was over. Interestingly, the bug made a brief reappearance when the same pattern turned up in a few other projects later. No big bounties, though. P.S.: Don’t do this. Sunk cost fallacy is real. Huge thanks to the teams of the affected project(s) for demonstrating their commitment to security with smooth and fair bounty payments. I’m also very grateful to the entire @HackenProof team for their great work as always, and especially to @d0rsky and @Striukovskyi for their excellent support over the past years!
HackenProof@HackenProof

A $225K bounty win for @0zSchnack 🫡 Not one, not two, but three $75K payouts — an impressive streak. HackenProof salutes you. Keep hunting 🔥

English
15
4
126
5.2K
HackenProof
HackenProof@HackenProof·
A $225K bounty win for @0zSchnack 🫡 Not one, not two, but three $75K payouts — an impressive streak. HackenProof salutes you. Keep hunting 🔥
HackenProof tweet media
English
4
9
162
9.3K
Mr Owl
Mr Owl@ziko29504803·
@HackenProof more reports more findings more triaged more bounties
English
1
0
1
26
HackenProof
HackenProof@HackenProof·
| ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| More bugs, more rewards |______________| \ (ᵔᴥᵔ) / \ / --- / \ _| |_
English
8
0
44
1.1K
Zer0day Sec 🗡
Zer0day Sec 🗡@Zer0day_sec·
@HackenProof | ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| Less sleep, more bugs |______________| ᕙ(⇀‸↼‶)ᕗ \ / / \ | |
English
1
0
3
55