Bitget kept external XRP withdrawals disabled on Sept. 26, and the exchange’s published timetable places XRP in the final phase of its post-breach withdrawal reopening on Oct. 2 at 08:00 UTC, according to its public status and timetable. Bitquery said 27.63 million XRP had moved onward from two tracked attacker accounts by 02:54 UTC on Sept. 26, while 75.35 million XRP remained in six tracked accounts.
Bitget XRP withdrawals disabled on Sept. 26; Oct. 2 reopening phase set
Bitget kept external XRP withdrawals disabled on Sept. 26, and the exchange’s published timetable places XRP in the final phase of its post-breach withdrawal reopening on Oct. 2 at 08:00 UTC, according to its public status and timetable. Bitquery said 27.63 million XRP had moved onward from two tracked attacker accounts by 02:54 UTC on Sept. 26, while 75.35 million XRP remained in six tracked accounts.
Bitget’s timetable lists BTC on the Bitcoin network on Sept. 28 at 08:00 UTC, ETH on Sept. 29 across the networks named in its notice, and USDT on Sept. 30. The Oct. 2 phase covers other tokens, fiat and peer-to-peer services, the exchange said. XRP is not listed separately, placing it in that final group by exclusion. Each date is a planned start, and Bitget says actual withdrawal availability will appear on its platform.
The exchange said it identified and remedied the vulnerability involved in the Sept. 24 incident and was carrying out further checks of its withdrawal infrastructure. It described the pause as a security measure, said user balances were unaffected, and said trading and deposits continue. Its public XRP status on Sept. 26 showed the XRP network open for deposits while external withdrawals were off at 12:11 UTC.
Bitquery’s transaction-backed investigation put the XRP taken from Bitget at about 102.98 million tokens. The Sept. 26 snapshot showed 27.63 million XRP had moved onward from two of six attacker accounts it tracked, while 75.35 million XRP remained across those six accounts at 02:54 UTC. The analytics firm followed outgoing XRP through new accounts toward THORChain, a cross-chain swap network, and said most of the XRP flow it could follow was being swapped toward Bitcoin. It said the description applies to the route it traced, not necessarily to the full 27.63 million XRP that moved onward, and that it cannot identify the owners of the final Bitcoin wallets.
Those transactions show a path from stolen XRP toward another asset, but do not establish the net XRP sold in a centralized exchange order book or the price of any such sale, according to the source. Bitget’s Sept. 25 incident update revised its estimate of the total value transferred to attacker-controlled addresses to about $387.5 million, up from $351.6 million. The company said the higher figure reflected additional Zcash and TRON assets in its accounting rather than further unauthorized transfers. CryptoSlate’s XRP market data displayed XRP near $1.55 when checked on Sept. 26 and listed a Bitget XRP/USDT market; the source says the snapshot contains no bid-ask spread and cannot attribute an XRP price change to the breach.
- The source does not state whether XRP withdrawals actually reopened on Oct. 2 or what Bitget’s platform status will show then.
- The source does not identify the attackers or the owners of the final Bitcoin wallets.
- The source does not measure any breach-linked XRP sold into a spot market or any price effect from the breach.
- The source does not state how many customers were affected or individual loss amounts.
- The source does not reconcile Bitget’s approximately $387.5 million total loss figure with Bitquery’s approximately 102.98 million XRP token count beyond describing them as separate measures.
- The source does not state which networks are covered in Bitget’s Sept. 29 ETH withdrawal phase.
Read the original at CryptoSlate