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 DeFi project Mozaic was exploited, who stole approximately $2 million from the project. According to Mozaic, this individual was a Mozaic developer who had illegally obtained the private keys of a security module by compromising the data of a core team member. They also stated that about 90% of the stolen funds have now been frozen on MEXC. Attack method (per SlowMist): Insider Manipulation. Reported loss: $ 2,000,000.
Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Mozaic
- bug_class
- private-key
- date_occurred
- 2024-03-15
- loss_usd
- $2,000,000
- source_id
- sm:mozaic::2024-03-15
Related — same bug class· private-key