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
Volo, a protocol in the Sui ecosystem, disclosed on X that Volo Vaults experienced a security vulnerability today, resulting in approximately $3.5 million in assets (WBTC, XAUm, and USDC) being stolen. Volo stated that it detected the attack and immediately notified the Sui Foundation and ecosystem partners, and has frozen all vaults to prevent further losses. Attack method (per SlowMist): Private Key Leakage. Reported loss: $ 3,500,000.
Primary source
https://x.com/volo_sui/status/2046715584201511351 ↗Sourced from
slowmist
Technical record
- chain
- sui
- protocol
- Volo Vaults
- bug_class
- private-key
- date_occurred
- 2026-04-21
- loss_usd
- $3,500,000
- source_id
- sm:volo-vaults::2026-04-21
Related — same bug class· private-key