What Happens if a Bridge’s Multisig Signers Collude to Mint Unbacked Tokens?
If a bridge’s multisig signers collude to mint unbacked tokens, the wrapped tokens on the destination chain become worthless or trade at a deep discount. The bridge’s custodial wallet - where the native assets are supposed to be held - will have a shortfall. The colluding signers can mint new wrapped tokens without depositing equivalent native assets, then sell those tokens for real value before anyone detects the fraud. The outcome is essentially a theft: users who hold the wrapped tokens are left with claims against an empty vault.
How multisig collusion works in practice
A lock-mint bridge typically relies on a multisig wallet - a set of signers who must approve transactions. The canonical process is:
- A user deposits native asset (e.g., ETH) into the bridge’s custodial wallet.
- The bridge’s off-chain oracle or relayer observes the deposit.
- A threshold of multisig signers (e.g., 3 of 5) signs a message to mint wrapped tokens on the destination blockchain.
- The wrapped tokens are created and sent to the user’s destination address.
In a collusion attack, the signers skip step 1. They coordinate to sign a minting message for wrapped tokens that have no corresponding native deposit. The minting happens on-chain, and the attacker receives wrapped tokens that appear legitimate - they share the same contract address, the same metadata, and initially trade at the same price.
Immediate consequences for wrapped token holders
Once unbacked tokens hit the market, the damage cascades:
- Price discount. The first sign of trouble is usually a price divergence. Wrapped tokens begin trading below the native asset’s price because informed traders suspect dilution or sell pressure. The discount grows as more unbacked tokens are dumped.
- Liquidity drain. Unbacked tokens can be swapped for other assets on decentralized exchanges. If the attacker sells large amounts, liquidity pools get depleted. Honest users who try to redeem their wrapped tokens for the native asset find the bridge’s redemption queue has no funds.
- Redemption failure. When a user attempts to burn wrapped tokens and withdraw the native asset, the bridge checks the custodial wallet. If that wallet is short, the transaction fails or is stuck in a pending state. The bridge may pause withdrawals entirely.
Detection and Discovery
Collusion is not always obvious immediately. Unlike a smart contract exploit, which leaves an on-chain trail of broken logic, a multisig collusion looks like normal operation - signers approved a mint. Detection often depends on:
- External audits. A proof-of-reserve check by a third party might reveal that the custodial wallet holds fewer native assets than the total supply of wrapped tokens. If the bridge publishes audited reserve data, a discrepancy can surface.
- Whistleblowers. A disgruntled signer or an insider leaks evidence of the collusion.
- Unusual trading patterns. A sudden spike in wrapped token supply, combined with large sales, can tip off exchanges or analytics platforms.
- Regulatory or legal action. Authorities may investigate if the bridge’s operators are registered entities.
What you can do if you hold wrapped tokens
If you suspect a bridge’s multisig has been compromised:
- Check the current supply. Look up the total supply of the wrapped token on a block explorer. Compare it to the amount of native assets the bridge claims to hold. If supply exceeds reserves, the tokens are not fully backed.
- Monitor the bridge’s official channels. The team may issue a statement, pause minting, or announce a recovery plan. Some bridges have emergency keys that can freeze the minting contract.
- Sell or swap immediately if you can. In a panic scenario, the window to exit at a reasonable price may be short. Use decentralized exchanges or peer-to-peer trades. Recognize that you may take a loss.
- Do not deposit more native assets. Any new deposit into the bridge will only increase the pool of funds the colluding signers can drain.
Long-Term fallout and recovery
After a collusion event, the bridge is effectively insolvent. Recovery options are limited:
- Bridge treasury or insurance fund. Some bridges keep a separate pool of capital to cover shortfalls. If that fund is large enough, token holders may be compensated. But insurance funds are rarely enough to cover a full-scale theft.
- Legal recourse. If the signers are identifiable and within a jurisdiction that enforces crypto-related crimes, law enforcement might recover some assets. This process can take years.
- Token re-peg or reissuance. The bridge team might issue a new wrapped token backed by recovered assets, while the old token becomes worthless. This is similar to a chain split: token holders vote on which version to accept.
- Complete loss. In many past incidents, wrapped token holders were never made whole. The native assets were either spent or moved to untraceable addresses.
Why multisig collusion is rare but dangerous
Multisig signers are usually chosen for their reputation and geographic diversity. Collusion requires a majority of them to agree to commit fraud, which is harder to coordinate than a single-party hack. However, the incentives are strong: a single large mint can net millions of dollars. And because the attack looks like normal bridge operation, it can go undetected longer than a code exploit.
The fundamental risk is that a lock-mint bridge is a central point of trust. No amount of smart contract audits can prevent a majority of human signers from breaking their agreement. For users, the only reliable defense is to verify reserves independently - and to treat any wrapped token as only as trustworthy as the people who hold its keys.
Not financial advice. ucit.lol publishes market data and general information about UCIT. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.