What Are Crypto Bridges and Why Do They Get Hacked?
Crypto bridges let assets move between blockchains, but their complex design makes them attractive targets for hackers.
Crypto bridges let assets move between blockchains, but their complex design makes them attractive targets for hackers.
A crypto bridge is a set of protocols, smart contracts, and off‑chain components that enable tokens, NFTs, or data to move from one blockchain to another without relying on a centralized exchange. By providing a trust‑less pathway, bridges aim to preserve the decentralized ethos of the ecosystem while unlocking liquidity across multiple networks.
The most common model is the lock‑and‑mint approach: the original token is locked in a contract on the source chain, and a wrapped version—often called a “synthetic” or “pegged” token—is minted on the destination chain. When the user wants to move back, the wrapped token is burned and the original is released. This two‑step process ensures that the total supply of the asset remains constant across chains.
Imagine Alice wants to transfer 10 ETH from Ethereum to Polygon. She sends the 10 ETH to a bridge contract on Ethereum, which records the amount, timestamps the transaction, and emits a standardized event that can be read by off‑chain relayers. Those relayers—often run by a set of validators—monitor the Ethereum blockchain for the lock event, verify that the contract’s state matches the expected parameters, and then submit a proof to a bridge contract on Polygon. Once the proof is accepted, the Polygon contract mints 10 Wrapped ETH (WETH) to Alice’s address on Polygon.
When Alice later decides to move the funds back, she sends the 10 WETH to the Polygon bridge contract, which burns the wrapped tokens and emits a corresponding unlock event on Ethereum. The validators observe this event, create a proof, and the Ethereum bridge contract releases the original 10 ETH to Alice’s Ethereum address. The whole process typically takes a few minutes to an hour, depending on the finality times of the involved chains and the bridge’s security parameters.
Bridges aggregate large amounts of locked value (TVL) in a single contract or a small set of contracts, making them high‑value targets. Because a successful exploit can instantly create or release millions of dollars worth of assets, attackers prioritize bridges over many other DeFi components.
The cross‑chain nature of bridges adds layers of complexity: they must coordinate state between two (or more) independent consensus mechanisms, handle differing finality guarantees, and often rely on off‑chain infrastructure such as relayers, oracles, and validator committees. Each additional component expands the attack surface, giving adversaries more entry points to inject malicious data or compromise private keys.
Smart‑contract bugs remain the most frequent cause of bridge failures. Re‑entrancy flaws allow an attacker to call a contract repeatedly before state changes are finalized, potentially minting unlimited wrapped tokens. Integer overflows or underflows can cause balance calculations to wrap around, again leading to unauthorized minting or draining of assets.
Validator collusion is another critical vector. Many bridges rely on a quorum of validators to sign off on cross‑chain events. If a majority of those validators are compromised—through private‑key theft, social engineering, or bribery—they can fabricate false lock events and trigger the minting of assets that were never actually locked. The Ronin bridge breach demonstrated this when nine out of ten validator nodes were compromised, allowing attackers to approve fraudulent withdrawals totaling $620 million.
**Wormhole (Feb 2022)** – The Wormhole bridge between Solana and Ethereum suffered a $320 million loss when an attacker discovered a missing signature verification in the contract that allowed arbitrary minting of wrapped ETH on Solana. The exploit highlighted the danger of incomplete message authentication and the importance of exhaustive test coverage for every code path.
**Ronin (Mar 2022)** – Operated by Sky Mavis for the Axie Infinity ecosystem, Ronin’s bridge was compromised after attackers obtained the private keys of 5 of the 9 validator nodes. They forged validator signatures to approve withdrawals of 173,600 ETH and 25.5 MATIC, totaling over $600 million. The incident underscored the risk of small validator sets and the need for multi‑sig governance with diverse key custodians.
**Polygon PoS Bridge (Oct 2021)** – A bug in the exit proof verification allowed an attacker to withdraw more tokens than were deposited, resulting in a loss of roughly $600 million worth of assets. The fix required a complete pause of the bridge and a migration to a new, audited contract architecture.
Security‑first bridge projects adopt layered defenses. Formal verification tools such as Certora or VeriSolid can mathematically prove that critical invariants—like “total wrapped supply never exceeds locked supply”—hold under all possible inputs. Regular third‑party audits from reputable firms (e.g., OpenZeppelin, ConsenSys Diligence) provide independent scrutiny of the code base.
Decentralizing the relayer/validator network is equally vital. Using threshold signatures (e.g., BLS signatures) means that no single key can authorize a cross‑chain event; a predefined number of independent participants must cooperate. Additionally, employing multi‑chain finality gadgets—like Polkadot’s GRANDPA or Ethereum’s Casper—helps ensure that a transaction is truly final on the source chain before it is acted upon on the destination chain.
Even the most secure bridge can be compromised, so users should follow a defensive mindset. Start by transferring only the amount needed for a specific transaction and keep the bulk of assets on their native chain where the security model is better understood. Test the bridge with a small amount (e.g., 0.01 ETH) before moving larger sums; this helps verify that the bridge is operational and that the address you’re sending to is correct.
Research the bridge’s security posture: look for recent audit reports, the number of active validators, and community sentiment on platforms like Discord or Twitter. Bridges that publish real‑time validator signatures or have transparent governance dashboards make it easier for users to spot anomalies.
Lock‑and‑mint bridges lock the original token on the source chain and mint a wrapped version on the destination chain, while liquidity‑pool bridges use pooled assets to provide instant swaps without locking the original token.
No bridge can guarantee absolute security; however, using audited contracts, decentralized validators, and layered safeguards can significantly lower the risk of a successful hack.
Unusual spikes in minting activity, delayed finality, or announcements from the bridge team about emergency pauses are common warning signs of a potential compromise.
Centralized exchanges handle the conversion internally and hold custody of assets, which removes the technical risk of a bridge but introduces custodial risk and reliance on the exchange’s security practices.
This guide is general information from the COINMAG newsroom, not financial advice.
Discussion 0