- July crypto losses climbed to $210.3 million across 30 recorded incidents.
- The COLDCARD firmware flaw became the third-largest crypto theft of the year.
- The biggest exploits hit hardware, developer machines and oracles rather than smart contract code.
- AFX Trade offered its attacker a share of the stolen funds to return the rest.
Where July’s $210.3M went
Bar length scaled to the largest loss. Estimates from PeckShield, Blockaid and Halborn.
The COLDCARD sweep drained $30 million in ten minutes
AFX Trade lost control of its bridge through a fake job offer
Once inside the development environment, the attacker pulled the keys behind the bridge’s hot validators. Five validator signatures were enough to meet the roughly two-thirds threshold the bridge required, so the smart contract read the withdrawal as entirely legitimate and executed it on command. Nothing had to be broken. AFX Trade then did what a growing number of protocols now do after a breach: it offered the thief a 30% bounty worth about $7.2 million in exchange for returning the other 70%.
How Ostium’s attacker wrote Bitcoin down to $5,000
Ostium’s $23.75 million loss came from its price feed. The attacker got hold of a private signing key for one of the platform’s oracles and pushed future-dated timestamps through a registered forwarder called PriceUpKeep. That let them write a false Bitcoin price of $5,000 into the contract, open heavily leveraged positions against that fiction, and then settle them at the real market price near $60,000. The gap became pure profit, paid out of the platform’s liquidity vault to positions that never earned it.
BONK DAO voted its own treasury away
The BONK DAO incident on Solana skipped the code entirely. There was no bug to exploit. The attacker spent about $4 million buying BONK on exchanges, then used that stake to control almost the entire vote. Turnout was so thin that wallets tied to the attacker made up roughly 99.9% of the votes cast, and the proposal moving about $20 million of treasury tokens to their own wallet passed cleanly. Every step was valid under the DAO’s own rules. The theft was legal in the narrow sense that the protocol worked exactly as written.
The random number generator was bypassed, entropy on the drained Mk3 devices fell to about 40 bits, and private keys became reconstructible by brute force.
A fake recruiter’s malicious repo compromised a developer’s machine; stolen validator signatures cleared a bridge withdrawal the contract read as legitimate.
A stolen signing key wrote Bitcoin down to $5,000, opened leverage, and settled near $60,000 out of the liquidity vault.
Attackers bought enough BONK to swing the DAO and passed a proposal that emptied the treasury into their own wallets.
Audits stopped being where the money leaks
What a firmware flaw does to the self-custody case
The COLDCARD breach lands hardest on retail holders who chose hardware wallets precisely to avoid trusting anyone else. If a foundational chip or firmware error can undo perfect personal security, the argument for holding your own keys weakens for anyone without the technical depth to audit their own device. That pressure points in one direction for part of the market, toward regulated custodians and spot Bitcoin ETFs, where the security burden sits with an institution rather than the individual.
Protocols now budget for paying attackers back
The AFX Trade offer is becoming standard practice rather than an exception. Negotiating the return of stolen funds has moved from rare improvisation into written incident-response plans, and some firms now treat a percentage payout to attackers as a recovery cost. What no one has settled is the legal status of those payments. US and European regulators have not drawn a clear line between a ransom and a lawful settlement, and how they eventually classify a bounty paid to a known thief will decide whether the tactic that saved AFX Trade most of its money stays available to the next protocol that needs it.
