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
Virtuals Protocol announced on X that their official Discord server has been compromised. They advised users not to click on any posts or private messages from administrators until further notice. Attack method (per SlowMist): Account Compromise. Reported loss: -.
Primary source
https://x.com/virtuals_io/status/1876921173340246492?s=46&t=DLwbX9Nw4QECiyZQ0av-fg ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Virtuals Protocol
- bug_class
- private-key
- date_occurred
- 2025-01-08
- loss_usd
- —
- source_id
- sm:virtuals-protocol::2025-01-08
Related — same bug class· private-key