🚨 What Bitget Confirmed
Bitget says it detected unauthorized transfers from some of its hot wallets at 18:31 UTC on September 24 and activated its emergency response procedures. The exchange later put the amount affected at approximately $351.6 million, a figure far above the early onchain estimates that circulated while the activity was still unfolding. The company has temporarily suspended withdrawals while it conducts a security review, though it says deposits and trading remain available. Bitget also says its cold wallets remain secure. These are important operational statements, but they are the company’s statements during an active incident, not a completed independent audit. The primary Bitget security notice is the right place to track the exchange’s own updates. For the first contemporaneous outside account, The Block’s onchain report documented transfers to a fresh address before Bitget disclosed its larger total.
🔎 Why The First Numbers Differed
Early figures near $170 million or $183 million reflected what analysts could observe quickly in wallets labeled as belonging to Bitget. Those movements involved assets including ETH, USDT, USDC, AVAX and BNB and were reportedly consolidated to a single address. Bitget’s later $351.6 million estimate indicates that the event extended beyond the earliest visible activity, including across multiple chains and wallet layers. That does not make either number a contradiction. It shows why the first number in a fast moving wallet incident is usually a floor, not a final ledger. CoinDesk’s reporting notes that independent researchers first flagged unusual movements before the company’s fuller disclosure. Cointelegraph’s account reports that Bitget identified Ethereum, XRP Ledger, Avalanche, BNB Smart Chain and Arbitrum among the affected networks. The useful distinction for readers is observed transfers versus the exchange’s running estimate.
🔐 Hot Wallets Are A Practical Tradeoff
An exchange needs some assets connected to operational systems in order to process customer withdrawals and other routine activity. Those are generally described as hot wallets. Cold wallets are designed to keep signing credentials away from internet connected infrastructure, which can reduce exposure but also makes them less convenient for immediate settlement. Bitget says the incident was limited to part of its hot and warm wallet layers, while cold wallets remained fully secure. That assertion has not yet been independently audited. Still, the episode is a clear reminder that custody risk does not disappear because an exchange has a cold storage policy. It is shaped by the wallets and systems actually used on a given day. Decrypt’s initial report described rapid transfers from wallets labeled as Bitget’s across several blockchains. The question now is whether Bitget’s controls, segmentation and response process operated as intended once those transfers were detected.
⏸️ A Withdrawal Pause Changes The User Experience
For customers, the immediate fact is simpler than the forensic story: withdrawals are paused. A temporary pause can be a sensible containment measure when an exchange needs to assess wallet exposure and protect remaining balances. It can also leave users unable to move assets at exactly the moment when they most want optionality. Bitget says user account balances remain accurate, deposits and trading continue, and withdrawals will resume after its review. Those statements deserve to be monitored against the actual return of withdrawal functionality. The exchange also says it has engaged law enforcement and onchain security firms and plans to publish a full report. The Block’s updated coverage confirms the pause and the stated plan for a report within 24 hours. Users should treat social posts about isolated withdrawal problems as discussion, not a substitute for the exchange’s status and their own account access.
🛡️ The Protection Fund Is A Claim To Test
Bitget says its User Protection Fund holds more than $464 million and fully covers the reported loss. If accurate, that is materially relevant: it would mean the exchange has identified a reserve larger than the stated $351.6 million affected. But a stated fund balance is not the same thing as a completed reimbursement process, a reserve audit, or proof that every operational impact has been resolved. The fund, its custody, liquidity, legal structure and the process for using it all matter. Investors should therefore avoid reading “covered” as a final settlement. CoinDesk reported the company’s claim that the fund exceeded $464 million, while Cointelegraph reported the same company position alongside the withdrawal suspension. Until Bitget provides the promised incident report, the fund is an important company assertion, not independently verified assurance.
📋 What To Watch From Here
The next meaningful update is not another estimate posted in the heat of the event. It is a specific incident report that explains the affected systems, scope, containment actions, root cause if known, and corrective measures. No attacker, cause or attribution has been proven in the reporting reviewed here, so readers should be wary of confident explanations that outrun the evidence. Watch for withdrawals to reopen in practice, not merely for a projected timetable. Watch for clear disclosure about the reported transfers and the protection fund, as well as whether independent security firms or law enforcement provide corroborating information. Bitget’s official notice remains the canonical source for what the company has formally said. For investors, this is a custody and transparency story rather than a price call. The test is whether the exchange can restore service and substantiate its assurances with evidence that holds up after the immediate crisis.
Sources
https://www.bitgetapp.com/support/articles/12560603896024
https://www.coindesk.com/markets/2026/09/24/crypto-exchange-bitget-loses-usd352-million-in-hack-claims-user-funds-are-safe
https://www.theblock.co/news/markets/2026-09-24-more-than-170-million-in-crypto-moves-from-bitget-wallets-unidentified-address-416345
https://cointelegraph.com/news/bitget-calls-security-withdrawal-claims-unverified-amid-178m-breach-reports
https://decrypt.co/379275/bitget-hack-183-million-crypto-exchange-wallets
Crypto Club and Mode Mobile communications are for informational purposes only, and are not a recommendation, solicitation, or research report relating to any investment strategy, security, or digital asset. All investments involve risk including the loss of principal and past performance does not guarantee future results.
Any information contained in this commentary does not purport to be a complete description of the securities, markets, or developments referred to in this material. The information has been obtained from sources considered to be reliable, but we do not guarantee that the foregoing material is accurate or complete. There is no guarantee that any statements or opinions provided herein will prove to be correct.
Get fresh insights, breaking news, and hidden gems in the world of crypto—delivered straight to your inbox with our Crypto Cookies newsletter.
Don’t miss out—sign up now and get your first bite of insider knowledge!
