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
Chain game project Vulcan Forged officially tweeted that 148 wallets holding PYR were hacked, and more than 4.5 million PYR had been stolen. It then stated: Most of the PYR has been returned from the treasury to the affected wallets. Attack method (per SlowMist): Private Key Leakage. Reported loss: $ 102,820,974.
Primary source
https://rekt.news/zh/vulcan-forged-rekt/ ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Vulcan Forged
- bug_class
- private-key
- date_occurred
- 2021-12-13
- loss_usd
- $102,820,974
- source_id
- sm:vulcan-forged::2021-12-13
Related — same bug class· private-key