Bitget Suspends Withdrawals After Hack, Pledges Hourly Updates and Report Within 24 Hours

MakeCryippreferred on

• Bitget suspended cryptocurrency withdrawal functionality at 18:31 UTC on September 24, 2026 while a security review is underway
• Deposits and trading remain fully operational for users during the suspension, according to the exchange’s own notice
• Bitget committed to hourly updates and a comprehensive incident report with root cause analysis within 24 hours of the notice

Bitget published an official withdrawal service update confirming it suspended cryptocurrency withdrawal functionality at 18:31 UTC on September 24, 2026, as part of its response to the roughly $351.6 million security incident affecting portions of its hot and warm wallet infrastructure. The notice lists the reason plainly: “security review in progress.”

Crucially, the suspension is limited in scope. The notice states that “deposits and trading remain fully operational” throughout the pause, meaning users can continue to fund their accounts and execute trades even while they are temporarily unable to move funds off the platform. That distinction separates this incident from a full platform outage, keeping the exchange’s core trading function running while the withdrawal path is locked down as a precaution.

Bitget’s notice frames the suspension as directly tied to completing its internal review rather than an open-ended freeze: “withdrawals will be restored as soon as the security review is complete.” No fixed calendar date accompanies that commitment, leaving the actual restoration timeline contingent on how quickly the exchange’s security team can close out its investigation into the backend compromise CEO Gracy Chen described separately on social media.

In place of a fixed date, Bitget committed to a specific communication cadence: hourly updates for the duration of the incident, plus a comprehensive incident report covering root cause analysis within 24 hours of the notice being published. That pledge puts a concrete outer bound on when users can expect Bitget’s own account of what happened, even if the withdrawal pause itself runs longer.

The notice also directs affected users toward Bitget’s designated support-ticket channel for individual account issues and points to the exchange’s official social channels for the latest updates, underscoring that the company wants users following its own verified channels for developments rather than relying on secondhand reporting while the review continues. Together with CEO Gracy Chen’s separate account of the attack mechanism, the notice gives Bitget users two official channels, a formal support article and the CEO’s own verified account, to follow rather than one, spreading the incident’s disclosure across both the exchange’s institutional voice and its leadership’s personal one. That dual-channel approach has become common practice among exchanges responding to major security incidents, pairing a company’s formal, legally reviewed statement with a more immediate, conversational account from its chief executive.