Bitget Reveals Increased Asset Loss in Security Breach Incident
Bitget has provided an update on the recent security breach, revealing that the confirmed amount transferred to attacker-controlled wallets has risen to approximately $387.5 million, up from the initial estimate of $351.6 million. The exchange attributes this increase to the identification of additional assets during transaction tracing, rather than a new wave of unauthorized transfers.
The exchange has stated that its security team has identified the attack path and the method used to bypass existing controls. Bitget has assured users that the underlying vulnerability has been patched, and no further unauthorized transfers are possible. Independent teams from Mandiant and SlowMist are assisting in the investigation.
The revised loss estimate includes assets across multiple networks, such as Ethereum, XRP Ledger, Zcash, and TRON. Bitget has also launched a recovery bounty program, offering rewards to parties whose actions result in funds being frozen or recovered.
Withdrawals on the platform will be restored gradually, with Bitcoin withdrawals set to resume on September 28. Ether withdrawals on various supported networks are expected to follow on September 29, with USDT withdrawals scheduled for September 30. Other tokens, fiat services, and peer-to-peer withdrawals are planned to return by October 2.
This staged approach to restoring withdrawals will serve as a crucial operational test for Bitget following the security breach. The exchange has assured users that customer account balances remain intact and that financial protection measures are in place to cover the impact of the breach.
The focus now shifts to remediation, asset recovery, and ensuring that the exchange can reopen without compromising security. Bitget’s priority is to restore withdrawal access for customers while maintaining a secure platform.
The increased asset loss and the planned timeline for withdrawals highlight the challenges faced by Bitget in the aftermath of the security breach. The exchange is working diligently to address the incident and restore normal operations for its users.
This article was written by the News Desk and edited by Samuel Rae.
