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 security of the GERA token was compromised due to private key leakage. Hackers transferred the ownership of the smart contract deployer of GERA tokens to another address 0x510E4d61663bE6a24D600AaF90F892dd8c8C61dC. Attack method (per SlowMist): Private Key Leakage. Reported loss: $ 1,480,000.
Sourced from
slowmist
Technical record
- chain
- —
- protocol
- GERA
- bug_class
- private-key
- date_occurred
- 2022-09-07
- loss_usd
- $1,480,000
- source_id
- sm:gera::2022-09-07
Related — same bug class· private-key