Skip to main content
AVOID.NET

Bitget Exchange — September 2026 Backend Hack ($387.5M)

avoid.net/bitget-exchange-september-2026-backend-hack-387-5m→0/100·82% conf.
[✓ FACT-CHECKED]· reviewed 2 times · last review 28 Oct 2026

Last changed 2026-11-03 · Community evidence — A moderator rejected a piece of community-submitted evidence: Same URL already accepted for this page (3cdd1387-fe91-452e-af1f-13602f81c510). Trust score now 0. Version history →

Provisional: this score is the AI investigator's judgment, not yet calculated by our published formula. Treat it as indicative. How scoring works →

anchored·7xuVhw…CJiv

Latest developments

last 45 days
  1. October 2026Bitget publicly confirms the zero-day flaw in third-party security products as the root cause of the breach.
  2. October 2026Bitget's published timetable targets this date for resuming remaining cryptocurrency, fiat and peer-to-peer withdrawal services.
  3. September 2026Bitget and SlowMist publish updated findings revising the loss estimate to approximately $387.5 million after identifying additional affected Zcash and TRON transfers; Bitget says its User Protection Fund has been restored above $300 million and resumes USDT withdrawals on several chains.
  4. September 2026Researcher ZachXBT publishes online identities of five alleged operators (aliases Cc, jack, Melon, lolo/Marin, HELP ME) he says are laundering the stolen funds, describing them as Chinese actors allegedly working for North Korean operators.
  5. September 2026Bitget CEO Gracy Chen publicly states North Korean-linked hackers are the likely perpetrators, citing IP, behavioral and on-chain evidence; initial loss estimate given as approximately $351.6 million (also reported as roughly $352 million).
All 9 events in the timeline →

Summary

On September 24-25, 2026, attackers stole approximately $387.5 million from Bitget's hot and warm wallets after exploiting a zero-day vulnerability in two third-party security appliances, according to Bitget and forensic reviews by SlowMist and Google Cloud's Mandiant. Bitget CEO Gracy Chen said the attack was "very likely" carried out by North Korea-linked hackers, citing IP addresses, behavioral patterns and on-chain signatures, while researcher ZachXBT separately identified five alleged Chinese operators he said were laundering the stolen funds on behalf of North Korean actors. Bitget halted withdrawals, pledged to cover losses from a User Protection Fund exceeding $464 million, and restored that fund above $300 million by September 30, 2026; recovery of the stolen assets themselves remains limited.

Connected Entities

4 entities
Organizations
□Bitget Hack — SlowMist and Mandiant Zero-Day Attribution (September 30, 2026)□Bitget Hack — SlowMist and Mandiant Zero-Day Attribution (September 2026)
Exchanges
△Bitget Exchange — September 2026 Backend Hack ($387.5M)
Protocols
⌂Bitget Hack Third-Party Zero-Day Vendor (Unidentified, October 2026)
Have evidence about Bitget Exchange — September 2026 Backend Hack ($387.5M)?
7
Accepted
8
Under review
1
Rejected / revoked

Community submissions

8 submissions awaiting moderator review.

Timeline(9 events)

August 2026

SlowMist later identifies this as the earliest logged malicious activity against a compromised third-party security appliance ("Product A").

Cointelegraph

September 2026

SlowMist reports similar suspicious activity detected on two other nodes.

BleepingComputer

24 September 2026

Mandiant's investigation finds the threat actor gained unauthorized privileged access to Bitget's third-party security appliances A and B and placed a web shell on Appliance B.

BleepingComputer

September 2026

Attackers use a custom withdrawal tool to execute unauthorized transfers from Bitget's hot and warm wallets; the earliest verified theft transfer occurs at 02:31 UTC+8, with activity spanning roughly two to three hours. Bitget suspends withdrawals.

Cointelegraph / BleepingComputer

September 2026

Bitget CEO Gracy Chen publicly states North Korean-linked hackers are the likely perpetrators, citing IP, behavioral and on-chain evidence; initial loss estimate given as approximately $351.6 million (also reported as roughly $352 million).

The Record / CNBC

September 2026

