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
The 600 million BETX tokens held by BETX managers were stolen by hacker and sold on the Newdex exchange. Preliminary analysis shows that the cause of this attack is that the private key of BETX project is stolen, and the hacker gains the owner privilege and transfers all the existing tokens of the contract. The selloff caused the BETX token to fluctuate sharply and close to zero. Attack method (per SlowMist): Private Key Leakage. Reported loss: 600,000,000 BETX.
Primary source
https://www.jinse.com/lives/100822.htm ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- BETX
- bug_class
- private-key
- date_occurred
- 2019-06-11
- loss_usd
- —
- source_id
- sm:betx::2019-06-11
Related — same bug class· private-key