Bitget has restored its protection fund to roughly $300 million after absorbing a $388 million security breach, according to a report from CryptoSlate published October 2, 2026. The exchange is framing the move as evidence that its balance sheet took the hit so customer funds did not. The restored backstop sits separate from customer reserves, and individual claims remain subject to Bitget's own assessment.
The headline number matters because it is the exchange's answer to the question every user asks after an incident: is my money still there, and who pays if it is not. By rebuilding a dedicated fund rather than quietly drawing down reserves, Bitget is trying to show that the loss was contained to corporate capital.
The breach that triggered the rebuild
The $388 million figure traces back to the September 24 incident that Bitget later tied to a zero-day in a third-party security tool. Stolen funds moved quickly across chains. Blockchain investigators flagged that North Korea-linked actors routed proceeds through Chainflip and CoW, the same laundering pattern seen after other large exchange hacks.
Recovery efforts hit a wall at the protocol level. When Bitget asked for help freezing the stolen assets, THORChain rejected the call to block the funds on decentralization grounds, a reminder that an exchange cannot assume the rest of the ecosystem will act as its collections department. With clawback off the table, rebuilding the fund became the realistic path back to normal operations.
Separate fund, same review process
Two details in the report deserve attention. First, the restored fund is separate from customer reserves. That separation is the point of a protection fund: it exists so an exchange can cover losses without touching the assets users deposited. A fund that drew from reserves would not be a backstop at all, just an accounting label on money that was never yours to begin with.
Second, claims remain subject to Bitget's assessment. The money being in place does not mean it flows automatically to anyone who files. Bitget decides what qualifies. For users, that is the gap between a marketing line and an enforceable guarantee. A protection fund is a discretionary promise from the exchange, not insurance with defined terms and an independent adjuster. Read it as a signal of intent and capital, not as a contract.
The phased return to service has moved in the same direction. Bitget had already restarted BTC withdrawals under a staged resumption before this fund restoration, so the backstop rebuild lands as the capital side of a recovery that was already underway operationally.
The custody lesson sitting underneath
The deeper takeaway is about where your assets live. Any balance held on a centralized exchange like Bitget carries counterparty risk: you hold a claim against the company, not the coins themselves. A protection fund softens that risk but does not remove it, because the same entity that lost the money also decides who gets reimbursed and how much.
That is the structural case for spending from your own wallet where it fits your needs. Self-custody card products keep assets under your keys until the moment of a transaction, which removes the exchange as a single point of failure for your stored balance. It is not a universal answer. Self-custody shifts the burden of security onto you, and a lost seed phrase has no claims desk. But it changes the failure mode from "the exchange got hacked and I wait for a ruling" to "I control the keys and the risk."
For users who keep funds on an exchange by choice, the practical move after an incident like this is boring but effective: enable every available security control, withdraw balances you are not actively trading, and treat a protection fund as a cushion rather than a promise of full recovery.
Overview
Bitget has rebuilt a roughly $300 million protection fund after a $388 million breach, keeping the backstop separate from customer reserves while reserving the right to assess claims case by case. The rebuild follows a September incident tied to a third-party zero-day, laundering through cross-chain routes, and a failed attempt to freeze the funds at the protocol layer. The restored fund signals that the exchange absorbed the loss with corporate capital, but a discretionary fund is not insurance. The durable lesson for users is custody: a claim against an exchange is not the same as holding your own assets.
