Bitget says $388m hack came from a third-party zero-day as withdrawals resume
The exchange has reopened withdrawals after a $388m breach on 24 September. Only about $1.1m of the stolen funds has been frozen, and the CEO says she is not optimistic about recovering the rest.
Why it matters: It shows how a flaw in a third-party tool, not a stolen key, can drain a major exchange, and how little of the money is usually recovered.
Reviewed by Jayshree MajumdarFact-checked by Ishu Aggarwal
In short
- Bitget says attackers stole about $388m on 24 September via a third-party zero-day, not compromised private keys.
- SlowMist traced the earliest malicious activity to 31 August, before the assets were moved out.
- Withdrawals resumed from 28 September, starting with Bitcoin, ether and USDT, after a multi-day halt.
- Only about $1.1m of the stolen funds has been frozen; CEO Gracy Chen is not optimistic about recovery.
What happened
Bitget has confirmed that attackers stole about $388m from its hot and warm wallets on 24 September by exploiting a zero-day vulnerability in third-party security products, according to The Hacker News. The exchange first put the loss at $352m and raised it as tracing found more assets, CoinNess reported. Bitget runs a global crypto exchange where users trade and hold digital assets.
How it happened
The attackers did not take private keys. According to GoPlus Security, they breached a wallet backend, forged transaction data and made Bitget's signing flow approve transfers it should have blocked. The drain lasted about two hours and 25 minutes, GoPlus said, with roughly $185m moved in the first stretch.
SlowMist traced the earliest malicious activity to 31 August, according to The Hacker News. A service on one node of a third-party product was hit by a zero-day, and the attacker ran a hidden script to read a database password from an environment variable. Similar activity appeared on two other nodes on 23 and 25 September, SlowMist said, meaning the environment was compromised before the assets moved.
Bitget said the attackers used high-level internal credentials to issue fraudulent withdrawal commands that bypassed existing risk controls, The Hacker News reported. The exchange has notified the vendor and disabled the affected function until a fix is ready. The incident touched 11 blockchains, including Ethereum, XRP Ledger, Zcash, TRON, Arbitrum, Optimism, Base, BNB Smart Chain, Avalanche, Algorand and Celestia.
The laundering started fast. Within 41 minutes of the breach, the attackers swapped stablecoins into native assets to dodge issuer blacklists and routed funds through THORChain, a cross-chain liquidity protocol, to break the trail and consolidate into Bitcoin, according to the source text. THORChain declined a request to block addresses tied to the stolen funds, citing decentralisation, CoinNess reported.
Freezes have been small next to the haul. Tether and Circle blacklisted attacker addresses and froze roughly $340,000 left in hot wallets, the source text says. NEAR Intents blocked over $50m in tainted assets passing through its routing pathways and intercepted another $503,000 mid-transaction, Odaily reported. In total, close to $1.1m has been frozen, according to The Hacker News.
Who is affected
Bitget suspended withdrawals for several days, then began a phased restart on 28 September, starting with Bitcoin, ether and USDT, according to the source text. The reopening triggered a $463m net outflow in a single 24-hour window as users pulled funds, the source text says. Ethereum withdrawals resumed on 29 September, according to MSN, and Bitcoin withdrawals restarted later, CryptoBriefing reported.
On-chain analyst ZachXBT said a group with Chinese roots, identified as Alias 4, helped launder the stolen funds and was also linked to the $292m Kelp DAO exploit this year, CoinNess reported. The same group is openly seeking order support in public Discord servers and Telegram channels, ZachXBT said, according to PANews. The Bitget hacker has moved about $3.8m of stolen ZEC into Zcash's shielded pool, FinanceFeeds reported.
Bitget says user funds are safe and fully backed. The loss fell within its $464m User Protection Fund, which the exchange says covers the full amount, and it drew on corporate reserves to top the fund back above $300m, according to the source text. Its latest audited Proof of Reserves snapshot shows a 131% reserve ratio across 19 major assets, the source text says.
Crypto hack losses jumped 462% to $766m in September, with Bitget and Liquid Network the biggest thefts of 2026, Yahoo Finance reported. The wider market has been soft: Bitcoin traded at $83,722 and ether at $2,692, with the total crypto market value at $2.85tn, down 3.66% in 24 hours, according to InvestIn.News market data at 10:42 UTC on 1 October.
What people are saying
Users who got their money out have been posting about it. On X, nomani said the withdrawal went through without issues and their trust in Bitget had grown, SIDRA COMMUNITY thanked the exchange for a successful withdrawal, Ejexx said they had finally got their money out, and posha lush said the withdrawal was successful and they could now eat.
Alhamdulillah, successfully withdrew all my funds without any issues! The transfer was smooth and completely seamless. My trust in Bitget has definitely grown even stronger after this experience. Keep up the great work! 🚀🙌
Thank you, Bitget Exchange! 🙏❤️
I’m so happy to confirm that I have received my withdrawal successfully. Thank you for your support and service! 💐🤝 pic.twitter.com/dveogHarLN
Gm
Finally got my money out of Bitget. pic.twitter.com/sqhspof4N0
Withdrawal successful. Thanks bitget. I can now eat 🤣🤣
What happens next
It is not clear yet whether Bitget will make users whole beyond the protection fund, or how much of the stolen $388m can be recovered. CEO Gracy Chen has said she is not very optimistic about recovery, according to the source text. The third-party vendor has not been named, and the fix for the affected function is still pending.
Our view
This is a serious blow to confidence in centralised exchanges, and it lands on an industry still living with the memory of FTX. The technical facts are stark: attackers never took private keys, yet they walked off with $388m by abusing a third-party zero-day and the exchange's own signing flow. That is a failure of architecture, not of one password. The response has been better than most. Withdrawals restarted within days, the $464m User Protection Fund is said to cover the loss, and reserves are reported at 131%. But only about $1.1m has been frozen, and the CEO is not optimistic about recovery. If the vendor fix and a fuller accounting of the outflow arrive, the containment case holds; if not, users should treat self-custody as the default.
Follow the latest updates as they happen on NewsFeeds.
Sources
- Odaily: Bitget hack took $388m; NEAR Intents froze $503,000 of funds (2026-09-28)
- CoinNess: ZachXBT links Chinese-rooted group to laundering of $387m stolen from Bitget (2026-09-28)
- PANews: ZachXBT: launderers tied to Bitget case seek order support on Discord, Telegram (2026-09-28)
- CoinNess: THORChain declines request to block addresses tied to Bitget hack funds (2026-09-28)
- Wu Blockchain (Telegram): GoPlus says Bitget's $388m hack exploited transaction-signing trust chain, not private keys (2026-09-26)
- Decrypt: Bitget says attacker faked transfer requests to steal $388m from wallets (2026-09-25)
- Wu Blockchain (Telegram): Bitget raises confirmed incident amount to $388m, withdrawal plan due 26 Sept (2026-09-25)
What to watch: Bitget has not named the third-party vendor or said when the affected function will be fixed; recovery of the stolen funds remains unresolved.
Live updates on NewsFeeds:StablecoinsBy Keshav Aggarwal
Disclosure: Keshav Aggarwal holds small amounts of crypto as long-term investments. He does not trade any asset he writes about within 24 hours of a story, and is not paid by any company covered on this site, updated 6 October 2026. Our holdings and trading policy.
How this was produced: the writer drafted this piece with AI help, from the reporting and sources it names, then checked and edited it. Read our Editorial and AI policy. Spotted a mistake? See Corrections.
Not investment advice. Read the risk disclaimer.