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
Multi-chain trading platform Thunder suffered an attack. Thunder responded by stating that a third-party service it uses appears to have been targeted. No one's private keys are compromised. Only 114 wallets out of over 14,000 were affected. Attack method (per SlowMist): Third-party Vulnerability. Reported loss: $ 192,000.
Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Thunder
- bug_class
- private-key
- date_occurred
- 2023-12-27
- loss_usd
- $192,000
- source_id
- sm:thunder::2023-12-27
Related — same bug class· private-key