Intel archive / Breaches and incidents
Bitget: $387.5 million stolen via a third-party flaw
Cryptocurrency exchange Bitget lost $387.5 million after an attacker used a flaw in a third-party security product to push fraudulent withdrawals past its risk controls.
Critical severity. Active. Moderate confidence. First reported 24 Sep 2026, last activity 28 Sep 2026. Briefing updated 29 Sep 2026.
AI-written summaries of public reporting, each checked against at least two sources from different publishers. Check the sources before you act. Last refreshed 2026-11-18 14:09 UTC. How this is made.
What is not settled: The North Korea attribution is the victim's own claim (Bitget's CEO), based on on-chain analysis and IP patterns; it has not yet been independently corroborated by a government agency or a second research team.
In plain words
What happened
A cryptocurrency exchange called Bitget was tricked into sending out $387.5 million of its customers' funds. The attacker did not break into Bitget directly; they broke into a security tool Bitget relied on, and used it to make Bitget's own systems approve fake withdrawals.
Who is behind it
Bitget's CEO has blamed North Korean state hackers, citing on-chain tracing and behavior patterns; that attribution has not yet been independently confirmed.
What they want
The stolen cryptocurrency itself, converted and laundered through the blockchain.
What they did
The attacker used a third-party product flaw to get high-level internal access, made two small test withdrawals that stayed under the radar, then large fraudulent withdrawals about 30 minutes later.
Who is at risk
Bitget customers with funds on the exchange at the time, and by extension any exchange or platform relying on the same third-party security product.
What to do
- If you use Bitget, watch official channels for guidance on affected accounts and any compensation process.
- Exchanges and platforms: audit trust placed in third-party security and custody tooling; a vendor's compromise can bypass your own controls entirely.
- Do not click links in messages claiming to help recover funds from this incident; heist news is reliably followed by recovery scams.
The technical version, for hunting and patching
What happened
An attacker exploited a vulnerability in a third-party security product used by Bitget to obtain high-level internal credentials, then inserted fraudulent withdrawal commands into wallet-related backend services, where they were processed as legitimate.
Who is behind it
Attribution to North Korean state-linked actors comes from Bitget's CEO, citing on-chain analysis and IP behavior; independent researcher confirmation was not yet available at time of writing.
What they want
Direct theft of exchange-held cryptocurrency, a signature DPRK objective when the attribution holds.
What they did
On 24 September 2026 at 18:31 UTC, two small test transfers stayed below Bitget's risk-control threshold and raised no alert; larger fraudulent transfers began about 30 minutes later and were executed by the wallet system, bypassing risk controls. Total losses: $387.5 million, per on-chain tracing.
Who is at risk
Bitget's own infrastructure was not the initial entry point; the exposure traces to a third-party security product's vulnerability, making this a supply-chain-style compromise for crypto custody.
What to do
- Treat vendor security products with the same access-review rigor as internal systems; a flaw there can grant internal-equivalent privilege.
- Alert on withdrawal patterns that include small test transactions followed by a volume spike, a known laundering-test pattern.
- Track official Bitget and law enforcement statements for indicators and any recovered-funds updates.
ATT&CK techniques
Sectors: Financial services. Regions: Global.
Sources
- Bitget Says Attacker Exploited Third-Party Security Product Flaw to Steal $388M, The Hacker News, 2026-09-28 (news)
- Bitget resumes Bitcoin withdrawals after $387.5 million crypto heist, BleepingComputer, 2026-09-28 (news)
Revision history
- 2026-09-29: First published.
Newer: Midnight Blizzard hijacks hotel Wi-Fi to phish travelers. Older: CVE-2026-35273: unauthenticated RCE in Oracle PeopleSoft.