AWS KMS Key Leak - 80M USR Minted
Treat this as a reported explanation to test against code, traces, transaction data, and other primary evidence.
Preparing your view
Checking the session, access policy, and current workspace data.
Checking the session, access policy, and current workspace data.
AWS KMS Key Leak - 80M USR Minted
Compromised AWS KMS key allowed 80M USR minting, causing $25M drain and 80% depeg.
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
AWS_KMS.get_signing_key()STUDY PHASE
Resolv.swap_request(USDC_deposit)STUDY PHASE
Resolv.completeSwap(inflated_output, SERVICE_ROLE_key)STUDY PHASE
USR.stake(wstUSR)STUDY PHASE
Uniswap.swap(wstUSR)Curve.exchange(ETH)STUDY PHASE
Teaching model
Educational reconstruction intended to explain the reported attack pattern, not a transaction-level evidentiary trace.
Start at Stage 1 and follow the numbered arrows. 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 | USDC Deposit | Resolv Labs system | USDC Deposit | $150K |
| 02 | Resolv Labs system | Inflated Mint | Inflated Mint | $80M |
| 03 | Inflated Mint | Stake To WstUSR | Stake To WstUSR | $80M |
| 04 | Stake To WstUSR | DEX | DEX Swaps | $24M |
| 05 | DEX | Value destination | ETH Extraction | $24M |
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.
0x66a1e37c9b0eaddca17d3662d6c05f4decf3e110Defensive 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.