Structural Shift in Exploit Root Causes: From Contract Logic to Signing Orchestration
Existing incident trackers either lock forensic data behind JavaScript single-page shells that search engines and
researchers cannot archive, or lump fundamentally unrelated failures under vague tags. A flash-loan solvency
miscalculation inside an automated market maker (CWE-682) requires formal verification and invariant
fuzzing; a compromised AWS S3 frontend JavaScript bundle that tricks three hardware-wallet custodians into
blind-signing a Safe operation=1 DELEGATECALL overwriting storage slot 0x0 (CWE-494 + CWE-345) requires air-gapped out-of-band calldata decoding
and ERC-7730 clear-signing hardware displays.
The DT.gl Incident Ledger pre-renders every forensic record as semantic HTML backed by structured YAML/MDX collections (`16` baseline events in V1 plus deep byte-level post-mortems), paired with direct one-click verification presets inside our offline EVM Calldata & Signature Auditor.
Deep-Dive Forensic Post-Mortem Monographs
Each flagship post-mortem below reconstructs exact UTC transaction timelines, mutated EVM storage slots or NPM package hashes, adversary tradecraft, and reproducible hardware/protocol mitigations:
- DT-INC-2025-001 CWE-494 Bybit $1.46B Safe Multisig UI Supply-Chain & Slot-0 Delegatecall Post-MortemComplete UTC timeline, EVM storage-slot forensics, calldata breakdown, and Safe Guard remediation for the $1.46 billion Bybit cold-wallet exploit (DT-INC-2025-001).
- DT-INC-2025-002 CWE-347 Ethereum Pectra EIP-7702 EOA Sweeper Delegations & Chain-ID Zero Replay AnalysisForensic breakdown of post-Pectra EIP-7702 (Type 0x04) wallet drainer campaigns ($85M+ cumulative losses), RLP authorization tuple mechanics, consecutive-nonce attacks, and revocation workflows (DT-INC-2025-002).
- Complete UTC timeline, NPM publish-token forensics, dynamic CDN loader vulnerability analysis, and Subresource Integrity (SRI) remediation for the Ledger Connect Kit supply-chain attack (DT-INC-2023-009).
- DT-INC-2025-003 CWE-285 Tornado Cash OFAC Sanctions, Fifth Circuit Van Loon Reversal & Immutable ZK LawComprehensive technical and legal analysis of Tornado Cash (DT-INC-2025-003): Groth16 immutable pool contracts vs mutable governance, Van Loon v. Treasury (5th Cir.), OFAC delisting, and 0xbow Privacy Pools.
Open Machine-Readable Dataset Schema (`CC-BY 4.0`)
Security teams, academic researchers, and data journalists can ingest the DT.gl Incident Ledger programmatically
via /incidents/dataset.json or /incidents/dataset.csv, and subscribe to new forensic reconstructions via /incidents/rss.xml. Each record guarantees stable DT-INC-YYYY-NNN
identifiers, ISO dates, USD exploit values, MITRE CWE codes, and canonical specification routes. For broader
systemic context and historical custody failure analysis, consult our flagship synthesis at Major Cryptocurrency Incidents & Systemic Risk.
MITRE CWE Vulnerability Taxonomy for Cryptographic & Custody Incidents
Standardizing post-mortem root causes onto formal MITRE Common Weakness Enumerations allows treasury operators and protocol auditors to map historical exploits directly onto preventative engineering controls:
-
CWE-345(Insufficient Verification of Data Authenticity) &CWE-451(User Interface Misrepresentation): Covers multisig UI spoofing (Bybit, WazirX, Radiant Capital), vanity address poisoning ($68M WBTC heist), and deceptiveEIP-7702SetCode phishing prompts. Mitigated only when hardware signers parse raw structured fields viaERC-7730clear-signing descriptors and independent air-gapped verification workstations recomputesafeTxHashdigests out-of-band. -
CWE-494(Download of Code Without Integrity Check) &CWE-829(Inclusion of Functionality from Untrusted Control Sphere): Covers compromised AWS S3 web bundles and unpinned NPM/jsDelivr wallet connectors (Ledger Connect Kit). Mitigated via immutable content-addressed deployments (IPFS/Arweave hashes or local desktop packages),Subresource Integrity (SRI)SHA-384 hashes, and hardware-key-gated NPM publishing withSLSAbuild provenance. -
CWE-287/CWE-347(Improper Verification of Cryptographic Signature) &CWE-269(Improper Privilege Management): Covers cross-chain bridge validator quorum takeovers (Ronin 5-of-9), unverified signature sysvar calls (Wormhole), and centralized cloud key custody disguised as distributed MPC (Multichain). -
CWE-532(Insertion of Sensitive Information into Log File) &CWE-200(Exposure of Sensitive Information): Covers wallet crash-reporting SDKs logging plaintext BIP-39 mnemonics (Slope Sentry leak) and e-commerce buyer PII breaches (Ledger Shopify leak, Trezor Mailchimp breach) that expose self-custody holders to targeted SIM swaps and physical coercion.
Mandatory Pre-Signing Treasury Multisig Runbook
Institutional and DAO multisig signers operating Safe or threshold custody vaults should enforce a
strict four-step ceremony prior to touching any hardware security module button:
- Out-of-Band Coordinator Diversity: Never allow all threshold signers to load the same hosted web UI simultaneously. At least one quorum signer must reconstruct the transaction calldata independently via CLI or our offline Calldata & Signature Auditor on an isolated OS profile.
- Zero-Tolerance `operation=1` (`DELEGATECALL`) Policy: Standard asset transfers, ERC-20
approvals, and staking interactions always use
operation = 0(CALL). AnySafepayload specifyingoperation = 1grants the target contract unrestricted write access to storage slot0x0(the singleton implementation pointer) and must be halted unless verified against an audited canonical migration contract byte-for-byte. - Domain Separator & `safeTxHash` Byte Comparison: Verify both the 32-byte EIP-712
domainSeparatorandsafeTxHashdisplayed on the physical hardware wallet screen against the locally computed Keccak-256 digest rather than trusting browser extension popups. - Post-Pectra `EIP-7702` Code-Slot Monitoring: Monitor EOA signers for unexpected
0xef0100delegation designators and reject any signature request bearing magic byte0x05or transaction type0x04withchain_id = 0.
Frequently Verified Technical Questions
Why does DT.gl classify cryptocurrency incidents by MITRE CWE rather than generic DeFi labels?
Primary Reference: MITRE CWE Database
Can researchers and journalists reuse the DT.gl Incident Ledger dataset?
Primary Reference: Creative Commons CC-BY 4.0