Bitget Lost $351.6M From Hot Wallets and Its $464M Safety Net Is Now On the Clock
Bitget says about $351.6 million walked out of its hot and warm wallets. Cold storage stayed clean, withdrawals are frozen, and the exchange is betting its $464 million User Protection Fund can eat the whole thing. The 24-hour root-cause report is the part everyone should be watching.
ok wait because this is actually insane. Bitget says roughly $351.6 million got moved out of its hot and warm wallets without authorization. Cold storage? Untouched. Customer balances? Bitget says they're still accurate. Withdrawals? Paused while the team works out what happened.
Deposits and trading are still live. That's the strange part. You can put money in, you just can't pull it out right now. Bitget says it flagged the sketchy transfer addresses, looped in law enforcement, and brought onchain security firms into the review. A full incident report with root-cause analysis is supposed to drop within 24 hours. Until then, no public guessing. Honestly, smart move.
Here's the number that actually matters. Bitget's User Protection Fund holds more than $464 million. That's bigger than the $351.6 million estimate. So on paper, customers don't eat the loss. no but seriously. read that again. An exchange just absorbed a nine-figure hit and says its own balance sheet covers it.
But a protection fund isn't a magic eraser. Pausing withdrawals means people who wanted out are stuck, at least for now. And $351.6 million is an early estimate. Exploit numbers drift. They usually drift up.
My take: this is a cold-storage ad Bitget didn't pay for. Every time a hot wallet bleeds, hardware wallet makers and self-custody apps get a free commercial. The winners are anyone holding their own keys, plus the marketing teams at Ledger and Trezor, who are probably drafting posts as you read this. The losers are exchange trust and everyone who's been telling friends that a CEX is basically a bank. It isn't. It's a counterparty, and counterparties can get robbed.
Watch the 24-hour report. If the root cause is a key management failure, that's bad news for every exchange running similar infrastructure. If it's narrower, Bitget limps out bruised but breathing. Either way, move what you can't afford to lose.