Skip to content
The Canadian DeFi rulebook · rules checked 2026-11-02 · what changedEducation only · not financial, tax or legal advice
Incident · Bridge exploit · Aug 2022

Nomad bridge exploit: what happened and what it teaches

Mitey the yeti talking a plan through with an older yeti, with a bridge
Mitey says: Not a story to scare you. A checklist of what to look for next time.

A faulty upgrade made the Nomad bridge accept any unprocessed message as valid, so anyone could copy the exploit; the project later reported about US$38.8 million recovered.

What happened

A code change made on May 26, 2022, during an audit, and deployed on June 21, 2022, caused Nomad’s Replica contract to treat a zero value as a trusted root. Any message could be forged as long as it had not already been processed (project's own root-cause analysis, 2022-08-05).

Because the exploit was easy to copy, many addresses drained funds. Nomad offered a 10% bounty and treated anyone returning at least 90% as a white hat.

Timeline

DateWhat happened
2022-05-26Faulty change made during an audit
2022-06-09Quantstamp delivers its final audit report; Nomad's Immunefi bug bounty goes live (project's own account)
2022-06-21Change deployed
2022-08 (early)Exploit copied by many addresses
2022-08-01On or about this date, one person allegedly makes four exploit transactions worth about US$2.89 million (US indictment)
2022-08-05Nomad publishes its root-cause analysis; Replicas unenrolled and bridge interface disabled
2022-08-08US Treasury sanctions Tornado Cash, saying it laundered at least US$7.8 million from the Nomad heist
2022-11-11About US$38.8 million in the recovery pool (project figure)
2026-10-30US DOJ says the extradited defendant made an initial appearance in the Northern District of California

Scale, from official records

  • No official total-loss figure found; about US$38.8 million in the recovery pool as of November 11, 2022 (Nomad’s own update, 2022-11-11)

The Canadian angle

Global reference case; no Canadian-specific angle sourced.

How did one upgrade let anyone forge a message?

Nomad's Replica contract decided whether an incoming message had been proven before acting on it. The upgrade deployed on June 21, 2022 replaced the old check with one that looked up the root a message was proven under and asked whether that root was acceptable. A message that was never proven has a root of zero by default (project's own account, 2022-08-05).

The problem was in how the contract was set up. When a Replica was first deployed alongside its partner contract, it pre-approved the zero root by giving it a timestamp of 1. So for an unproven, forged message, the check found a valid-looking timestamp and let it through. Any message could be processed without proof, as long as it had not been processed before (project's own account).

Quantstamp audited the upgrade in May and early June 2022 and delivered a final report on June 9. The change was made on May 26, during that audit, as part of audit-related clean-up. An Immunefi bug bounty had been live since June 9, but no one reported the flaw there. Nomad's Watchers only watched for a stolen updater key, not contract bugs, so they did not act (project's own account).

Has anyone been charged?

Yes, one person, in the United States. On October 30, 2026, the US Department of Justice said an Israeli national had made an initial appearance in the Northern District of California on a 2023 indictment. He was arrested in Israel in May 2025 and extradited. According to the indictment, on or about August 1, 2022, he made four exploit transactions and moved 103 wrapped bitcoin (WBTC) and 300 wrapped ether (WETH), worth about US$2,894,390 at the time, to an address he controlled.

He is charged with causing damage to a protected computer, interstate transportation of stolen money and money laundering. The DOJ release says an indictment is merely an allegation and that defendants are presumed innocent until proven guilty. The amount covers only his alleged transactions, not the whole loss. This page does not name him because he has not been convicted.

Separately, when the US Treasury sanctioned the Tornado Cash mixer on August 8, 2022, it said the mixer had been used to launder at least US$7.8 million from the August 2, 2022 Nomad heist. A mixer pools funds from many users to hide where they came from. The figure is what passed through that one mixer, not the total taken from the bridge.

How did the recovery pool work?

Recovery depended on people giving money back. In the days after the hack, Nomad offered a 10% bounty to whitehats who returned funds, and many returned 90% and kept 10%. Some returned funds before the bounty existed, or returned everything and asked for the bounty later. By its November 11, 2022 update, the recovery wallet held the equivalent of about US$38.8 million (project's own account).

Nomad sorted that pool into four groups. About US$29.8 million (76.7%) came back in the same token that was taken. About US$8.3 million (21.3%) came back in a different token, to be converted back by a market maker. About US$610,000 (1.6%) was set aside for bounties claimed later, paid after identity checks. About US$160,000 (0.4%) was held back as possibly subject to regulatory restrictions (project's own account).

The plan was to load recovered tokens into upgraded bridge contracts so users could reach pro-rata shares of what came back for each token. That is a share of what was returned, not a promise of full repayment, and Nomad ran it itself, not a court or monitor. We found no official total-loss figure, so no recovery percentage can be given.

Is there a Canadian angle?

We found no Canadian regulator, court or police proceeding about the Nomad exploit, and no Canadian-dollar loss figure on any official page. The only criminal case we found is the US one above. The case is here because a single faulty upgrade emptied a bridge that many people used, and anyone could copy the attack.

Canadian securities rules set custody terms for trading platforms, not bridges. Under the CSA's pre-registration undertaking, a platform operating in Canada while it seeks registration commits to keep at least 80% of the value of clients' crypto with third-party custodians, to hold client assets in trust and apart from its own, and not to pledge or reuse them. CSA Staff Notice 21-332 (February 22, 2023) does not mention bridges or decentralized protocols.

On tax, the CRA's general folio on losses from crime says that compensation received for a stolen capital asset counts as proceeds of disposition, and that with no compensation the property is treated as disposed of on the date the loss was discovered. The folio is not written for crypto-assets, and a partial pro-rata return like Nomad's is not discussed in it.

What broke

An upgrade and initialization bug that slipped in during an audit window and could be replayed by anyone.

What a user could have checked

  • Whether the exact deployed code was audited, including recent upgrades.
  • Whether the bridge has rate limits or pause controls.
  • Whether the bridge's monitoring covers contract bugs or only stolen keys. Nomad's Watchers responded only to a compromised updater key.
  • Whether the bridge had a published policy for sharing losses before anything went wrong. Nomad's pro-rata plan was written after the hack and covered only what was returned.
  • Your own records of wallet addresses, balances and the Canadian-dollar value of each bridge transfer, which CRA asks crypto users to keep.

Recovery

About US$38.8 million recovered as of 2022-11-11 (project's own figure).

Sources

Education only. Nothing on this page is financial, investment, tax or legal advice, or a recommendation to buy, sell, stake, lend or borrow any crypto-asset. Crypto-assets can lose some or all of their value and are not covered by CDIC. Canadian rules change: check the dated sources above and talk to a qualified professional about your situation. Full disclaimer.

Rule-change alerts

Ask to be told when a rule on the tracker changes status. The MITEY network team sends these, and your enquiry goes to the MITEY intake inbox. For instant updates use the RSS feed or the JSON file.