Bitget will restart withdrawals in staged phases beginning September 28, according to a statement the exchange posted on its official X account. The company said the security vulnerability behind a September 24 incident has been identified and remediated, and that independent firms Mandiant and SlowMist are supporting the investigation and validating the fixes.
Withdrawals were paused as a precaution after the incident. Trading and deposits kept running throughout, so the pause was specific to funds leaving the platform rather than a full freeze.
The resumption timeline
Bitget published a dated schedule, all times in UTC:
- September 28, 8:00: BTC on the Bitcoin network
- September 29, 8:00: ETH on Ethereum, BSC, Arbitrum, Base, and Optimism
- September 30, 8:00: USDT on Ethereum, BSC, Solana, and Tron
- October 2, 8:00: other tokens, fiat, and P2P
The company framed the staged approach as a way to bring services back "as quickly and safely as possible" while security checks finish across the withdrawal infrastructure. It said no further unauthorized transfers are possible and that the incident remains contained. Users do not need to take any action before the rollout; withdrawal availability will show up directly in the app as each phase opens.
Bitget's word on user balances and the Protection Fund
The statement is direct on the money question. Bitget said the pause "is not related to the availability of user assets," that account balances remain unaffected, and that its Protection Fund covers the financial impact of the incident. That reserve is the same backstop Bitget has pointed to during past platform-wide events, and it is the reason the exchange can promise a full return to normal withdrawal service rather than a haircut.
The claims here come from Bitget itself. The involvement of Mandiant and SlowMist adds outside validation of the technical remediation, but the phased schedule and the "funds unaffected" language are the vendor's own account. A fuller picture usually arrives with an incident post-mortem, which Bitget has not yet published.
The angle for Bitget cardholders
The Bitget card draws on your Bitget account balance, so anything that gates money moving off the exchange is relevant to how you fund spending. During the pause, balances stayed intact and trading continued, but shifting assets to an external wallet or another rail waited on the schedule above. If you rely on the card and your funding asset sits lower in the queue, note the date: BTC frees up first on September 28, stablecoin balances in USDT on September 30, and the long tail by October 2.
This is also a plain reminder of counterparty exposure. An exchange-funded card means your spendable balance lives with a third party that can pause access when it needs to, however briefly. That trade-off is the structural difference between Bitget and a card that lets you spend from your own wallet, where an exchange-side incident does not touch your funds. Neither model is strictly better; they carry different risks, and an event like this is where the exchange model's dependency shows.
For most users the practical step is simple: wait for the relevant phase, confirm the withdrawal option is live in-app before assuming it, and keep an eye on Bitget's official channels rather than third-party rumor while the rollout completes.
Overview
Bitget says a September 24 security incident is contained and remediated, with Mandiant and SlowMist validating the work. Withdrawals reopen in phases from September 28 (BTC) through October 2 (remaining tokens, fiat, and P2P). The exchange states user balances are unaffected and its Protection Fund covers the financial impact. Trading and deposits were never paused. Cardholders funding from a Bitget balance should track the dated schedule for their asset and treat the episode as a reminder of the counterparty risk that comes with exchange-funded cards.