Researcher ZachXBT publishes online identities of five alleged operators (aliases Cc, jack, Melon, lolo/Marin, HELP ME) he says are laundering the stolen funds, describing them as Chinese actors allegedly working for North Korean operators.

CryptoTimes

September 2026

Bitget and SlowMist publish updated findings revising the loss estimate to approximately $387.5 million after identifying additional affected Zcash and TRON transfers; Bitget says its User Protection Fund has been restored above $300 million and resumes USDT withdrawals on several chains.

CryptoTimes

October 2026

Bitget's published timetable targets this date for resuming remaining cryptocurrency, fiat and peer-to-peer withdrawal services.

CryptoTimes

October 2026

Bitget publicly confirms the zero-day flaw in third-party security products as the root cause of the breach.

The Hacker News
Provenance & Audit Trail

Decision Log

  • #13rejectRecorded on Solana ✓11/3/2026, 11:18:10 PM
    slot 465080786 · hash EsgEfwuhJbw4zPPhpHsaRnZF3w6std3RXWAw89bhpTbB
  • #12acceptRecorded on Solana ✓11/3/2026, 11:18:04 PM
    slot 465080606 · hash 9j1kCKbEfns3kH8A75wTa9Z3m3Rs2AxavGKtCifsui8t
  • #11acceptRecorded on Solana ✓11/3/2026, 11:16:53 PM
    slot 465080443 · hash Fx5d31Amegdg1yCJtVAzy5GDMVN1TKuA3SBqeU8gcaJ2
  • #10accept-11Recorded on Solana ✓11/3/2026, 11:15:56 PM
    slot 465080210 · hash 6yLneR6JuZGZvSSWosySKWZ2SNmvVRBKkq5YCkBozKkv
  • #9accept-9Recorded on Solana ✓11/3/2026, 10:40:05 PM
    slot 465070050 · hash 43nCY197nWB5sVLgW7B3a7Y9ZZTyVUNvCxBVmPSrBTuC
  • #8accept-6Recorded on Solana ✓10/31/2026, 11:44:16 AM
    slot 463676202 · hash EwkMh6vYzSFu6WHTw7Wg5sJuZEXdpRNF8KJMqhcfvLAw
  • #7accept-3Recorded on Solana ✓10/31/2026, 3:43:14 AM
    slot 463541479 · hash FqFakTqgPm2iFwscSFAnLvdNxpv82u8cwvh9kvMuWAaM
  • #6accept-1Recorded on Solana ✓10/31/2026, 3:43:13 AM
    slot 463541473 · hash 9E3ZbQoUycC3BGrZXLNLY871tVQ8axHLWGD9p1oXq6Ft
  • #5review approveRecorded on Solana ✓10/28/2026, 12:46:28 AM
    slot 462278588 · hash 8zL8ZmM21JnD5Cz5FUCeZc9rVrqL7WZbaVzvaHoxM4fU
  • #4reviewRecorded on Solana ✓10/28/2026, 12:46:28 AM
    slot 462278580 · hash HTP9z7zZhRCUyzaa4dLFEtP1YS5k8bkv5fMGDnmgFpyY
  • #3review revise-8Recorded on Solana ✓10/27/2026, 6:34:49 AM
    slot 461970872 · hash 81jkJoMy7i3RsVemFdyoiRbQy7Y6JjpEadJAkT4iSEmc
  • #2reviewRecorded on Solana ✓10/27/2026, 6:34:46 AM
    slot 461970867 · hash V2KvpiAP7RnXeMruEqkj1989pdYswDWptDsTiKWEMgY
  • #1publishRecorded on Solana ✓9/29/2026, 12:05:25 PM
    slot 451636815 · hash CYvt7GxqgwyPGBd11aiRhuJofUHU19NDtGJqTcmRJhwm

This investigation is cryptographically anchored to the Solana blockchain (13 decisions). 18 of 20 cited source URLs have an Internet Archive snapshot.

Fact-checked 2026-10-2814 claims checked0 corrections pending0 applied⛓ anchoredSee findings →

model: claude-code-investigator

generated: 9/29/2026, 12:05:14 PM

last updated: 11/3/2026, 11:18:10 PM

6 views

avoid.net — verified advice for a post-truth world