AMLConsensus · course
Programme · Lesson 11.3
Section 11 · Lesson 11.3 · case study

Ronin Bridge: How Lazarus Stole $625M

A game about cute digital creatures called "axies," played by millions of people, became the scene of one of the largest thefts in the history of cryptocurrency. Behind the hack stood not a lone hacker but a state cyber group of North Korea — Lazarus. About $625M was stolen, and the money went to fund the regime's programmes. This case is a textbook on three topics at once: why bridges between blockchains are so vulnerable, what a sanctioned address looks like, and how multi-stage laundering through a mixer and cross-chain works.

▶ Video case study: Ronin and Lazarus (English narration).

The bridge as a target

The popular game Axie Infinity ran on its own sidechain called Ronin — a separate blockchain linked to Ethereum through a bridge. A bridge is needed to move assets between networks: a user "locks" tokens in one network and receives their equivalent in another. The problem is that such a bridge concentrates gigantic sums of collateral — and therefore becomes an ideal target.

On 23 March 2022 Ronin was hacked. But the most alarming thing about this story is that the theft was not noticed right away: the incident was discovered only on 29 March, nearly a week later. While the team was unaware of the breach, the attackers managed to drain the assets. The result: 173,600 ETH and 25.5M USDC — about $625 million in total — were stolen.

Why bridges are vulnerable. A bridge is essentially a gigantic shared safe securing transfers between networks. Control over transfers often rests on a limited set of validator keys. If an attacker obtains a sufficient number of these keys, they can "sign" the withdrawal of all the collateral — which is what happened with Ronin. Hence the rule: large cross-chain bridges are a priority target for attacks, and funds that came out of a hacked bridge are toxic.

Attribution: a state stands behind the hack

On 14 April 2022 the case moved from the category of "major theft" to that of "national security matter." The U.S. Department of the Treasury (OFAC) officially linked the theft to the North Korean hacker group Lazarus. This is a state cyber group of the DPRK, whose operations bring the regime currency that goes, among other things, toward military programmes. Lazarus has billions of dollars in thefts across the industry to its name.

The attribution changed everything. Funds stolen by Lazarus are not just "dirty" money; this is money under direct sanctions, dealing with which is prohibited. And for the industry to be able to block these funds, a concrete reference point was needed — a sanctioned address.

The sanctioned address: what it looks like

OFAC added to the sanctions list a specific Ethereum address holding the stolen ETH — about $400M at the time:

0x098B716B8Aaf21512996dC57EB0615e2383E2f96

Remember how this looks in real work. From the moment it is added to the SDN list, this set of 42 characters stops being merely a "wallet" — it becomes legally toxic. Any transfer to it or from it is a potential sanctions violation. This is exactly how the abstract idea of "sanctions against an address" turns into a concrete string that an AML system is obliged to recognize.

Sanctioned Ronin bridge exploiter address (Lazarus)

The real sanctioned address linked to the Ronin theft: 0x098B716B8Aaf21512996dC57EB0615e2383E2f96. In the explorer it is flagged as connected to OFAC sanctions.

Laundering: mixer → bridge → bitcoin

Having gained control over $625M, Lazarus faced the same problem as all thieves before it (recall Bitfinex): stealing is only half the job, you still have to "launder" and cash out. And here the group applied a honed multi-stage obfuscation scheme typical of the DPRK.

  1. Theft from the bridge. 173,600 ETH + 25.5M USDC (~$625M) drained from the Ronin sidechain.Hacked 23 March, discovered 29 March — a window of nearly a week.
  2. Run through a mixer. Part of the funds is run through Tornado Cash — a mixer that breaks the "input↔output" link.The goal is to sever traceability so the analyst can't see that this came from the stolen loot.
  3. Cross-chain via the Ren bridge. The funds are moved through the Ren bridge into another network.Switching blockchains ("chain hopping") complicates end-to-end tracing between different ledgers.
  4. Conversion into bitcoin. Ultimately the assets are moved into BTC.Switching asset and network is one more layer of obfuscation before the attempt to cash out.
Ronin Bridge
173,600 ETH + 25.5M USDC
Tornado Cash
mixer: link broken
Ren bridge
network switch
Bitcoin
asset switch

Note the logic of this chain. Each step solves a separate obfuscation task: the mixer breaks the direct link between what was stolen and what was withdrawn; the cross-chain bridge leads the trail into another blockchain, where end-to-end tracing is harder; the asset switch into BTC adds one more layer. This is not chaotic "scattering" but an engineered, deliberate laundering conveyor that Lazarus applies from operation to operation.

Why this case is a concentrate of risks

Ronin is valuable to us because in a single case all the main AML red flags we studied separately converge at once.

What this case teaches. Ronin shows the "grown-up" level of adversary: not a lone actor but a state conveyor for theft and laundering. For practice this means several things. Bridges are the juiciest target, so the origin of funds from a hacked bridge automatically places a wallet in the high-risk zone. A sanctioned address is not an abstraction but a concrete string like 0x098B716B8Aaf21512996dC57EB0615e2383E2f96, and recognizing such strings is a basic function of screening. And the multi-stage "mixer → bridge → BTC" scheme teaches you to look not at a single hop but at the whole chain: if a mixer or a link to Lazarus addresses appears somewhere in a wallet's history, "cleaning up" such funds is impossible — the verdict is stop.

What to take away from this lesson

Ronin long held the sad record of the largest theft. In the next case study we will see how that record was broken by the same Lazarus group — and why the 2025 Bybit hack revealed a new, even more insidious attack vector.

The facts are presented from open sources. The materials are for educational purposes.