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
According to an official tweet from Web3 liquidity provider Orderly Network, their Discord server has been compromised. The official team advises users not to click on any links until the situation is fully resolved to avoid potential losses. Attack method (per SlowMist): Account Compromise. Reported loss: -.
Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Orderly Network
- bug_class
- private-key
- date_occurred
- 2024-08-29
- loss_usd
- —
- source_id
- sm:orderly-network::2024-08-29
Related — same bug class· private-key