Morning Edition · Friday, September 25, 2026Published at 9:11 AM EDT · New York
Chief executive Gracy Chen says the signing process approved forged instructions rather than leaking private keys, and the loss would consume about 76% of the exchange's $464 million protection fund.

Bitget lost $351.6 million after attackers compromised a backend wallet system, generated forged transfer instructions and pushed them through the exchange's own authorization and signing process. Chief executive Gracy Chen described the breach in a public account of the incident. Her central claim is that private keys were not stolen. The signing system worked as designed: it approved instructions that appeared valid because the system feeding it data had already been compromised.
The exchange says hot wallets absorbed the losses while cold wallets remained untouched, that it has restored wallet control, and that its User Protection Fund covers the amount, according to statements relayed by market news channels. Deposits and trading continue. Withdrawals remain suspended while engineers rebuild the affected systems, and Chen said restoration could take hours or days rather than weeks, per CNBC's account. CryptoSlate calculates that covering the full estimate from a fund valued near $464 million would leave roughly $112 million, below the floor Bitget has publicly stated for the fund.
Attribution remains unconfirmed. Chen said the exchange identified internet addresses whose virtual private network usage patterns match those associated with a North Korean group, while stressing that the link is not confirmed. Blockchain analysts and Bitcoin Magazine tracked unauthorized transfers across multiple chains before the exchange confirmed the total loss. The North Korea framing benefits Bitget in a specific way: attributing the breach to a state intelligence operation casts the exchange as the target of a national security matter rather than of an internal operational failure, and it also opens the door to law-enforcement and stablecoin-issuer cooperation on freezing the stolen funds.
The mechanism described here has drained the largest sums from exchanges over the past two years. The cryptographic keys held. The infrastructure that tells the keys what to sign did not.
Part of a tracked trend
Losses Move to Components That Worked as Designed
A growing share of DeFi losses will come not from buggy contract code but from components behaving exactly as specified — oracle forwarders, validator signature sets, governance votes and other trusted off-contract inputs — so audits and bug bounties scoped to on-chain code keep missing the failure surface, and protocols will be repeatedly forced to extend review, scope and monitoring to their privileged operational infrastructure.
Start a discussion in Townsquare.
More from this edition
Bitget, whose customers and counterparties are told a state-sponsored intelligence operation defeated its backend rather than an internal control failure, and which gains access to law-enforcement and stablecoin-issuer channels for freezing funds; competing exchanges gain a marketing contrast while Bitget's withdrawals stay frozen.
The $351.6 million figure, the "keys were never stolen" mechanism and the "cold wallets untouched" claim all originate with Bitget and its chief executive, and no independent forensic firm has published a confirming report, while the North Korea link rests on virtual private network address patterns that Bitget itself calls unconfirmed and that Pyongyang's foreign ministry has broadly rejected as fabricated; separately, reporting elsewhere puts the protection fund above $464 million with more than $1 billion in company capital behind it, which weakens the "76% drained" framing.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
The failure surface here is the operational pipeline that constructs withdrawal instructions, not the cryptography that signs them, and the exposed parties are Bitget's customers (whose withdrawals are frozen), the exchange's insurance reserve, and any venue that relies on a similar backend-to-signer trust path. A well-documented precedent is the February 2025 Bybit breach, also attributed by investigators to North Korea-linked operators, where the compromise sat upstream of the signing step and the exchange restored withdrawals quickly while rebuilding reserves from revenue and external loans. The likelier outcome is that Bitget reopens withdrawals within days and replenishes the protection fund out of trading income over the following months, while custody teams across the industry expand security reviews to cover transaction-construction infrastructure that audits of on-chain code never touched. The condition is that the $351.6 million figure holds. Evidence that would prove the read wrong: a materially larger loss estimate, a prolonged withdrawal freeze, or confirmation that cold-wallet keys were also exposed.
What to watch
Observations to monitor, not financial advice.
Synthesized from: CoinDesk · CryptoSlate · Bitcoin Magazine · Polylog editors · CNBC
Comments
0No comments yet.