Withdrawals restart in stages
Bitget says it resumed Bitcoin withdrawals on the Bitcoin and BSC networks at 08:00 UTC on September 28 following unauthorized transfers from its hot and warm wallets on September 24. The exchange’s latest estimate puts the incident at approximately $388 million. Its published timetable schedules other withdrawal services to return later, including ETH on September 29 and USDT on September 30. Those dates are plans, not confirmation of completed restoration.
The explanation remains preliminary
The company says its cold wallets were unaffected and that its investigation has ruled out a private-key compromise. It describes a possible flaw in a third-party security product that enabled high-level credential access and fraudulent withdrawal commands. That account remains preliminary; Bitget says Mandiant and SlowMist are involved in the investigation. The vendor and final root cause have not been established in the account reviewed for this article. These are company statements, not independent findings by Cyber Security Journal.
Availability answers only one question
For financial-services teams assessing a counterparty incident, a working withdrawal button and a completed forensic investigation answer different questions. Our analysis is that an internal incident brief should track service availability, transaction reconciliation and unresolved control questions separately. Combining them into one red-or-green status risks telling decision-makers more than the evidence supports. Any assessment should also identify when the information was checked and whether it came from the operator or an independent investigator.
Use a defined route for customer updates
Support teams should point customers to verified status information and distinguish completed milestones from forecast dates. Account-specific questions belong in authenticated support channels, not public comment threads. Businesses relying on an affected service can document outstanding transactions and escalation contacts without making assumptions about another organization’s solvency or eventual recoveries. The next meaningful update will be evidence about what changed in the controls and what investigators have confirmed—not simply another restoration target.
Sources & further reading
Our practical suggestions are editorial guidance. Verify applicability against current source and vendor instructions.
