Preview surface — demo data. Where real data exists today (e.g. RealT, BlackRock BUIDL, Lift Dollar) we render it; everywhere else we render synthetic enrichment generated deterministically from public signal and clearly marked Demo or Inferred. The Phase 3 roadmap replaces every synthetic source with live ingestion — see Methodology → Exposure Graph & Similarity Engine.
← back to incident ledger

frontend dns hijackDemo

Feb 20, 2022 · $6.1M · frontend

Narrative

On 2022-02-20, Chainbase suffered a frontend dns hijack incident resulting in approximately $6,075,496 in losses. The exploit targeted the frontend layer. Attribution: unknown. This is a demonstration entry — not a real incident.

Victims

Classification

Root cause
frontend_dns_hijack
Secondary causes
supply_chain_npm
Attack layer
frontend
Strategy
tech_vuln
Actor role
target
Attribution
unknown
Attacker address
0xe9da951d4cfa47725e0bf8b9acb27cd1137a3664
Flash loan
no
Audited at time
yes
Bounty at time
no

AADAPT mappings

DEMO:AADAPT.TA0001DEMO:AADAPT.TA0008DEMO:AADAPT.T1071.001DEMO:AADAPT.T1583.001

Evidence

Disclosure date
Feb 22, 2022
Funds recovered
Audit firms at time
Code4rena, Spearbit
Post-mortem URLs (synthetic)
  • https://medium.com/chainbase/post-mortem-chainbase-2022-02-20
  • https://rekt.news/chainbase-rekt
  • https://blog.chainbase.xyz/incident-report
tx hashes (3)
  • 0x0606a55c97d1fe895a158f225137c8762f04f4fb517a242e765d40c7ebf04564
  • 0x0e8101dacacb4aa4e5cb10904902db3294a1da48350aa7527227789fd162a0de
  • 0x1cda0836df758b7826a0227903a9fcf5d2abfd8afb5c9a5d632f752b7edfd833