Bitget Loses $351.6M in Hot Wallet Breach, Withdrawals Frozen
Bitget confirmed approximately $351.6 million in unauthorized transfers from its hot and warm wallet layers on September 24, 2026. Withdrawals are frozen, the attack vector is unknown, and the exchange's $464M protection fund claim rests on unverified composition.
Withdrawals are frozen for every Bitget user while the exchange investigates one of 2026's largest confirmed exchange security incidents.
Key takeaways
- Bitget confirmed approximately $351.6 million in unauthorized transfers from its hot and warm wallet layers, detected at 18:31 UTC on September 24, 2026, with the attack vector still unknown.
- CEO Gracy Chen says the exchange's User Protection Fund holds over $464 million and covers the entire loss, but the fund's asset composition has not been independently verified.
- Withdrawals are suspended for all users, including those whose assets were untouched by the exploit, which is counterparty risk made visible in real time.
Bitget CEO Gracy Chen confirmed on September 24, 2026 that the exchange suffered unauthorized transfers from portions of its hot and warm wallet infrastructure, with losses estimated at approximately $351.6 million, per her X security notice. The breach is among the largest confirmed exchange security incidents of 2026, and withdrawals remain frozen across the platform while the investigation proceeds.
What Happened and What Bitget Is Claiming
Bitget's security systems flagged unauthorized transfers at 18:31 UTC and triggered emergency protocols immediately, according to Chen's post. The losses, self-reported at approximately $351.6 million, are nearly double the $174 million to $183 million range that blockchain security researchers estimated in the hours before Bitget confirmed the incident.
Chen says the breach was contained to the hot and warm layers of Bitget's three-tier wallet architecture, with cold wallets described as "fully secure." That claim is self-reported and has not been independently verified by forensic analysts at time of publication.
Onchain researchers including PeckShield and Hacken flagged suspicious movements from Bitget-labeled addresses earlier in the day. The attacker consolidated assets across multiple chains (ETH, USDT, USDC, AVAX, BNB, and XAUT) into a single fresh wallet, then swapped freezable stablecoins into ETH before issuers could intervene. The exploiter address has been tagged as "Bitget Exploiter 1" on Etherscan by independent researchers. Bitget said law enforcement and onchain security firms have been notified, though no law enforcement agency has publicly acknowledged the report.
The attack vector remains unknown. Chen was direct: "We will not speculate on the attack vector until the investigation is complete." A full incident report, including root cause and corrective measures, is promised within 24 hours.
The Protection Fund Math Deserves Scrutiny
The number Bitget wants you to focus on is $464 million. Chen stated that the exchange's User Protection Fund "currently holds over $464 million" and that the full $351.6 million loss falls within its coverage. On paper, that is a 132% coverage ratio with roughly $112 million in headroom.
Three questions that paper ratio does not answer: what assets make up the fund, are they liquid, and are they genuinely segregated from Bitget's operating capital? The fund's composition is not publicly audited in real time. The same entity that just lost $351.6 million is the one asserting the fund is whole.
Chen's closing statement was firm: "Bitget has navigated multiple market cycles. We will not run from this. Every dollar and every decision will be accounted for, transparently and in full." That commitment matters, and the 24-hour incident report will be the first real test of it.
The Lesson That Predates the Headline Number
The attacker's playbook is instructive. Swapping USDT and USDC into ETH immediately is standard procedure: once stablecoins move, issuers can freeze them at the contract level. ETH has no such issuer. That dynamic only exists because Bitget's custody stack spans multiple token types with different counterparty structures.
Bitcoin held in self-custody has no issuer to call and nothing to freeze, which is a security property, not a limitation.
The withdrawal freeze is the real story for anyone who holds assets on Bitget today. Users whose funds were never touched by the exploit cannot exit while the review is underway. This risk was always present in custodial structures; the hack made it legible.
This pattern has played out before in custodial and federated structures, which carry structural exposure regardless of how they are architected. Regulatory frameworks meant to address exactly this class of risk cannot return funds from a frozen exchange.
This is not FTX. There is no contagion signal, no insolvency claim, no evidence of socialized losses beyond the breach itself. Bitget appears to be responding in good faith and quickly. The thesis here is narrow: the protection fund claim is only as strong as the fund's actual liquidity and independence from exchange assets, and a self-reported figure during an active security incident is not a substitute for that verification.
The trigger that disproves it: Bitget pays every affected user in full, on time, with no haircut, and an independent attestation confirms the fund was genuinely segregated and never double-counted. If that happens, the coverage ratio holds. If payouts stretch or the fund composition turns out to include illiquid or exchange-native assets, the math breaks.
What to Watch
The 24-hour incident report is the first real checkpoint. Composition of the protection fund (BTC, ETH, exchange tokens, or IOUs) matters more than the headline figure. Any delay in withdrawal restoration beyond the security review window will be a signal worth tracking. Independent forensic confirmation of the cold wallet integrity claim is still outstanding.
Update, September 24, 2026
Hours after confirming the breach, Gracy Chen hosted a live Q&A on X where she pointed toward a state-level actor. Chen said preliminary findings link IP addresses to VPN services used by a North Korean group, and that security investigators had flagged similarities with previous North Korean attacks. Her exact words: "We've identified some IP addresses that match the VPN choices by a certain DPRK group."
Chen said Bitget believes the Lazarus Group, a North Korean state-backed hacking operation, was responsible, though no technical evidence supporting that attribution has been published.
Investigators concluded the hackers moved funds directly rather than attempting to forge user withdrawal requests, and that the attackers did not obtain Bitget's cold-wallet or hot-and-warm-wallet private keys.
Chen also said the exchange does not believe the breach was an inside job.
The DPRK attribution, if it holds, fits a well-worn pattern. North Korean hackers were linked to an estimated $2.02 billion in crypto theft in 2025, including the roughly $1.5 billion Bybit exchange hack, which the FBI attributed to North Korea. IP-based attribution via VPN infrastructure is thin evidence at this stage and no law enforcement agency has corroborated Chen's claim, so treat the Lazarus angle as a working hypothesis, not a conclusion. Some stolen funds were reported recovered, though Bitget did not disclose an amount.
Update, September 25, 2026
Circle and Tether have moved to blacklist a wallet tied to the hack, but the numbers tell the real story. Circle blacklisted "Bitget Exploiter 8" at 05:00 UTC Friday, locking roughly 99,990 USDC and 218,023 USDT at the contract level, with Tether following via its multisig hours later. Total frozen: $318,000 out of a breach in the hundreds of millions.
The reason that number is so small is the same reason this story matters beyond Bitget. The frozen wallet also held around 170 ETH, but that portion remains untouched, because issuers can blacklist their own tokens at the contract level but no one can freeze Ethereum itself. The attacker's playbook, swapping freezable stablecoins into ETH before issuers could respond, worked almost perfectly. Other exploiter addresses still hold more than 63,000 ETH, which no issuer can freeze.
Circle's response was faster this time than after April's Drift hack, when critics said it let about $232 million in stolen USDC move across chains without stepping in. That is worth noting, but speed only matters if the asset can actually be stopped. Stablecoins can be frozen because they have issuers with admin keys. Bitcoin cannot be frozen because it has neither. Every exchange breach that ends with funds parked in ETH or BTC is a live demonstration of why custodial risk and counterparty risk are two separate problems, and why sound money with no issuer is not a feature request but a security property.
Update, September 29, 2026
Bitget reopened Bitcoin withdrawals at 08:00 UTC on September 28 in a phased rollout, and users wasted no time. The exchange processed 9,585 Bitcoin withdrawal orders totaling 4,098 BTC in the opening stretch. CEO Gracy Chen told Bloomberg Television that over 4,000 BTC worth more than $334 million at current prices moved out in the first hour alone, saying "those hundreds of millions [in bitcoin withdrawals] actually most of them happen on the first hour of the withdrawal restart."
Ether and USDT withdrawals followed Bitcoin, with other tokens, fiat, and peer-to-peer services set to resume October 2.
The aggregate picture is starker. Bitget recorded roughly $463 million in net outflows in the 24 hours into Tuesday, and the surge marked the largest one-day net outflow since data aggregator DefiLlama began tracking proof-of-reserves four years ago.
The exchange currently holds about $5.7 billion in reserves. That last figure is the only reason this does not rhyme more directly with FTX, but the behavioral signal is the same: users locked out of their funds by an exchange's security failure will exit the moment the door opens.
Bitcoin specifically is the asset users reached for first. That is not a coincidence. Every bitcoin that left Bitget in that first hour moved into a wallet where no exchange, no issuer, and no hacker can freeze or redirect it. Meanwhile, recovering the stolen Bitget funds is becoming more difficult as the assets are fragmented across bridges, cross-chain protocols, and privacy services.
Blockchain investigator ZachXBT said Chinese illicit actors were laundering proceeds from the exploit on behalf of hackers he described as allegedly linked to North Korea, with funds being chain-hopped and deposited into mixing services including Wasabi. The contrast could not be drawn more cleanly: stolen funds scattered across chains and mixers, while users voted with 4,000 BTC in a single hour to take their own coins somewhere no one else can touch them.
Update, September 30, 2026
SlowMist's interim investigation report released today confirms that this was not a smash-and-grab. The attackers first ran code inside a compromised server on August 31, nearly four weeks before the theft, making the dwell time 25 days.
The entry point was a zero-day vulnerability in a third-party security product, referred to only as "Product A," which Bitget had deployed on its infrastructure. The attackers were not loud. They were patient.
In the early hours of September 25, the attackers used compromised internal accounts to infiltrate another security product management platform, uploading customized malicious tools in batches to forge withdrawal parameters and trigger the withdrawal process.
An employee identity and a custom withdrawal tool then let the attackers move funds for 2 hours and 52 minutes.
SlowMist has not yet disclosed the attacker's identity, nor announced the final scale of losses or the full scope of affected systems.
On the laundering side, the picture is getting messier. SlowMist's threat-tracking arm Mistrack flagged suspected North Korean scripts on September 30 routing stolen funds via CoW Protocol and Chainflip.
Near Intents blocked most of a $50 million laundering attempt, letting $166,000 through and freezing $503,000. The rest keeps moving. A 25-day undetected presence inside a major exchange is a damning indictment of centralized custody monitoring. The attackers did not need private keys. They needed patience and a vendor nobody had patched yet.
Sources
Frequently Asked Questions
Are Bitget user funds safe right now?
Bitget says yes, citing a $464 million protection fund that it claims covers the full $351.6 million loss. But withdrawals are paused during the security review, meaning users cannot access any funds regardless of that assurance. The protection fund's composition has not been independently verified. Whether user assets are ultimately made whole depends on the fund being both liquid and genuinely segregated from exchange operating capital.
What is the difference between a hot wallet and a cold wallet, and why does it matter here?
Hot wallets are internet-connected and used to process day-to-day withdrawals. Cold wallets are offline and theoretically inaccessible to remote attackers. Bitget operates a three-tier system (hot, warm, and cold) and reports only the hot and warm layers were breached.
The structural tradeoff is unavoidable: exchanges must keep enough in hot wallets to stay operationally liquid, which means a meaningful fraction of assets is always exposed to online attack vectors. Self-custody eliminates this exposure entirely.
Why did the attacker swap stablecoins into ETH?
USDT and USDC are freezable at the issuer level. Once Tether or Circle identifies a theft address, they can blacklist it and render the tokens immovable. ETH has no such mechanism.
Swapping freezable assets into ETH immediately after an exploit is the standard playbook to prevent issuers from clawing back funds onchain. It worked here: the window between the transfers and any potential freeze was too short to stop the conversion.
