Bitget Rebuilds Protection Fund to $309M After $388M Hack

Six days after a $388M hack, Bitget has rebuilt its Protection Fund to $309M and resumed withdrawals without charging customers.

@sharedot

Bitget Rebuilds Protection Fund to $309M After $388M Hack

By @sharedot · · 6 pages

  • Crypto
  • Bitget
  • Exchange Hack
  • Protection Fund

Six days after a $388M hack, Bitget has rebuilt its Protection Fund to $309M and resumed withdrawals without charging customers.

Bitget replenished its fund within a week

Six days after hackers drained roughly $388 million from Bitget on September 24, 2026, the exchange's Protection Fund — which fell below $200 million as it absorbed customer losses — had been rebuilt to $309 million by September 30, approximately 3,705 BTC, per aol.com.

That is still about a third smaller than its pre-hack level of around $464 million. Crucially, customers were compensated through the fund rather than asked to cover the theft themselves.

Withdrawals resumed in stages: Bitcoin on September 28, Ethereum on September 29, USDT on September 30, and the rest of the exchange's cryptocurrencies on October 2.

Hackers hit software, not keys

According to aol.com, the attackers never compromised Bitget's private keys.

Instead, CEO Gracy Chen said they exploited vulnerabilities in third-party software the exchange had acquired, stole internal login credentials, and issued fake withdrawal requests that drained the online hot and warm wallets while offline cold wallets stayed secure.

The breach came just 18 days after a separate $320 million drain from the Liquid Network, which aol.com notes made September 2026 an especially costly month for crypto hacks based on DeFiLlama data.

Reserves held, but recovery is scarce

Bitget's proof of reserves published September 29 showed 131% overall coverage, including 142% for Bitcoin and 110% for Ethereum, meaning the exchange held more assets than it owed customers, per aol.com.

Recovery of the stolen funds is another matter: investigators froze only $821,000 of the haul, while NEAR Intents flagged over $50 million in transfers but froze just around $503,000, as 24/7 Wall St. reports.

Launderers moved funds through THORChain — which refused Bitget's block request and saw volume spike to $678 million in two days — and pushed 2,746 ZEC worth about $3.9 million into Zcash's Ironwood shielded pool.

Trust remains the open question

The key caveat, as aol.com lays out, is that Bitget's Protection Fund is discretionary: the exchange controls it under its own internal policies rather than any regulatory requirement, so customers were covered only because Bitget chose to pay.

Holding crypto on an exchange means trusting the platform's private-key custody entirely.

aol.com suggests the $309 million level is a benchmark to watch — sustained reserves above 100% and a rebuilt fund justify staying, while an unexplained drop below $309 million would be a signal to reconsider custody.

NEAR's own $3.8 million Intents exploit on October 1, fully returned by the hacker within a day, underscores that even the protocols catching stolen funds face bridge risk, per 24/7 Wall St.

Sources

  1. aol.com › Bitget Rebuilt a $309 Million Protection Fund After a $388 Million Hack. Is Your Crypto Safe on an Exchange?
  2. 247wallst.com › NEAR Blocked $50 Million of Bitget's Stolen Money, Then Lost $3.8 Million of Its Own Two Days Later

More on Crypto