Circle and Tether freeze hacked stablecoins

TLDR

Circle and Tether used their contract controls to freeze a hackers stablecoins tied to the recent Bitget exchange exploit.

1. Circle and Tether blacklisted a Bitget hacker wallet, freezing about $318,000 in USDC and USDT linked to a roughly $350 million to $380 million theft.
2. The move only affected a small slice of the loot, as most stolen funds had already been swapped into ETH and spread across other addresses that issuers cannot freeze.
3. The incident highlights both the safety benefits and the centralization risks of fiat stablecoins, and it is driving fresh debate on freeze policies and exchange security.

Deep Dive

1. What Was Actually Frozen

Circle and Tether froze stablecoins in a wallet labeled Bitget Exploiter 8 after a major Bitget exchange hack that drained around $351.6 million, later revised closer to $387.5 million.

Reports say Circle blacklisted the address at 05:00 UTC using the USDC contracts freeze function, and Tether followed hours later via its multisig, locking roughly 99,990 USDC and 218,023 USDT, around $318,000 in total. This is confirmed by multiple outlets, including a detailed summary of the freeze amounts and timing from Decrypt, which notes the tokens were frozen at the contract level, not at the exchange.

Bitget has said its user protection fund of more than $464 million will cover the losses, and has launched a bounty program offering 5 percent rewards for parties that help freeze or recover related funds, signaling that recovery efforts are still ongoing.

2. Limits Of Stablecoin Freezes

The frozen wallet also held about 170 ETH, and on-chain trackers show other exploiter addresses still control more than 63,000 ETH, which neither Circle nor Tether can touch. Those positions are emphasized in coverage by CoinDesk and Decrypt, which both stress that issuers can only freeze their own tokens, not base-layer assets like ETH.

The attacker moved quickly, swapping large amounts of USDC into ETH and dispersing funds before the issuers acted, which is why only a small fraction of the stolen value was ultimately frozen. This pattern mirrors earlier controversies, such as Aprils Drift exploit, where critics argued Circle reacted too slowly and allowed hundreds of millions of USDC to move before any blacklist was applied.

3. Centralization And User Tradeoffs

Technically, these freezes are possible because USDC and USDT are centrally issued tokens with admin functions that can blacklist addresses and render tokens unspendable. That central control can be a feature when it helps protect exchanges and users from hacks, as shown by the Bitget response.

At the same time, it introduces counterparty and censorship risk: any address that falls under a legal order or policy decision can be frozen, even if it is a self-custodied wallet. Debate around the Bitget hack focuses not only on how fast Circle and Tether reacted, but also on whether their policies should allow proactive freezing or require formal legal orders first.

For users, the practical takeaway is that fiat stablecoins sit somewhere between bank balances and permissionless assets. They carry useful protections, but you rely on an issuer, its banking partners, and its policy choices.

Conclusion

Circle and Tethers freeze of Bitget hack funds shows how centralized stablecoin controls can help limit some damage after an exploit, but also how constrained those tools are once attackers move into ETH and other non-freezable assets. The episode underlines a core tradeoff: stablecoins offer speed and reversibility closer to traditional finance, yet that same control surface introduces policy and censorship risk that users and exchanges need to factor into how they manage balances and counterparty exposure.