Root Cause and Technical Vulnerability
Published 7/13/2026, 9:45:36 PM
On July 11, 2026, Bonzo Lend, the largest lending protocol on the Hedera network, suffered a $9.05 million exploit that resulted in a 77% collapse of its Total Value Locked (TVL) [Source: https://x.com/ilmeaalim/status/2075905177203417317, https://x.com/shuigvn/status/2076324120774778954]. The incident was caused by a critical cryptographic vulnerability in the Supra oracle's on-chain verifier, which allowed an attacker to manipulate asset prices and drain the protocol's liquidity.
Root Cause and Technical Vulnerability
The exploit stemmed from a signature verification failure within the Supra oracle's requireHashVerified_V2 contract on the Hedera network [Source: https://supra.com/id/news/security-incident-report-hedera-pull-oracle-verifier/].
The attacker exploited a "point at infinity" edge case in the BLS signature scheme:
- Zeroed Signature: The attacker submitted a price update for the SAUCE token using a zeroed BLS signature
[0,0][Source: https://x.com/ilmeaalim/status/2075905177203417317]. - Precompile Failure: Hedera’s pairing precompile (system contract
0.0.8) incorrectly returned a "true" value when validating this zeroed signature against a committee public key that also resolved to zero [Source: https://x.com/ilmeaalim/status/2075905177203417317]. - Price Manipulation: This bypass allowed the attacker to inflate the price of SAUCE by approximately 12 orders of magnitude (from ~0.2 HBAR to a value represented by 1 followed by 30 zeros) [Source: https://x.com/bpaynews/status/2075912941124157778].
Impact on Bonzo Lend
With the collateral value of SAUCE artificially inflated, the attacker was able to borrow massive amounts of liquidity against a negligible deposit.
| Metric | Value / Impact |
|---|---|
| Total Loss | $9.05 Million [Source: https://x.com/ilmeaalim/status/2075905177203417317] |
| Assets Stolen | 6.63M USDC and 34.5M wHBAR [Source: https://x.com/ilmeaalim/status/2075905177203417317] |
| Collateral Used | 250 SAUCE tokens [Source: https://x.com/ilmeaalim/status/2075905177203417317] |
| TVL Impact | 77% Decrease [Source: https://x.com/shuigvn/status/2076324120774778954] |
| Protocol Status | Lending and Points paused; Vaults and Staking operational [Source: https://x.com/ilmeaalim/status/2075905177203417317] |
Lessons for DeFi Protocols
The Bonzo Lend exploit provides several actionable security lessons for the broader DeFi ecosystem:
- Oracle Redundancy: Protocols should avoid relying on a single oracle provider. Implementing a multi-oracle solution (e.g., combining Chainlink, Supra, and a Time-Weighted Average Price/TWAP) can prevent a single point of failure from compromising the entire system [Source: https://x.com/ilmeaalim/status/2075905177203417317].
- Sanitize Cryptographic Inputs: Smart contracts must explicitly validate signatures to ensure they are not "zero" or "point at infinity" values, especially when interacting with low-level system precompiles that may handle edge cases inconsistently [Source: https://supra.com/id/news/security-incident-report-hedera-pull-oracle-verifier/].
- Implement Circuit Breakers: Protocols should deploy automated "sanity checks" or circuit breakers that pause borrowing or liquidations if an oracle reports a price deviation beyond a reasonable threshold (e.g., >10% in a single block) [Source: https://x.com/bpaynews/status/2076324120774778954].
- Borrow and Supply Caps: Setting conservative limits on how much can be borrowed in a single transaction or by a single account can limit the "blast radius" of an exploit, even if the underlying price data is compromised.
- Full-Stack Auditing: Security audits must look beyond the protocol's own smart contracts to include the specific implementation details of third-party dependencies and the underlying blockchain's system contracts (precompiles) [Source: https://x.com/ilmeaalim/status/2075905177203417317].
While Supra has since deployed a fix to the affected verifier contract on Hedera, the incident remains a stark reminder that even "verified" external data can be a vector for catastrophic failure if not handled with multiple layers of defense [Source: https://supra.com/id/news/security-incident-report-hedera-pull-oracle-verifier/].