Bridge message verification failure allowed the attacker to mint wrapped assets without valid backing.
Treat this as a reported explanation to test against code, traces, transaction data, and other primary evidence.
Checking the session, access policy, and current workspace data.
Signature verification bypass minted unbacked wrapped ETH
A deprecated, insecure Solana syscall allowed an attacker to forge guardian signatures, minting 120,000 wETH (~$325M) on Solana without burning any ETH on Ethereum.
Imported-record overview
These fields reproduce or normalize claims in an imported research record. “Reported” describes provenance; it does not mean ChainRadar has confirmed the claim.
Treat this as a reported explanation to test against code, traces, transaction data, and other primary evidence.
Date-free learning path
Synthetic study sequence for learning purposes; timestamps and ordering may not reproduce the full verified incident chronology. Synthetic dates are deliberately omitted below.
STUDY PHASE
STUDY PHASE
STUDY PHASE
STUDY PHASE
Teaching model
Educational reconstruction intended to explain the reported attack pattern, not a transaction-level evidentiary trace.
Follow the numbered arrows; loopbacks model repeated actions or repayments. Every label is derived from the imported flow actions and structure.
Values describe reported movement between stages. Repeated amounts are not additional losses.
| Step | From | To | Reported action | Value |
|---|---|---|---|---|
| 01 | Attacker | Bridge Core | Submit Forged Message | Not reported |
| 02 | Bridge Core | Wrapped Token | Mint Unbacked WETH | $120B |
| 03 | Wrapped Token | Attacker | Credit Balance | $120B |
| 04 | Attacker | Ethereum Exit | Bridge And Swap | $93B |
Imported indicators
Contract entries are reproduced from the local research archive. Confirm chain, bytecode, ownership, and incident relevance against primary evidence before using them in an investigation.
0x98f3c9e6E3fAce36bAAd05FE09d375Ef1464288BDefensive prompts
These imported mitigation labels are study prompts, not a complete or validated remediation plan. Test them against the protocol's actual architecture and failure mode.
Investigator workflow
Turn this background study into questions for a separate, evidence-led investigation. Never promote an educational edge or imported label into a finding without corroboration.
Preserve official disclosures, on-chain transactions, code, retrieval times, and other evidence supporting each material claim.
Start from corroborated addresses or transactions and trace each hop without assuming the educational flow is exact.
Compare decoded calls, logs, bytecode, and state changes with the reported cause.
Record provenance for every claim and identify gaps that still require confirmation.
Source status: cataloged. Classification: educational. Risk methodology: heuristic only. Primary-source verification remains required for every material claim.