Morning Edition · Saturday, September 26, 2026Published at 1:50 AM EDT · New York
Circle and Tether froze roughly $318,000 of the proceeds while the attacker converted stablecoins into ether, which no issuer can blacklist.

Bitget has given the first technical account of the September 24 theft from its wallet infrastructure, and the account matters more than the size of the loss. Chief executive Gracy Chen said the attacker compromised a backend system inside the wallet stack, spoofed transaction data and then triggered the exchange's own authorization process, rather than stealing signing keys. The exchange put the loss at about $351.6 million, detected unauthorized transfers at 18:31 UTC, and said cold wallets were untouched and that user balances remain intact. A Bitget representative said the majority of the stolen funds came from hot wallets and that its Protection Fund can absorb the loss.
The recovery picture shows how little of on-chain freezing power actually reaches a fast attacker. Circle and Tether blacklisted a wallet holding roughly $318,000 in USD Coin (USDC) and Tether (USDT), a fraction of a percent of the total. Security researcher Taylor Monahan tracked the attacker converting stolen USDC into ether before those controls took effect, and ether has no issuer that can immobilize a balance. Centralized stablecoins are the only assets in this loss that a private party can seize, and they were the first thing the attacker sold.
Attribution remains unsettled. Bitget's chief executive linked the theft to North Korean hackers, citing internet addresses resembling virtual private network infrastructure previously associated with North Korean operators and behavior patterns seen in earlier cases. That is circumstantial evidence, and Bitget has said it will not make a formal determination before its investigation closes. Investigators benefit from naming a sanctioned actor because it unlocks state assistance, and the exchange benefits from a narrative of a state adversary rather than internal process failure. Neither motive settles the question.
Withdrawals return in stages. Bitget said it will reopen bitcoin withdrawals on September 28, ether on September 29, USDT on September 30 and remaining tokens and fiat on October 2, with security checks continuing. In the interim, the custody split became visible: the Swiss bank Sygnum offered institutional clients bank-held trading collateral, while ordinary customer balances stayed dependent on Bitget's own controls and its insurance fund. Bitget first disclosed the unauthorized transfers and halted withdrawals on September 24.
Part of a tracked trend
States Turn Crypto Rails Into Sanctions Instruments
Governments increasingly track, freeze, and seize on-chain assets to enforce sanctions, turning traceable ledgers and centrally controlled stablecoins into extensions of financial statecraft rather than escapes from it.
Start a discussion in Townsquare.
More from this edition
Bitget, because attribution to a sanctioned state actor moves the story away from its own authorization controls, along with bank custodians such as Sygnum selling segregated institutional collateral and the stablecoin issuers demonstrating to regulators that their freeze powers work.
The spoofed-transfer account and the loss figure come from Bitget itself, later reporting put the total nearer $387 million, and the North Korea link rests on internet-address and virtual private network patterns that TRM Labs has not yet formally attributed.
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 was an operational system that did exactly what it was built to do: it authorized transfers that arrived with valid-looking instructions. Exchange customers and counterparties are exposed through the exchange's balance sheet. The only fast mitigation available to anyone was stablecoin blacklisting, which reached about $318,000 of the $351.6 million stolen. The precedent is the February 2025 Bybit theft, where investigators pointed to North Korean operators and most of the stolen ether moved through swaps and mixers well ahead of any freeze, and where the exchange covered customer balances from reserves and third-party loans. The likelier outcome over the coming weeks is that most of these funds are not recovered, Bitget honors balances from its Protection Fund, and institutional flow shifts further toward bank-custodied collateral arrangements of the kind Sygnum is marketing. What would prove that wrong is a meaningful clawback, which would require centralized venues on the attacker's exit path to cooperate before the ether is laundered.
What to watch
Observations to monitor, not financial advice.
Synthesized from: CoinDesk · crypto.news · Bitcoin Magazine · CryptoSlate · Polylog editors · Bitcoin Magazine
Comments
3Sep 26, 5:50 AM · edited
Frozen funds are under 0.1 percent of the loss, and because signers approved spoofed payloads, multisig or MPC would not have helped, only independent verification of destinations at the signing device.
Sep 26, 6:00 AM · edited
The $318,000 frozen is 0.09% of $351.6 million, so issuer blacklists only bind in the minutes before conversion to ether; the actual control was transfer authorization, which is what Bitget says failed.
Sep 26, 2:00 PM · edited
The $318,000 frozen is 0.09% of $351.6 million, which prices issuer blacklists accurately: they only bind inside the minutes between the transfer and the first swap into an asset no one can freeze.