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 official X account of the blockchain AI project Aizel Network was hacked at noon on January 11 and is currently in the process of being recovered. The official reminder to users is to be cautious of the content posted by this account, do not trust any token information, and avoid clicking on any suspicious links or participating in any suspicious activities. Attack method (per SlowMist): Account Compromise. Reported loss: -.
Primary source
https://foresightnews.pro/news/detail/62891 ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Aizel Network
- bug_class
- private-key
- date_occurred
- 2025-01-11
- loss_usd
- —
- source_id
- sm:aizel-network::2025-01-11
Related — same bug class· private-key