Bitget Halts Withdrawals After $351M Security Incident, Resumes Staged Rollout
Bitget halted all withdrawals following a September 24 security incident involving an estimated $351 million in losses. The exchange began resuming services in stages on September 28, starting with Bitcoin withdrawals, with Ether and stablecoins to follow through October 2.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
The Security Incident and Initial Response
Bitget halted all withdrawals after a security breach on September 24 resulted in approximately $351 million in losses, according to Crypto Briefing. The CEO stated that customer funds remained safe despite the incident, though the exchange did not immediately disclose technical details of the attack or its scope.
Staged Withdrawal Restart
Bitget announced a phased resumption plan beginning September 28, with Bitcoin withdrawals restarting first, followed by Ether and other assets including USDT through October 2, according to Crypto.news. The exchange's technical team identified the underlying vulnerability and implemented fixes before each asset class came back online.
Market and Industry Implications
The incident underscores operational vulnerabilities at centralized exchanges and has the potential to affect user confidence in the sector. The multi-day withdrawal halt forced users to hold positions they may have wanted to liquidate, while the staged restart suggests Bitget prioritized testing security measures for higher-value assets before resuming broader trading services.
Why It Matters
For Traders
Exchanges resuming in stages may create temporary liquidity imbalances as users withdraw; monitor order book depth on other platforms during Bitget's rollout.
For Investors
A $351M breach at a mid-tier exchange raises questions about custody practices across the CEX landscape and could accelerate capital flows toward self-custody or regulated custodians.
For Builders
High-profile exchange breaches reinforce demand for non-custodial trading infrastructure and cross-chain bridges; consider security assumptions in protocol integrations.
This article is for information only and is not financial advice. Read the full disclaimer.
