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 Turkish cryptocurrency exchange BtcTurk has reportedly suffered another hack. BtcTurk acknowledged “unusual activity” in its hot wallets and has suspended deposits and withdrawals. However, the exchange did not disclose further details regarding the scale of the attack. Attack method (per SlowMist): Unknown. Reported loss: $ 54,000,000.
Primary source
https://x.com/BtcTurkKripto/status/1955973500583170252 ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- BtcTurk
- bug_class
- private-key
- date_occurred
- 2025-08-14
- loss_usd
- $54,000,000
- source_id
- sm:btcturk::2025-08-14
Related — same bug class· private-key