Bitget Hack Revised to $387.5M; Initial $351.6M Undercount Included Zcash/TRON Transfers
Bitget revised theft estimate to $387.5M Friday (updated from initial Article 137 $351.6M). Increase reflected assets taken during original breach, not additional attack. Revision included Zcash + TRON transfers missed in initial accounting. Nearly 103M XRP stolen Thursday divided among five accounts. By Saturday 12:41 UTC, two accounts holding 20M XRP each reduced to ~23 and ~55 tokens (nearly emptied). Third account down to ~5.8M XRP. Validates exchange security breach scope expanding as hacker methodically liquidates + redistributes stolen assets.
$83M XRP Moved; $75M Remains Unfrozen; XRP Ledger Can’t Freeze Native Asset Unlike Stablecoins
Hacker moved ~$83M stolen XRP from three holding wallets by Saturday. Roughly $75M remains in original accounts that cannot be frozen under XRP Ledger’s existing rules. XRP Ledger (Ripple’s blockchain) lets companies freeze tokens they issue on it, but power does not extend to native XRP. Even Ripple has no built-in way to block attacker from spending stolen XRP. Validates architectural constraint: issuer-level freeze controls (USDC/USDT) available but protocol-level freeze unavailable for native XRP. Hacker exploiting this asymmetry to move funds beyond Bitget’s recovery reach. Transfers accelerated overnight: ~70M XRP remained in original accounts Saturday 04:32 UTC, fell to 49M eight hours later.
Circle/Tether Froze $320K Stablecoins; Blacklist Controls on USDC/USDT Prevent Native XRP Fate
Circle and Tether froze ~$320K in USDC/USDT connected to breach (from hacker-controlled wallets). Both companies’ stablecoins contain controls allowing blacklisting of addresses (unlike native XRP). Validates stablecoin architecture advantage: issuer-level controls enable asset seizure. Contrasts to XRP’s protocol-level limitation. Recovery efforts depend on where stolen XRP flows next—exchanges receiving XRP can restrict accounts/prevent withdrawals but can’t freeze coins in attacker’s wallet. Validates stablecoin issuer competence (Circle/Tether) in breach response vs protocol-level vulnerability (XRPL).
XRP Price $1.54 Saturday; Original Haul ~$160M; 4% Daily Loss, 9% Weekly Gain; Sales Impact TBD
XRP traded ~$1.54 Saturday (down 4% over 24 hours, weekly gain ~9%). Original stolen XRP haul worth ~$160M at Saturday price (103M XRP × $1.54). Equivalent to ~4% of XRP’s $4.4B reported daily trading volume. How much hacker’s sale would move price depends on buy orders available when executed. Validates exchange-level liquidity risk: large stolen asset sale could trigger slippage + price impact. Market absorbing ~$160M worth of stolen XRP liquidation threat. Article 136 mentioned Brent oil -1% on Iran deal rumors; similar price pressure possible if XRP hacker initiates large-scale liquidation.
Bitget Withdrawal Resume Schedule; Protection Fund Covers Loss; Customer Balances Unaffected
Bitget confirmed protection fund covers loss, customer balances remain unaffected. Withdrawal resume schedule: Bitcoin Sept 28, Ether Sept 29, USDT Sept 30, other tokens Oct 2. Staggered resumption suggests exchange rebuilding confidence in custodial controls. Validates Article 137 context (User Protection Fund $464M+ covers full loss). Resumption timeline validates exchange operational recovery progression. Customers regain custody of assets starting Bitcoin (largest security focus) through minor tokens (lowest priority).
What Happened
Bitget hack revised $351.6M (Article 137) → $387.5M (Sept 26). Includes Zcash/TRON missed in initial accounting. ~103M XRP stolen Thursday, divided five accounts. By Saturday 12:41 UTC, two accounts (20M each) reduced to ~23, ~55 tokens (nearly emptied). Third account down ~5.8M XRP. Hacker moved ~$83M XRP to new wallets. $75M remains unfrozen in original accounts (XRP Ledger can’t freeze native XRP). Circle/Tether froze $320K USDC/USDT (blacklist controls available on stablecoins). Transfers accelerated overnight (70M→49M remaining). XRP traded $1.54 Saturday (-4% daily, +9% weekly). Original haul ~$160M at Saturday price. Bitget protection fund covers loss. Withdrawal resume: BTC Sept 28, ETH Sept 29, USDT Sept 30, others Oct 2.
Why It Matters
For XRP investors, $83M hacker liquidation threat validates price/slippage risk. For XRPL ecosystem, native asset freeze limitation reveals protocol vulnerability vs stablecoin architecture. For Circle/Tether, freeze controls validation strengthens stablecoin regulatory narrative (issuer competence). For Bitget customers, protection fund + withdrawal schedule validates exchange security response + custody recovery. For exchange industry, Bitget breach validates security infrastructure investment necessity. For Ripple, XRPL freeze limitation highlights competitive disadvantage vs Ethereum/Solana stablecoin protocols. For hacker tracking, $75M unfrozen XRP validates recovery challenge (can’t blacklist native asset on XRPL).
What’s Next
Monitor XRP hacker wallet movements; if liquidates $75M+ XRP, validates price impact. Track XRP price; if declines significantly post-liquidation, validates exchange-level liquidity constraints. Monitor Bitget withdrawal resume; if proceeds on schedule, validates recovery confidence. Watch XRPL protocol updates; if implement native asset freeze controls (reducing future hacker advantage), validates protocol-level security response. Also track Ripple’s security/custody positioning; if emphasizes stablecoin issuance vs native XRP, validates protocol limitation acknowledgment. Monitor Bitget customer sentiment; if exodus occurs post-hack, validates trust damage. Finally, watch Circle/Tether freeze power usage; if blacklist more hacker wallets proactively, validates issuer-level security evolution.
Affected Tickers & Exchanges:
XRP | USDC | USDT | BTC | ETH | ZEC | TRX | Bitget | XRP Ledger | Circle | Tether
Source: CoinDesk
