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
An admin on the Fetch discord server showing the username "Atari_buzz1kLL" has had their @discord account compromised. Please do not interact with any posts on our Discord until the issue has been resolved. There is no Fetch airdrop happening right now. Attack method (per SlowMist): Account Compromise. Reported loss: -.
Primary source
https://twitter.com/wublockchain12/status/1690679058147966977?s=46&t=DLwbX9Nw4QECiyZQ0av-fg ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- Fetch.ai
- bug_class
- private-key
- date_occurred
- 2023-08-13
- loss_usd
- —
- source_id
- sm:fetch-ai::2023-08-13
Related — same bug class· private-key