Incident Overview
Published 7/14/2026, 2:56:11 AM
The Bonzo Finance exploit, which occurred on July 11, 2026, resulted in a loss of approximately $9.05 million from the Hedera-based lending protocol [Source: https://x.com/ilmeaalim/status/2075905177203417317]. The incident was not caused by a failure in Bonzo's core lending logic, but rather by a critical cryptographic vulnerability in the Supra pull-oracle verifier [Source: https://supra.com/news/security-incident-report-hedera-pull-oracle-verifier/].
Incident Overview
The attacker exploited a flaw in how the Supra verifier contract handled BLS signatures on the Hedera mainnet. By submitting a forged price update for the SAUCE/wHBAR pair, the attacker inflated the value of their collateral by 12 orders of magnitude, allowing them to drain the protocol's liquidity [Source: https://x.com/ilmeaalim/status/2075905177203417317].
| Metric | Details |
|---|---|
| Total Loss | ~$9.05 Million [Source: https://x.com/ilmeaalim/status/2075905177203417317] |
| Assets Stolen | 6.63M USDC & 34.5M WHBAR [Source: https://x.com/ilmeaalim/status/2075905177203417317] |
| Root Cause | Oracle BLS Signature Verification Failure [Source: https://supra.com/news/security-incident-report-hedera-pull-oracle-verifier/] |
| Attacker Collateral | 250 SAUCE tokens [Source: https://x.com/ilmeaalim/status/2075905177203417317] |
| Protocol Status | Bonzo Lend & Points Paused; TVL dropped ~77% [Source: https://x.com/shuigvn/status/2076324120774778954] |
Technical Vulnerability Analysis
The exploit targeted the requireHashVerified_V2 function in the Supra verifier contract.
- Forged Signature Acceptance: The attacker submitted a price update with a zeroed BLS signature field
[0,0][Source: https://supra.com/news/security-incident-report-hedera-pull-oracle-verifier/]. - Precompile Flaw: The verifier incorrectly validated this zeroed signature via Hedera's pairing precompile (system contract
0.0.8). Because both the signature and the public key resolved to the "point at infinity," the cryptographic check returnedtruedespite the absence of a valid signature [Source: https://supra.com/news/security-incident-report-hedera-pull-oracle-verifier/]. - Price Manipulation: This allowed the attacker to overwrite the on-chain price of SAUCE (normally ~0.2 HBAR) with an arbitrarily high value, enabling the massive over-collateralized borrow [Source: https://x.com/ilmeaalim/status/2075905177203417317].
DeFi Security Lessons
The Bonzo Finance incident highlights several systemic risks for DeFi developers and users:
- Oracle Risk is Systemic: Even audited protocols are vulnerable if their "trusted" data inputs are compromised. Security is only as strong as the weakest link in the data supply chain [Source: https://supra.com/news/security-incident-report-hedera-pull-oracle-verifier/].
- Defense in Depth for Price Feeds: Relying on a single oracle provider creates a single point of failure. Best practices suggest implementing multi-oracle consensus or sanity checks (circuit breakers) that pause the protocol if a price deviates by an unrealistic percentage in a single block [Source: https://x.com/ilmeaalim/status/2075905177203417317].
- Validation of Third-Party Precompiles: Cryptographic assumptions regarding system-level precompiles (like BLS pairing) must be rigorously tested for edge cases, such as "point at infinity" inputs, which can bypass standard validation logic [Source: https://supra.com/news/security-incident-report-hedera-pull-oracle-verifier/].
- Rapid Incident Response: Bonzo successfully paused the protocol within 45 minutes of the exploit, preventing further losses. The incident also saw a white-hat responder (Wallet B) secure approximately $1M during the attack to protect it from the exploiter [Note: not independently confirmed] [Source: https://x.com/ilmeaalim/status/2075905177203417317].
The exploit serves as a reminder that "secure" smart contracts can still be drained if the underlying infrastructure or external dependencies contain hidden cryptographic flaws.