How the Nomad Bridge Hack Became Mass Looting

On August 1, 2022, attackers exploited Nomad, a cross-chain bridge, and withdrawals quickly spread across many addresses. The stolen amount was reported at about $190 million, with some reports putting it near $191 million. Assets taken included ETH and USDC, and the bridge connected networks including Ethereum, Avalanche, Evmos, Milkomeda C1 and Moonbeam.

This was not one attacker breaking into a wallet and emptying it. A flaw let people submit messages that appeared valid to the bridge, and other users began copying successful withdrawal transactions. Many changed the recipient address so the funds went to them instead. The result looked like a crowd stripping assets from one vulnerable system in public.

The phrase “decentralized looting” describes that copycat dynamic; it is not a technical category or proof that every participant acted independently. The important lesson is practical: once a bridge’s validation fails, a public blockchain can make an exploit easy to observe and imitate. Speed can matter as much as technical skill, which is why a single flaw can become a mass incident within hours.

Nomad relies on cross-chain messages: activity on one blockchain is relayed so a contract on another can recognize a deposit or authorize a withdrawal. The bridge must verify that a message really came from the right source and was approved under its security rules. If that check fails, the destination chain may accept a withdrawal that was never properly backed by a deposit.

In the 2022 incident, a software upgrade left a zero-valued root accepted as valid. That broke the check that should have tied withdrawal messages to legitimate cross-chain activity. Attackers could submit messages that the bridge treated as authorized even though they did not represent valid deposits.

The vulnerability did not mean every wallet using Nomad had its private key stolen. It was a flaw in the bridge’s contract logic. That distinction matters when you assess your own exposure: a compromised bridge may put assets locked in, or routed through, its contracts at risk even if your wallet seed phrase remains private. But if you signed suspicious transactions or disclosed your phrase, you also need to assess your wallet’s separate security.

The first exploitable transactions made the weakness visible on-chain. Other users could inspect them, copy the general method and alter transaction data—especially the destination address—to try to claim funds for themselves. In a conventional bank transfer, one customer usually cannot watch a failed security check and repeat it against the same shared system. On a public blockchain, transaction details are visible and can be copied quickly.

That helps explain why the incident spread so widely. The exploit did not require every participant to discover the flaw independently. Once the pattern was apparent, imitation lowered the barrier to joining in. Some addresses identified themselves as white-hat hackers, but a self-description does not establish that a transfer was authorized or that funds were ultimately returned.

Public visibility is not the same as safe transparency. It can help incident responders trace transactions, but it can also help attackers replicate them. For users, the response should be to stop interacting with the affected route, avoid copying transaction instructions from social posts, and wait for clear, independently verifiable information before considering any recovery action.

“First decentralized looting” is a dramatic description of what people saw: numerous addresses appeared to race to take funds from the same vulnerable bridge. It is useful shorthand for the copycat behavior, but not a precise technical term. It also makes a stronger historical claim than the incident itself can prove. Crypto has had earlier thefts involving multiple participants, and “first” depends on how looting is defined.

What made Nomad stand out was the speed and visibility of the replication. The original flaw opened the door; public transactions showed others how to follow. The crowd effect did not make the conduct legitimate, and an address acting like a white hat cannot be assumed to be one. Some actors may have intended to return funds, while others may have sought to keep them.

For your security decisions, the label matters less than the pattern. When a bridge starts processing withdrawals that do not match real deposits, assume that the system may be under active attack. Don’t test it with a small transfer, copy someone else’s transaction, or trust a message promising a share of recovered funds. A live exploit is not a safe opportunity to experiment.

The widely reported loss was about $190 million, but that figure is an estimate, not a guarantee of how much any one user lost. Nomad reportedly offered white-hat hackers a 10% bounty for returning 90% of funds. That offer does not establish how much was returned, whether a particular address qualified, or whether affected users received compensation.

In 2026, Nomad’s current security status and supported routes are unclear. Don’t infer that the bridge is safe because its name still appears in old articles, wallet menus or community posts. Nor should you assume an old transaction route remains operational or that funds can be recovered by sending another transfer.

Before using any bridge, look for a current, specific statement about whether deposits and withdrawals are enabled, what contracts and networks are supported, and what users should do if a transfer is stuck. Check that details against the exact contract and network shown in your wallet. If you cannot establish that a route is currently supported and secure, choose not to send assets through it. An unavailable route is inconvenient; a mistaken transfer or exploit can be far more costly.

If you used Nomad, first work out what you actually did: connected a wallet, approved a token, sent a bridge transaction, or entered a recovery phrase. Those actions carry different risks. Do not send more funds to “unlock” a transfer or pay someone who claims they can recover assets for an upfront fee.

Use this checklist:

1. Stop using the route. Don’t approve new transactions or follow recovery instructions from unsolicited messages.
2. Check your wallet activity. Confirm the network, token, contract and transaction status using a trusted block explorer or wallet history. Never rely only on a screenshot or a message from a stranger.
3. Review token approvals. Revoke permissions you no longer need using a trusted wallet or approval-management tool, and check that you are on the correct chain. Revoking an approval does not reverse a completed transfer.
4. Protect the recovery phrase. If you entered it anywhere, create a new wallet using a secure device and move any remaining assets. Do not reuse the exposed phrase.
5. Keep records. Save transaction IDs and messages if you need to report a loss, but never share your seed phrase or private key.

A bridge transaction that is pending or failed may need a different response from an approval or a compromised wallet. Avoid guessing; verify the exact on-chain state first.

Treat a bridge as a system that adds risks beyond holding tokens on one chain. Before you move funds, check the route, the contracts involved, the transaction costs and what happens if the transfer fails. A bridge can rely on smart contracts, message verifiers, relayers, validators or other components; a weakness in one part may affect assets even when your wallet itself is secure.

Use this pre-transfer checklist:

• Confirm the route: source network, destination network, token and receiving address must all match your plan.
• Check current operation: look for a clear, current status for deposits and withdrawals. Don’t rely on an old tutorial.
• Inspect costs: expect network gas and any bridge or swap charges. Fees and quotes can change; compare the amount you send with the amount you expect to receive before signing.
• Review the approval: check which contract can spend your tokens and whether the permission is limited to the amount needed.
• Consider the exit: find out how you would move funds back and whether that takes extra time, fees or steps.

For example, Arbitrum Bridge is a canonical route for supported assets between Ethereum and Arbitrum One, but Ethereum withdrawals typically take around seven days. Squid Router provides cross-chain swap quotes, but you still need to check route costs and security details. Neither option removes bridge or self-custody risk.

A few common mistakes make bridge incidents more expensive or harder to resolve:

• Trusting an old guide. Contract addresses, supported networks and operating status can change. Verify the route before every transfer.
• Sending a test amount during an active incident. A small test is still exposed to the same underlying flaw and may not reveal whether a larger transfer will work.
• Approving a request without reading it. Check the token, amount, network and spender. If the wallet display is unclear, cancel rather than guess.
• Treating a familiar interface as proof of safety. A front end can be copied, outdated or connected to a risky contract. Confirm the contract and chain independently.
• Assuming a transaction can be reversed. Confirmations and smart-contract transfers are generally difficult or impossible to undo. A support message cannot simply roll back a completed on-chain transfer.
• Paying a recovery stranger. Be suspicious of anyone demanding an upfront fee, your seed phrase or remote access to your device.

Nomad’s story is a reminder that a bridge’s central promise—moving assets across chains—depends on complex checks working correctly. If you cannot verify the exact route and its current status, don’t send the funds. Waiting or using a different, well-understood route is usually safer than relying on a promise of quick recovery.