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 game ecosystem platform SeascapeNetwork stated that the private key of an early investor was stolen after the token was released today, which led to hackers obtaining 18,750 CWS in the investor's wallet. According to Etherscan data verification, this address has changed all CWS to ETH, and then recharged it to the Ethereum mixing platform Tornado.Cash several times, which is close to 330 ETH, which is equivalent to USD 500,000. Attack method (per SlowMist): Private Key Leakage. Reported loss: $ 500,000.
Primary source
https://www.jinse.com/lives/229955.html ↗Sourced from
slowmist
Technical record
- chain
- ethereum
- protocol
- SeascapeNetwork
- bug_class
- private-key
- date_occurred
- 2021-03-01
- loss_usd
- $500,000
- source_id
- sm:seascapenetwork::2021-03-01
Related — same bug class· private-key