← Radar

Incident case file

Sign in to watch

MEXC — Unrevoked attacker API key drains recovered user account

Incident date Sep 24, 2026Last updated Oct 8, 2026

3 views

ResolvedCEX (MEXC) — USDT and ONE withdrawalsExchange account takeover (unrevoked API key)Cluster: MEXC-API-2026-09

Estimated loss

$340K

Affected users

1
Group joining is coming soon.

Investigation

50%

Facts and investigation

Ledger

Attacker

MISSING — no wallet address was published. Known only: a session from a Jakarta IP address and a withdrawal-enabled API key created on Sep 24, 2026 at 21:05:42 UTC. Manual recovery: read the withdrawal screenshots in the long X thread posted by the affected user @shuangfei8 (about Sep 28, 2026; the short reply post contains no address), or ask MEXC for the destination addresses under ticket M2026092712031.

Funds moved to

MISSING — 322,110 USDT and 9,133,999 ONE were withdrawn in six transactions between 20:12:45 and 20:25:49 UTC on Sep 26, 2026, to two destination addresses. Only the start of the first address was published (0xd3f… ending …96427; first withdrawal of 1 USDT at 20:12:45 UTC); the second is unknown. Manual recovery: same X thread, or the exchange's withdrawal record.

Linked

No on-chain wallets identified. Support ticket M2026092712031. MEXC CEO Vugar Usi Zade announced full compensation of the affected user (Sep 28-29, 2026); MEXC later said it had reached an agreement with the user and considered the matter resolved, without publishing terms.

Chronology

1 beat
  1. Sep 24, 2026 at 19:10 UTC (Sep 25, 03:10 Beijing time) a security-settings reset email the user had not requested was approved about ten minutes later. The attacker then logged in from a Jakarta IP address, bound a Google Authenticator and created a withdrawal-enabled API key at 21:05:42 UTC, 83 seconds after the login. On Sep 25 at 02:55 UTC MEXC's risk review froze the account and restored the original email, but the API key was left active. The user changed the password and authenticator on Sep 26, which triggered a 24-hour withdrawal hold. Twenty-seven minutes after the hold expired, between 20:12:45 and 20:25:49 UTC on Sep 26, six withdrawals through the still-active API key took 322,110 USDT and 9,133,999 ONE (about $340,000). The user went public on Sep 28 with a long X thread. One outlet (TechFlow) claimed the attacker passed identity checks with a deepfake video; MEXC did not confirm this. MEXC confirmed the API-key path, announced full compensation on Sep 28-29, and later said the matter was resolved. Destination addresses and any onward movement are not public.

Sources and coverage

Victim testimonies

No testimonies yet.

+ Add my testimony → (coming soon)