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
On November 8, 2023, CoinSpot was exploited across two of its hot wallets, resulting in a loss of over 1,283 ETH, worth approximately $2.472 million. Attack method (per SlowMist): Private Key Leakage. Reported loss: $ 2,472,000.
Primary source
https://medium.com/neptune-mutual/taking-a-closer-look-at-coinspot-exploit-ac8c08ed18ee ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- CoinSpot
- bug_class
- private-key
- date_occurred
- 2023-11-08
- loss_usd
- $2,472,000
- source_id
- sm:coinspot::2023-11-08
Related — same bug class· private-key