Bonzo Finance, a DeFi lending protocol on Hedera, lost a reported $9.05 million on 2026-07-14 after its Supra price oracle accepted a zeroed cryptographic signature validated against a zeroed key. The verifier returned "valid" because the underlying math holds for the zero case, and no non-zero constraint was enforced. The loss figure is an early estimate from rekt.news and may change as the postmortem firms up.
TL;DR: An oracle verifier accepted a zero signature against a zero key, so the check passed trivially. That let an attacker feed manipulated prices into a lending protocol and drain a reported $9.05M. Hedera and the core signature scheme were not "broken" — the verifier missed a non-zero check.
What actually happened
An oracle is the piece of infrastructure that tells a DeFi protocol what an asset is worth. Lending protocols like Bonzo Finance rely on that price feed to decide how much you can borrow against collateral and when to liquidate positions. If the price feed lies, the protocol acts on the lie.
According to the rekt.news report (retrieved 2026-07-14), Supra's oracle verifier accepted a signature of zero checked against a public key of zero. In many signature schemes the verification equation is satisfied trivially when both inputs are zero — zero equals zero — so the check returned valid without a genuine signer.
The missing guard was a non-zero constraint on the key and signature. With that guard absent, an attacker could submit a forged "valid" price and push manipulated data into the protocol. The result was a reported $9.05M drained. Treat that number as provisional until a formal postmortem lands.
Why the distinction matters
This was not a break in Hedera's ledger or in the cryptography itself. The signature math worked as specified; the verifier failed to reject a degenerate input the math never promised to reject.
That pattern recurs across DeFi incidents: the core primitive is sound, but a validation layer trusts an input it should have rejected. It echoes recent Safe-module drains and oracle-manipulation cases, where the exploit lived in the coordination or verification layer, not the base protocol.
For users, the practical lesson is about exposure surface. A DeFi lending protocol has an oracle, a shared pool of deposited funds, and liquidation logic. Each is a place where one bad assumption can cascade into everyone's balance.
What it means for no-KYC swap users
If you swap coins rather than lend or farm them, your exposure to this class of bug is different. A price-feed manipulation drains protocols that hold pooled funds and price them against an oracle. A one-shot swap that routes your coins from one wallet to another has no ongoing position to liquidate and no oracle deciding your collateral ratio.
That does not make swapping "safe" in the absolute — every service has attack surface, and floating-rate pricing carries its own trade-off. But the shape of the risk is different: there is no shared lending pool holding your balance while an oracle decides its fate.
| Attribute | DeFi lending protocol | GhostSwap swap |
|---|---|---|
| Funds custody | Deposited into a shared pool | Non-custodial — funds pass through, never held |
| Price oracle | Required for collateral / liquidation | Not used; floating rate at settlement |
| Ongoing position | Yes — subject to liquidation | No — one swap, then done |
| Account / KYC | Wallet connect, sometimes KYC front-ends | None required; no account, no email |
Where GhostSwap fits
GhostSwap is a no-KYC crypto exchange: no account, no email, no signup required to swap. Funds pass through non-custodially — we never hold them. There is no shared lending pool to price, and no oracle deciding whether your collateral gets liquidated, because a swap has neither collateral nor a standing position.
Pricing is floating-rate, drawn from aggregated liquidity from leading crypto markets, so you get the rate at the moment your funds arrive rather than the moment you click. Median completion time is around 8 minutes, though congested chains can push that toward 30. Support spans 1,600+ pairs across BTC, ETH, XMR, SOL and altcoin networks.
None of this makes any system "unhackable." It means the specific failure that hit Bonzo Finance — a manipulated oracle feeding a pooled lending protocol — is not part of a wallet-to-wallet swap's design.
FAQ
Q: Was Hedera hacked in the Bonzo Finance exploit?
A: No. Per the rekt.news report, the failure was in Supra's oracle verifier accepting a zeroed signature, not in Hedera's ledger or consensus. The base cryptography behaved as specified; the verifier missed a non-zero check.
Q: How much did Bonzo Finance lose?
A: A reported $9.05 million as of 2026-07-14, per rekt.news. Treat that as an early estimate — loss figures in the first hours of an incident often shift once a formal postmortem is published.
Q: Does a no-KYC swap use a price oracle?
A: A GhostSwap swap does not rely on an oracle to hold or liquidate your funds. Pricing is floating-rate from aggregated liquidity, applied at settlement. There is no collateral position and no shared pool priced against an external feed.
Q: Is swapping safer than DeFi lending?
A: It is not free of risk — every service has attack surface. But a wallet-to-wallet swap has no shared lending pool and no oracle-driven liquidation, so the specific failure mode behind this incident does not apply to it.
Before you move funds
If you are rotating out of a DeFi position and want to move into Bitcoin or a privacy coin without an account, you can swap without signing up at the live widget, or go straight to a pair like BTC to XMR. For a broader walkthrough, see how to buy crypto.
More detail on the incident is at rekt.news.
