Cross-Chain Bridge Exploits
Real collateral on one side, a claim on the other. When verification breaks, the claim wins.
Every bridge is the same promise in different code: lock value here, mint a claim there, and let a verifier swear the two match. The verifier is the entire security model, and it is usually the least reviewed component in the stack.
The exploits collected here are failures of proof, not of cryptography — a message accepted without validation, a DVN that signed what it should have refused, a router that trusted its caller. Each case shows the exact line where the promise stopped being enforced.
How it works
Lock and mint
Collateral sits on chain A. Chain B mints a representation of it. Solvency depends entirely on the two staying in sync.
The verification gap
A forged message, a quorum that can be reached alone, or a missing check lets chain B mint without chain A ever locking.
The cash-out
The phantom asset is swapped against real liquidity within minutes, then bridged onward before governance can pause anything.
Investigations in this vector
Aztec Router Hack: $2.19M Drained From The Bridge
Aztec's Ethereum Router released $2.19M with no L2 deposits behind them — a proof-vs-settlement mismatch in an unpausable contract.
Read the investigationDrift Hack: $285M Drained From The Vault in 12 Minutes
A fake DRIFT token forged a CarbonVote tally, seized vault authority and moved $285M in 12 minutes. The transaction-by-transaction breakdown.
Read the investigationKelpDAO + LayerZero: $292M Lost to a 1-of-1 DVN
A compromised LayerZero DVN released 116,500 rsETH (~$292M) from KelpDAO's bridge. LayerZero and Kelp dispute who chose the 1-of-1 setup.
Read the investigationHyperbridge $1.2B Fake DOT: The Unchecked Mint Function
A missing access-control modifier let an attacker mint $1.2B of unbacked DOT on Ethereum via Hyperbridge. Full kill chain plus $237k Uniswap dump.
Read the investigationCrossCurve Bridge Hack: $3M Stolen in 15 Minutes [2026]
One fake message. Zero validation. $3M drained across 3 chains in a single tx. The audit passed — the bridge didn't. See the exact exploit flow inside.
Read the investigationIoTeX Bridge Hack: How 1 Leaked Key Drained $8.8M [2026]
One validator key leaked. $8.8M gone in minutes. The IoTeX ioTube bridge had zero failsafes.
Read the investigationRed flags
- The bridge's verifier set is small, permissioned, or run by the same team as the bridge.
- Upgrade keys are a single multisig with a low threshold and no timelock.
- Total value locked greatly exceeds the size of the last audit's scope.
- Wrapped supply on the destination chain has drifted from locked collateral.
- Incident communications arrive hours after on-chain sleuths already published.
If it already happened
- 1.Exit wrapped positions before the peg follows the news — depegs are fast.
- 2.Withdraw approvals to the bridge router; exploited routers are re-used.
- 3.Track the official post-mortem for a reimbursement snapshot block, and keep proof of your position at that block.
- 4.Do not trust 'recovery portals' announced in replies — they are the second wave of the same attack.
Related vocabulary
Got a suspicious message, link or token?
Paste it into the free detector. No signup, no cost, answer in seconds.