VERDICT —OUT OF SCOPE
Root cause is private-key / signer compromise — the on-chain contract behaved exactly as written. No pre-deployment source audit or bytecode review reaches the key-custody perimeter; this is operational-security territory (HSM/MPC hygiene, key rotation, hot-wallet isolation). Bytecode would show nothing wrong.
▰ METHOD
PRIVATE KEY
PRIVATE-KEY
Root cause
Root-cause analysis not yet published. The incident description below contains all currently available signal — review the attack transaction directly for definitive forensics.
Forensic narrative
According to a report from CoinDesk Korea, Bithumb may have also lost 20.2 million XRP in the recent breach. The XRP was moved from Bithumb’s wallet on March 29 in transactions that can be seen on XRPSCAN. Attack method (per SlowMist): Wallet Stolen. Reported loss: 20,172,060 XRP.
Primary source
https://www.btcsearch.com/t/1298307 ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Bithumb
- bug_class
- private-key
- date_occurred
- 2019-03-29
- loss_usd
- —
- source_id
- sm:bithumb::2019-03-29
Related — same bug class· private-key