What Bitget has confirmed
In its official update, Bitget says it detected the incident on September 24 at 18:31 UTC. The company says that part of its hot and warm wallets were involved, while cold wallets and private keys were not affected.
The exchange attributes the attack to a vulnerability in a third-party security product and says the attack path has been remediated. These are the exchange's own statements. A press release alone cannot independently establish the technical root cause or full impact.
Why BTC withdrawals returned first
Bitget announced a phased timetable: the Bitcoin network was scheduled to open on September 28, followed by Ethereum and related EVM networks, then USDT on several networks. A final stage for other assets, fiat and P2P was scheduled for October 2.
A phased return means availability of a specific asset and network should be checked in the exchange interface before an operation. It does not mean every route is restored immediately, and it does not replace checking a transaction's on-chain status.
Checks for users
When withdrawing Bitcoin, verify the destination address, selected network, fee, minimum amount and withdrawal status in the account. Do not use links from compensation messages and never share confirmation codes with another person.
An exchange statement that balances are unaffected is distinct from proof of reserves. To assess a public claim, check the report date, methodology and whether you can verify your own balance instead of relying only on a service-restoration headline.
