Bitget to Resume Withdrawals After Absorbing $387 Million Hack

Bitget said it will resume user withdrawals following a hack that drained an estimated $387 million from the exchange, insisting that customer balances remain untouched. The announcement marks a critical test of whether a centralized exchange can absorb a breach of this size without passing losses on to depositors — and whether users will believe it.

What happened

The breach, which pushed total estimated losses to roughly $387.5 million, ranks among the largest single incidents to hit a major cryptocurrency exchange in recent years. As detailed in earlier reporting on how the Bitget hack losses climbed to $387.5 million, the breach has been linked to North Korean state-sponsored hacking groups, which have repeatedly targeted exchange infrastructure and hot wallets over the past several years. Rather than freezing operations indefinitely or socializing losses across customer accounts, Bitget has opted to reopen withdrawals while stating that user funds were not affected — implying the platform itself, rather than its depositors, is covering the shortfall.

That distinction matters enormously in the history of exchange failures. When Mt. Gox collapsed in 2014 and when FTX imploded in 2022, customers ultimately bore the brunt of missing funds, in some cases waiting years for partial recovery through bankruptcy proceedings. Bitget’s framing — that it will make users whole out of its own resources — follows a different playbook, one that a handful of exchanges have used after smaller breaches to preserve trust and avoid a run on deposits.

Why the hack matters beyond Bitget

A loss of this magnitude does more than dent one company’s balance sheet. It reopens a debate that has trailed centralized exchanges since the earliest days of the industry: how much custodial risk should users accept in exchange for convenience, liquidity, and fiat on-ramps. Every large hack renews scrutiny of hot-wallet architecture, internal controls, and the speed with which exchanges can detect and contain an intrusion before it metastasizes into a nine-figure loss.

The aftermath has also illustrated the limits of blockchain’s traceability as a recovery tool. In a separate development tied to the same incident, investigators tracked the attacker moving $83 million in XRP through the network — a maneuver notable because, unlike some centralized stablecoin issuers, Ripple has no mechanism to freeze XRP in a hacker’s wallet. That stands in contrast to stablecoin issuers, which have shown they can intervene: reporting on the same breach noted that Circle and Tether froze a wallet linked to the Bitget hacker, even if the amount captured was modest relative to total losses. The episode underscores a growing asymmetry in the crypto ecosystem: assets built with centralized issuer controls can sometimes be clawed back, while more decentralized networks offer attackers a cleaner escape route.

For everyday users, the immediate takeaway is that Bitget is asserting solvency and continuity of service. But the broader signal is less comfortable: exchanges remain attractive, high-value targets, and the sophistication of state-linked hacking operations means no platform’s defenses can be assumed airtight. Confidence in centralized platforms is not just a matter of marketing — it rests on whether an exchange can demonstrate, transparently and over time, that it has covered a loss rather than merely announced that it has.

What to watch next

Several threads from this episode deserve continued attention in the weeks ahead:

• Whether Bitget publishes concrete evidence — proof-of-reserves data, audits, or on-chain disclosures — supporting its claim that user balances are fully intact, rather than relying on a statement alone.
• How withdrawal volumes behave once the freeze lifts; a surge of outflows would signal that user trust has been shaken despite the exchange’s reassurances.
• Whether law enforcement or blockchain analytics firms make further progress tracing and freezing the stolen funds, building on the partial success stablecoin issuers have already had with wallet freezes.
• Regulatory response: incidents of this scale often trigger scrutiny of exchange custody practices, echoing the kind of regulatory attention already visible elsewhere in the industry, including scrutiny of stablecoin issuers’ banking relationships and reserve requirements, such as the recently reported Federal Reserve rule requiring rapid disclosure of stablecoin reserve gaps.
• Whether the hack has any measurable effect on broader market sentiment, at a moment when institutional flows into regulated products like Bitcoin ETFs have otherwise been strong.

Ultimately, Bitget’s decision to resume withdrawals while absorbing an estimated $387 million loss is a significant bet on its own balance sheet and reputation. Whether that bet pays off will be measured not in this week’s headlines but in whether users, over the coming months, keep trusting the platform with their funds.

Source: CriptoNoticias

This content is for informational purposes only and does not constitute financial or investment advice.