The $320M Wormhole Exploit: Jump’s ETH Replacement and a Court-Ordered Recovery
In February 2022, an attacker minted 120,000 unbacked wrapped ETH through Wormhole. Jump supplied replacement ETH; a year later, Oasis helped retrieve assets under a court order. The recovery exposed a different set of control powers.
Key Points
- A Solana contract verification flaw allowed 120,000 wrapped ETH to be minted without matching deposits, valued at roughly $320 million at the time.
- Jump announced that it had replaced 120,000 ETH on February 3, 2022. Restoring backing addressed the bridge’s shortfall; a collapse of all Solana DeFi was a feared scenario, not an established outcome.
- Oasis confirmed a court-ordered asset retrieval in February 2023. Wormhole later announced a ZK roadmap and launched W in 2024; neither announcement proves that Guardian verification had been abolished.
Chronological Timeline
A verification flaw allows 120,000 wrapped ETH to be minted on Solana without the corresponding deposit.
Jump publicly confirms replacing 120,000 ETH to support Wormhole and its community.
Immunefi reports a $10 million payment for a separate Ethereum contract flaw reported and fixed on February 24.
Oasis says its multisig and a court-authorized third party retrieved assets associated with the attacker’s wallet.
The ZK roadmap is announced on January 31; W goes live on April 3. These are distinct development and governance milestones.
1. A deposit that never happened
Wormhole’s bridge connected assets held on Ethereum with wrapped tokens used on Solana. The arrangement depended on a simple promise: tokens issued on the destination chain should correspond to assets deposited on the source chain. On February 2, 2022, an attacker broke that connection and minted 120,000 wrapped ETH without supplying the matching ETH, a shortfall valued at roughly $320 million.[1][2]
Kudelski’s technical analysis traced the failure to the Solana contract’s handling of instruction data. The load_instruction_at function did not check that its input was the genuine instruction sysvar account. Fabricated data could therefore pass the contract’s verification path. The failure was in accepting purported authorization; it does not show that the attacker obtained the Guardians’ private keys or persuaded all of them to sign.[1]
Chainalysis tracked 93,750 ETH bridged back to Ethereum and reported that the remaining wrapped tokens were exchanged for other assets on Solana. That transfer quantity differs from the 120,000 tokens minted without backing. The distinction matters: the attack created an accounting gap across chains, rather than making every ETH-related token on Solana valueless.[2]
2. Replacing ETH before recovering it
The immediate problem was the missing backing. Chainalysis described the danger that selling pressure and troubled collateral could spread to connected protocols. That was a risk assessment, not proof that every lending market was about to liquidate. Restoring the missing assets was therefore a direct response to the bridge’s immediate problem, while the broader consequences of leaving the gap open remained uncertain.[2]
On February 3, Jump Crypto publicly said it had replaced 120,000 ETH to support Wormhole and community members. Its announcement specifies ETH, not a $320 million bank transfer. The dollar figure describes the approximate contemporary scale of the exploit. Replacing the assets could restore backing even while the attacker still held proceeds; replacement and recovery were separate events.[6]
Wormhole also sought the return of the funds through a $10 million bounty offer, which Chainalysis recorded and later reported had been reiterated. A whitehat settlement proposal is not evidence of a grant of criminal immunity by public authorities. The offer did not produce the return of funds described in the initial report, so the replacement ETH and the pursuit of the attacker continued on separate tracks.[2][5]
3. The vaults and the court order
A year later, the story moved to automated vaults on Oasis. In its statement, Oasis said a whitehat group had reported an administrative-design vulnerability on February 16, 2023. It then received a High Court of England and Wales order on February 21 to retrieve certain assets linked to the Wormhole attacker’s wallet. Oasis identified neither the whitehat group nor the authorized third party as Jump.[4]
Oasis confirmed that its multisig and the court-authorized third party carried out the retrieval, and that the assets went immediately to a wallet controlled by that third party. Blockworks’ contemporaneous analysis attributed a possible Jump role to transaction patterns, while explicitly noting that wallet ownership had not been confirmed. The public record therefore leaves a distinction between the confirmed retrieval and the unconfirmed identities behind parts of the operation.[4][5]
Blockworks estimated a net recovery of about $140 million after debt repayment; it described approximately $218 million of collateral and 80 million DAI used to repay loans. Those reported amounts are not 120 million DAI newly recovered. Oasis’s own statement confirms the retrieval but gives no recovery valuation. The episode illustrates the reach of automation and upgrade powers, without establishing a first-ever legal precedent.[4][5]
4. Security repairs, investment and W
Security work also had a separate timeline. On May 20, 2022, Immunefi disclosed a $10 million reward to satya0x for an Ethereum proxy flaw reported and fixed on February 24. This was a different issue from the Solana exploit. The disclosure supports a concrete repair and payment, not a claim that Wormhole had already replaced its entire verification network with zero-knowledge proofs.[7]
Multicoin Capital stated on April 3, 2024 that it had co-led a $225 million round closed late in 2023, and timed its announcement to W going live that day. The round brought fresh capital to a project that had continued developing after the exploit. Funding a project and launching its token are milestones of their own; neither establishes that recovery caused the investment or that all protocol control had become decentralized.[9]
Wormhole’s January 31, 2024 roadmap proposed ZK verification as an additional option. It described the existing requirement for at least 13 of 19 Guardians and future light-client integrations. The roadmap was not evidence of a completed May 2022 transition. The story thus has three distinct responses to risk: replacement capital, retrieval through administrative authority, and further verification work whose announced plans must be distinguished from deployment.[8][9]
Key Takeaways for Investors & Builders
Verify the message, not just its format
A bridge must establish that authorization came from the expected verifier. Accepting fabricated verification data can break the link between deposits and minted tokens.
Restoring backing takes assets
Jump’s replacement addressed the ETH shortfall. It does not establish every hypothetical liquidation that would have occurred without that intervention.
Recovery depends on control
The Oasis retrieval used administrative powers and a court order. Its success also makes the scope of upgrade and automation authority important to users.
Continue reading
Explore the topic through other cases and contexts.
Sources & References
- [1]Source 1: Technical analysis of the Wormhole attackKudelski Security
- [2]Source 2: Wormhole exploit and contagion risksChainalysis
- [3]Source 3: Report on Jump replacing the stolen fundsBloomberg
- [4]Source 4: Oasis statement on the court-ordered retrievalSummer.fi
- [5]Source 5: Blockworks analysis of the recovery and its attribution limitsBlockworks
- [6]Source 6: Jump confirms replacing 120,000 ETHJump Crypto · 2022-02-03
- [7]Source 7: Separate Ethereum proxy repair and bounty disclosureImmunefi · 2022-05-20
- [8]Source 8: ZK roadmap and existing Guardian verificationWormhole · 2024-01-31
- [9]Source 9: Investor confirmation of the funding round and W launchMulticoin Capital · 2024-04-03