Bridge / config · Apr 2026 · $292M · rsETH omnichain bridge
Kelp DAO — $292M — the bridge was audited and clean
Kelp's rsETH omnichain bridge ran on LayerZero, and its contracts had been audited. By every account the code was clean — LayerZero itself later confirmed the contracts “operated exactly as designed.” The problem was never the code.
The bridge shipped with a single-verifier configuration — a 1-of-1 DVN, one attestation source with no redundancy. Attackers compromised the RPC nodes that single verifier relied on and DDoS'd the backups, then injected a forged cross-chain message attesting a deposit that never happened. The lone verifier signed it, and the destination contract released 116,500 rsETH from escrow. It cascaded into roughly $177–190M of bad debt downstream.
This is the defining pattern of 2026: a clean, audited contract, undone by a configuration choice a contracts-only audit doesn't treat as in-scope.
What the audit covered vs. where it broke
Vari's cross-chain layer checks the verifier / DVN threshold as a first-class item — a 1-of-1 configuration is a high-severity single-point-of-failure finding we raise before an attacker finds it. Config is in scope, not just code.
Drift Protocol — $285M — the attackers never touched the contracts
Drift had been audited by multiple well-known firms. The attackers didn't bother with the contracts. Over roughly six months they socially engineered contributors and captured two of five multisig signers.
Using Solana durable-nonce accounts, they pre-signed admin transactions that stayed valid indefinitely, moved admin control to their own wallet, stood up a fake market with an attacker-controlled oracle, disabled the circuit breakers, and drained 15+ assets in about ten seconds.
The code was fine. The operational configuration — a 2-of-5 threshold with no timelock on admin transfers — is what made two compromised signatures fatal.
What the audit covered vs. where it broke
Vari's live on-chain verification reads the deployed multisig threshold and timelock; a 2-of-5 with no timelock is a high-severity centralization finding, and the operational scorecard mandates hardware-key signing and signer separation. We can't stop a phish — but we flag the config that turns one into a $285M loss.
Venus / THENA — correct code, exploited listing
Venus is a heavily audited, Compound-lineage lending protocol. Every unit test passed. The exploit lived in the parameters of a single listed market, not in a broken function.
The attacker donated tokens directly to the vToken to inflate its exchange rate and slip past the market's supply cap, then looped deposits and borrows to push a thin-liquidity oracle price roughly 18× — over-borrowing against collateral that was only briefly worth what the oracle claimed.
Listing a thin-liquidity token with a manipulable price feed, plus a known donation-attack vector, is a configuration and parameter failure — precisely the kind of exploit that passes every code test.
What the audit covered vs. where it broke
Vari's deployment-and-config layer reviews listing parameters as deployed — oracle source and liquidity depth, supply caps, donation-vector exposure on new vTokens — before the market is ever listed.
More breakdowns are published as they happen. 28 incidents analyzed in our full 2026 coverage study.