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
Kaito official representative Sandra (@sandraaleow) posted on X that Kaito AI founder Yu Hu and Kaito's X account have been compromised. However, no KAITO wallets have been affected. Attack method (per SlowMist): Account Compromise. Reported loss: -.
Primary source
https://x.com/sandraaleow/status/1900999678466126100?s=46&t=C99FI4Hm9YFZrc41IlEaog ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Kaito AI
- bug_class
- private-key
- date_occurred
- 2025-03-16
- loss_usd
- —
- source_id
- sm:kaito-ai::2025-03-16
Related — same bug class· private-key