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
Solar, the official Solana Mandarin community, highly suspects its official X account (@Solana_zh) has been hacked. The team currently lacks access and is working urgently with X support to resolve the issue. Recovery time is TBD. Attack method (per SlowMist): Account Compromise. Reported loss: -.
Primary source
https://x.com/xueqiu88/status/2015990208471437490 ↗Sourced from
slowmist
Technical record
- chain
- solana
- protocol
- Solar
- bug_class
- private-key
- date_occurred
- 2026-01-27
- loss_usd
- —
- source_id
- sm:solar::2026-01-27
Related — same bug class· private-key