This was over a year ago now. Boy-o-boy, how time flies: https://t.co/peagOF5hwU
Thank you again @NotionalFinance for your professionalism in handling this bug.
If you’re a security researcher doing Bug Bounty in blockchain, don’t waste your time reporting it unless it’s a zero-day with no preconditions that can affect millions of dollars today without much effort. If your vulnerability can’t do that, good luck getting a decent bounty honestly even zero-days aren’t guaranteed to be properly paid in today’s economy.
In case you missed it, both LayerZero and Stargate significantly reduced their Immunefi bug bounty rewards:
- LayerZero: Max Critical reward $15M → $3.5M (-77%)
- Stargate: Max Critical reward $10M → $3.5M (-65%). High severity rewards removed entirely.
And that's just today - there were dozens of similar cuts over the past few months.
Security researchers invest their own time hunting for vulnerabilities, often for weeks or months, with no guarantee of getting paid. Cutting rewards makes that risk increasingly difficult to justify.
Meanwhile, the overall number of security researchers is growing, but truly exceptional ones remain rare. Many have more profitable opportunities to pursue, and some are already moving in that direction.
The incentives are clearly shifting in the wrong direction.
If a major protocol suffers a devastating exploit affecting thousands of users, we shouldn't simply dismiss it as bad luck. It will also be a consequence of the decisions made over the past few months.
I filed 3 critical bugs with them.
They confirmed those bugs as valid.
(I teamed up with @0x60511e57 on the last 2 bugs.)
Here’s how it went.
3rd bug: Loss of funds. They awarded 200 SOL while >10M USD was at risk. (wtf)
2nd bug: Chain halt. Was not fixed because the dev
liked his bugs to live longer. Apparently we weren't even the second or third to find it.
They (basically): We know it’s a problem, not gonna pay, and also we won’t fix the bug anytime soon.
Sounds bad?
But ye can get lucky!
My 1st bug with them: Loss of funds. They paid!
So
If you really like:
- uncertainty
- long waits for a response
- them sometimes not giving a shit about fixing bugs
Go for it.
But consider: I got paid on the first bug while I teamed up with @0x60511e57 (#13 Immunefi All Time) on the 2nd and 3rd.
Just..
Imagine:
- how good you must be to match @0x60511e57
- spending your time finding crits
- getting 200 SOL and a "thank you" on an undisputed LoF
Btw: Discount the bounty amount.
1 year lock on that!
If you hunt bugs: Please answer the poll.
What should we do with this codebase?
Cheaply paying the whitehat $250K for a critical infinite XRP supply bug when your treasury has billions?
Thanks for helping ensure the next time an attacker exploits it for 9 figures instead of reporting it in good faith.
This is why people do not take XRPL or Ripple seriously as an org….
the ledger story just got 10x worse
it's not just southeast asia anymore. the same spy chips were just found inside ledgers bought from mediamarkt in europe
two different store locations. same modification. antenna. LTE module. identical setup
these weren't returns. the store confirmed they came directly from the distributor
the distributor? aqipa gmbh. they supply over 1,000 stores across 11 european countries
this means the compromise is happening BEFORE the devices reach the shelves
you walk into a legit electronics store. buy a ledger off the shelf. sealed box. receipt and everything
and there's a spy chip inside it
first it was a compromised reseller in southeast asia
this is no longer an isolated incident. this is a supply chain crisis
We've recently crossed 10,000 paid vulnerability reports on @Immunefi!
That's over 10,000 security issues found and reported before attackers could exploit them.
And over 10,000 reasons why crypto is safer today, thanks to the work of our community of whitehat hackers around the world 🫶
Using one of @bunniestudios's Precursor devices would be a much safer hardware choice than using a Trezor or a Ledger wallet. As long as you vibecode your RNG correctly, that is... 🤣
https://t.co/WYP85tc2Dk
The root cause of this attack stems from @GMX_IO v1's design flaw where short position operations immediately update the global short average prices (globalShortAveragePrices), which directly impacts the calculation of Assets Under Management (AUM), thereby allowing manipulation of GLP token pricing.
The attacker exploited this design vulnerability by leveraging the Keeper's ability to enable `timelock.enableLeverage` during order execution (a prerequisite for creating large short positions). Through a reentrancy attack, they successfully established massive short positions to manipulate the global average prices, artificially inflating GLP prices within a single transaction and profiting through redemption operations.
Haven't disclosed in this style in a while:
SHA256(project-xxxxxxxx-discord-disclosure-msg1.txt)=45bd06cf46663c94391c5800d8f84fb95f32f009018b5d7ec7caaa990747b0d9
SHA256(project-xxxxxxxx-discord-disclosure-msg2.txt)=7d85afc8ed29e28166190dd3384686140fefcdfe677fa8ea0391d7ac52e442ec