What do the biggest crypto bridge hacks teach about bridge risk?
Biggest crypto bridge hacks teach one clear lesson: a few stolen keys or one verification bug can drain a bridge’s backing and put every wrapped token at risk.
iCrypto Editorial5 min read
The biggest crypto bridge hacks teach that a bridge can put a large pool of locked assets behind a small set of keys or verification code. If attackers control enough keys—or exploit a flaw in the code—they can release assets or mint tokens without backing, putting every holder of those wrapped tokens at risk.
How a bridge turns a deposit into a token on another chain
A lock-and-mint bridge moves value in three steps: you lock tokens on the source chain, validators or code verify the deposit message, and the destination chain mints wrapped tokens. Those tokens can be redeemed only while the bridge’s pool and release logic remain sound. Bridges often hold a central pool of funds, which helps explain why they have become a major target for crypto theft.
Say you move an asset into a DeFi app on Berachain. The Berachain bridge is a cross-chain asset bridge used to transfer assets into Berachain’s DeFi ecosystem. It helps make assets available on that chain; the wrapped token still depends on the bridge’s pool or mint logic for its backing.
Different bridges verify deposits in different ways. Some rely on a group of validators signing off on a transfer; others rely on smart-contract checks. LayerZero is one name readers may encounter in cross-chain messaging. The design details vary, but the core question stays the same: what evidence must the destination chain accept before it releases or creates tokens?
Three major hacks exposed three ways that check can fail
The Ronin, Harmony Horizon, Wormhole and Nomad attacks show three main failure types: stolen validator keys, signature-verification bugs and faulty contract initialization.
Ronin’s March 2022 attack was a key-compromise failure. Attackers gained control of five of the bridge’s nine validator keys, enough to approve withdrawals. The FBI attributed the theft to North Korea’s Lazarus Group. The lesson is that a nominally multi-key system can still have a single point of failure if too few keys can authorize a release, or if those keys are not kept sufficiently independent.
Harmony Horizon showed the same risk in a smaller multisig: two of five signatures could approve a transaction. When attackers controlled enough signing power, they could authorize withdrawals. A multisig reduces reliance on one key, but the threshold matters. So does whether the people or systems holding the keys can be compromised together.
Wormhole’s February 2022 exploit exposed a code flaw. A signature-verification bug on Solana let an attacker bypass the check and mint about 120,000 wETH without a matching deposit. The lesson is that a bridge must verify the origin and validity of every message before minting. A small mistake at that step can turn a claimed deposit into unbacked tokens.
Nomad’s August 2022 attack was a faulty-initialization failure. An upgrade left a zero root marked as valid, so the contract accepted messages that should have failed verification. After the first exploit transaction, hundreds of copycat addresses replayed it to withdraw funds. Nomad shows how an initialization error can change the rule for every message, and how a public exploit can spread once anyone can repeat it.
Wrapped tokens carry bridge risk after the transfer
A wrapped token stays exposed to its bridge’s backing for as long as it exists. If attackers drain the locked pool, the token can lose that backing even if its current holder never used the bridge during the attack. Buying or receiving a wrapped asset later does not erase the risk created when the bridge was compromised.
In practice, that means checking more than the token’s price or the DeFi app where you plan to use it. Find out which bridge issued the asset, how it verifies deposits, and how many independent keys can approve withdrawals. An audit can help you understand what code was reviewed, but it cannot by itself guarantee that keys remain secure or that later upgrades preserve the same protections.
The central design trade-off is straightforward: bridges make assets usable across chains, but they add another system that must correctly verify transfers and safeguard backing. Large locked pools attract attackers; a small validator threshold or a broken verification rule can let them reach that pool. The incident type tells you where to look: key custody and approval thresholds, message verification, or contract setup and upgrades.
Bridge hack questions readers ask
Are burn-and-mint bridges safer than lock-and-mint bridges?
Not automatically. Burn-and-mint bridges avoid a pool of locked tokens in the same way, but the destination mint still depends on correct verification and secure authorization. The bridge’s full design determines its risks.
Were Ronin users repaid after the hack?
Yes. Ronin announced that affected users were reimbursed after the attack. Repayment addressed user losses, but it did not change the lesson about how validator keys were compromised.
How can I check whether a bridge has been audited?
Look for audit reports from the bridge itself or the auditor, and check which contracts and versions were reviewed. Also check whether the bridge has changed since the audit; a report on older code may not cover the contracts currently in use.
Do bridge aggregators add extra hack risk?
They can add another layer to understand because an aggregator routes transfers through underlying bridges or services. Before using one, check which route it selects and which bridge’s security model backs the asset you receive.
A token moved through the Berachain bridge remains backed by that bridge’s pool or mint logic. Holding bridged assets on Berachain therefore means holding the bridge’s risk, even when the transfer happened earlier or someone else made it.