Security and scams · Explainer
What Happened in the Nomad Bridge Hack?
The 2022 Nomad bridge exploit turned into a public wave of copycat withdrawals, often described as “decentralized looting.” Learn how it happened, what remains uncertain, and how to assess bridge risks in 2026.
By the HelpfulCoin editorial team · Updated

What was the Nomad bridge?
Nomad was a cross-chain messaging protocol and bridge that moved digital assets between blockchains. It connected networks including Ethereum, Avalanche, Evmos, Milkomeda C1 and Moonbeam. A bridge is a system for transferring tokens or messages between separate blockchains, which do not normally share the same transaction records.
In a typical bridge transfer, a user deposits or locks tokens on one network. The bridge verifies that event and arranges for corresponding tokens to be released or created on another network. That verification step is critical: if the bridge accepts a false message, it may release assets without a valid deposit.
Nomad’s exploit in August 2022 exposed that risk. Roughly $190 million in crypto was taken, including ether and USDC. The event drew attention not only because of the amount, but because many people could imitate the initial exploit using public transaction data.
Nomad is not a bridge to treat as a normal transfer option in 2026. Its current status is unclear, and the size of its past exploit makes it especially important not to assume that a service, contract or recovery process is still active or safe.
What happened in the Nomad bridge hack?
The Nomad bridge was exploited in August 2022, when attackers used a flaw in its cross-chain message verification to withdraw assets without valid authorization. The losses were reported at roughly $190 million, with some estimates putting the amount near $191 million.
The affected assets included ether and the stablecoin USDC. The bridge connected several chains, so the incident involved transactions across more than one network. The central problem was not that users had to give an attacker their passwords; it was that the bridge’s own verification process could be fooled into accepting withdrawals.
Once the exploit became visible on-chain, other people began copying and modifying the transactions. That meant the damage spread through a sequence of public, similar withdrawals rather than remaining a single hidden attack. Some people identified themselves as white-hat hackers, a term for people who claim to exploit a flaw to help return funds or expose a vulnerability. A claim of good intent, however, does not by itself make taking funds lawful or safe.
Nomad later offered a 10% bounty to people who returned 90% of what they had taken. That offer is not the same as proof that funds were returned or that affected users were fully reimbursed.
How did the Nomad exploit work?
A flaw in Nomad’s message verification meant the bridge could treat withdrawals as authorized even when they did not have a valid message from the source chain. In a bridge, a message is evidence that an event—such as a token deposit—really happened on another blockchain. If that evidence check fails, the bridge can release assets it should keep locked.
The first exploit transaction showed others what the bridge would accept. Because blockchain transactions are public, people could inspect that transaction, copy its structure and alter details such as the recipient address. They could then submit similar withdrawals. In effect, the flaw made it possible for many wallets to repeat a pattern that should have been rejected.
This is different from a user clicking a phishing link and signing away tokens. The key vulnerability was in the bridge’s smart-contract logic: software running on a blockchain that manages assets or rules. Users who copied the exploit were still responsible for their actions, but the repeated withdrawals were enabled by the underlying verification defect.
The lesson is that a bridge’s security depends on the whole message-verification system, not just the security of the blockchains it connects. A well-known chain cannot protect users from a bridge contract that accepts invalid instructions.
Why was the Nomad hack called decentralized looting?
“Decentralized looting” describes how copycat withdrawals spread among many independent wallets after the first exploit became public. It is a memorable phrase, but it is not a technical category or a claim that every person involved had the same motive.
In many crypto attacks, one attacker quietly exploits a weakness and moves the stolen funds. The Nomad incident became unusually visible because the first transaction gave others a template. Observers could see what had worked, and some adapted the transaction rather than needing to discover the flaw themselves. A public blockchain made the pattern observable, while the bridge defect made the withdrawals possible.
That openness has two sides. Public transaction records can help security researchers and investigators trace activity. But when a weakness is still exploitable, the same transparency can help copycats understand how to repeat it. A visible transaction is not proof that an action is legitimate, harmless or legally protected.
The phrase also risks making the event sound like a game or a victimless free-for-all. It was not: the bridge held user assets, and withdrawals created losses and uncertainty for people who depended on it. Calling the incident looting captures the rush of imitation, but does not settle questions about individual responsibility or recovery.
Were the stolen Nomad funds recovered?
Nomad offered a 10% bounty to people who returned 90% of the funds they had taken, but that offer does not show how much was ultimately recovered. The current recovery process and a final accounting of losses are unclear, so affected users should not assume that funds have been returned or that a claim can still be filed.
A bounty offer is an attempt to encourage people who took funds to return most of them in exchange for keeping a portion. It is not the same as insurance, a guaranteed refund or a finding that every recipient acted as a white hat. Whether a user receives compensation can depend on what funds were recovered, the project’s actions and any legal process.
If you believe you were affected, keep your own records: transaction hashes, wallet addresses, dates, token amounts and any communications about the incident. Do not share seed phrases or private keys with anyone claiming they can recover crypto. A legitimate recovery process does not need a wallet’s secret recovery phrase.
Be wary of unsolicited messages promising to restore stolen funds for an upfront payment. Crypto transfers are generally difficult to reverse, and recovery scammers often target people who have already suffered a loss. Verify any current process through independently authenticated project communications before taking action.
Is Nomad safe to use in 2026?
Nomad is best avoided in 2026 because its current operating status is unclear and it suffered a major exploit. A history of a bridge exploit does not prove that every later contract is vulnerable, but it is not a reason to assume the service has resumed safely or that users can withdraw without risk.
Before using any bridge, check the specific network route and the contract address through the project’s current, independently verified communications. Confirm that deposits and withdrawals are functioning, that the bridge explicitly supports the token and networks involved, and that there is a clear way to get help if a transfer fails. A token with the same name on another network may not be the same asset.
Use this basic checklist:
- Verify the project and contract addresses; do not rely on an address sent in a chat or direct message.
- Read the current warnings and status notices for both networks and the bridge.
- Check the quoted fees, exchange rate and expected transfer time before signing.
- Send a small test amount first when appropriate, while remembering that even a small transfer can be lost.
- Review the wallet prompt and revoke approvals you no longer need.
A successful test does not prove a bridge is secure. Avoid transferring an amount you could not afford to lose.
What mistakes should bridge users avoid?
The main mistake is treating a bridge as a simple pipe between chains rather than a separate piece of software that can fail. A bridge may hold large amounts of user funds and rely on complex contracts, validators or message-verification systems. Its risks are additional to the risks of the blockchains and tokens it connects.
Watch out for these common errors:
- Assuming a familiar chain means a safe bridge. Bridge contracts can have their own flaws even when the connected networks are operating normally.
- Sending funds to an old or unverified contract. Addresses can change, and scam sites can imitate project names.
- Trusting a transaction because many wallets used it. Public activity is not a safety endorsement; copycat transactions were central to the Nomad incident.
- Ignoring token and network details. Sending the wrong asset or choosing an unsupported route can leave funds inaccessible.
- Believing recovery promises. No person can guarantee a refund, and requests for seed phrases or upfront recovery payments are red flags.
Stop if the bridge’s status is unclear, a route is paused, or the wallet asks for permissions that do not match the action. Do not rush because a price is moving or someone says a transfer window is closing.
What does the Nomad hack teach crypto users?
The Nomad exploit shows that cross-chain bridges add a security layer that users need to assess separately. A bridge must correctly verify events on one network before allowing assets to move on another. If that check is wrong, users can face losses even when they never shared a password or signed a transaction to an attacker.
For readers comparing bridges, useful questions include:
- What mechanism verifies messages from the source chain?
- Who can pause transfers or change the contracts?
- Are the contracts and any security reviews current and independently verifiable?
- What happens if a transfer is delayed, disputed or sent to the wrong address?
- Does the project publish current operating status and clear support procedures?
Answers to these questions reduce uncertainty but cannot remove smart-contract, operational or market risks. A security review is not a guarantee that code is free of vulnerabilities, and a bridge’s past uptime does not guarantee future safety.
In 2026, Nomad’s exploit remains a useful warning, not a reason to repeat old transaction patterns or seek out vulnerable contracts. Treat bridge status as something to verify before every transfer, and do not use a service whose current operations and user protections are unclear.
Frequently asked questions
What was the Nomad bridge?
Nomad was a cross-chain messaging protocol and bridge that let users move digital assets between blockchains. The 2022 exploit drained roughly $190 million in crypto, including ether and USDC.
How was the Nomad bridge exploited?
A flaw in the bridge’s message verification let withdrawals proceed without valid authorization from the source blockchain. After the first exploit transaction appeared, other users copied it and changed details to direct withdrawals to their own addresses.
Why is the Nomad hack called decentralized looting?
“Decentralized looting” is an informal description, not a formal security term. It refers to how many people were able to copy and adapt public exploit transactions, rather than one attacker carrying out every withdrawal.
Were the stolen Nomad funds recovered?
Nomad offered a 10% bounty to people who returned 90% of what they took. That offer does not establish how much was ultimately recovered, and Nomad’s current recovery process and final accounting are unclear.
Is Nomad safe to use in 2026?
The incident happened in 2022, but Nomad’s current operating status is unclear, so it is best avoided. Never send funds to a bridge unless you can verify that its service, contracts, supported networks, and recovery arrangements are current.
Mentioned in this guide
dApps in this guide
Nomad is a cross-chain messaging protocol and bridge, but a major 2022 exploit and unclear current status make it one to avoid.
Crypto.com is a crypto app and exchange with broad trading and euro deposit options; it merits a look, but check fees and product risks.
Keep reading
Related guides
Security and scams · Explainer
What Happened in the Poly Network Hack?
In August 2021, an attacker used a flaw in Poly Network’s cross-chain system to move more than $600 million in crypto. Most of the assets were later returned, but the incident showed why bridge security matters.
Security and scams · Explainer
What Happened in the Alpha Homora Exploit?
Alpha Homora’s 2021 exploit was a smart-contract security incident, while the “Binance growth” headline referred to separate DeFi activity. Learn what happened, what it means for users in 2026, and how to assess a protocol before connecting a wallet.
Security and scams · Explainer
What Happened After the Harmony Hacker Moved Funds?
In June 2022, an attacker stole about $100 million from Harmony’s Horizon bridge, then began moving some of the assets. Harmony announced a $1 million bounty; later reporting documented the recovery of some Bitcoin, but not a complete final accounting of the stolen funds.
Security and scams · Explainer
What Happened in the QiDao Superfluid Exploit?
QiDao’s Superfluid-related contract was reportedly exploited for about $13 million. Learn what that figure does—and does not—tell you, how to check whether you may be exposed, and what to do before using either protocol.
Security and scams · Explainer
What Happened in the OpenSea Data Breach?
In 2022, an employee at OpenSea’s email vendor improperly accessed and shared email addresses associated with OpenSea users and newsletter subscribers. The exposure did not include wallet credentials or private keys, but it can make targeted phishing attempts more convincing.
Security and scams · Explainer
What Were the McAfee Scam Tokens, and Are They Safe?
John McAfee died in 2021, but his name can still be used to attract attention to crypto tokens. Learn how impersonation and pump-and-dump schemes work, what his past token promotions involved, and how to check a token before interacting with it.
Security and scams · Explainer
How Do OpenSea Phishing Emails Steal NFTs?
Fake OpenSea emails can steer NFT traders to lookalike sites or trick them into approving wallet actions that transfer assets. Learn how the scams work, how to check an alert, and what to do if you clicked or signed something suspicious.
Security and scams · Explainer
Did Floyd Mayweather Promote Another NFT Scam?
The claim that Floyd Mayweather has promoted another NFT scam is not established by the reporting summarized here: it names no NFT project or campaign. Mayweather did face SEC action over a paid cryptocurrency promotion in 2018, but that case involved an initial coin offering, not an NFT.