Coinfomania and The Crypto Basic both cite Lookonchain's XRP figures for the Bitget hack but disagree on whether $157.48M was the total breach or just the XRP portion of a much larger loss.
Coinfomania and The Crypto Basic both cite Lookonchain's XRP figures for the Bitget hack but disagree on whether $157.48M was the total breach or just the XRP portion of a much larger loss.
What all sources agree on
- The hack involved Lookonchain reporting 102.93 million XRP tokens as part of the stolen assets.
- The figure $157.48 million is associated with the XRP portion per Lookonchain's data.
- Other cryptocurrencies beyond XRP were also affected in the breach.
Where the reports disagree
1Whether $157.48M represents the total hack amount or just XRP's value within a larger total
Bitget was hacked with $157.48M in total funds compromised. XRP accounted for $102.93M of the stolen amount.
Bitget disclosed a security breach affecting approximately $351.6 million on September 24, 2026. A subsequent breakdown from Lookonchain identified 102.93 million XRP worth $157.48 million as the largest component of the stolen assets.
What would settle it: Bitget's official incident report or the on-chain Lookonchain/Arkham asset breakdown
2The overall scale of the hack in dollar terms
The recent hack of the Bitget cryptocurrency exchange has drawn attention, revealing a staggering $157.48 million in compromised funds, including $102.93 million worth of XRP.
The itemized total is approximately $5.26 million higher than Bitget's initial $351.6 million estimate.
What would settle it: Bitget's official incident report
What to make of it
Treat the specific XRP figures (102.93 million tokens, $157.48 million value) as consistently reported by both outlets via Lookonchain; do not treat either outlet's characterization of the total hack size as settled until Bitget's promised full incident report is published.
Treat the specific XRP figures (102.93 million tokens, $157.48 million value) as consistently reported by both outlets via Lookonchain; do not treat either outlet's characterization of the total hack size as settled until Bitget's promised full incident report is published.
