0x778088817780…7780887e

ConfirmedStablecoins663 vB75 sat/vB3 min decode

Circle Froze $1.1B in USDC Tied to Binance Hot-Wallet Breach

Circle froze about $1.1 billion in USDC tied to Binance’s Oct. 29 hot-wallet breach; Binance cited $6.34 billion in affected assets and $2.85 billion frozen or intercepted.

Circle Freezes $1.1 Billion in USDC Tied to Binance Breach
WitnessCircle Freezes $1.1 Billion in USDC Tied to Binance BreachWorldSpectrum / pixabay

Outputs

  1. Circle froze about $1.1 billion in USDC tied to Binance's Oct. 29 hot-wallet breach, according to its Nov. 5 statement.

  2. Binance valued affected assets at roughly $6.34 billion and frozen or intercepted assets at $2.85 billion on Nov. 3, subject to reconciliation and market-price changes.

  3. Binance said 98% of affected token assets had been replenished as of Oct. 31.

  4. During the incident, an attacker supplied $60 million in USDT to Aave V3 Ethereum Core and borrowed 19,762 WETH, then worth about $44.6 million; Aave froze reserves across its networks.

  5. An April 18 Kelp DAO bridge exploit released 116,500 rsETH, then worth about $292 million; Aave froze 11 markets listing rsETH or wrsETH.

What did Circle freeze?

Circle, the issuer of USD Coin (USDC), froze about $1.1 billion in USDC tied to Binance's Oct. 29 hot-wallet breach, according to the stablecoin issuer's Nov. 5 statement. Circle said in that statement: “The freeze was coordinated with law enforcement.” The source does not identify the agency or provide a court filing.

Binance placed the compromise at about 4:05 p.m. ET (20:05 UTC) on Oct. 29. Its Nov. 3 update valued affected assets at roughly $6.34 billion and put frozen or intercepted assets at $2.85 billion, subject to reconciliation and market-price changes.

Those figures do not describe the same thing. The $6.34 billion represented Binance's valuation of affected assets, while $2.85 billion combined funds already frozen or intercepted. Neither number should be presented as the amount stolen, returned or lost by customers.

The $1.1 billion action was an issuer-level block on affected USDC. It demonstrated the centralized control a stablecoin issuer can exercise during a crypto emergency.

Takeaway: Circle stopped specific USDC from moving, but the final loss is not yet settled.

How much has Binance recovered?

Writing in its Nov. 3 update, Binance said: “98% of affected token assets had been replenished as of Oct. 31.” That language describes the replenishment of affected token assets. It does not establish that 98% of customers recovered funds, that withdrawals were fully restored or that the incident produced no further loss.

Binance's $2.85 billion figure merged two recovery channels: freezing and interception. A frozen asset has not necessarily returned to customers, while an intercepted asset may have been stopped before loss. Market-price changes can also alter the dollar value before the promised reconciliation.

The gap between affected and restored assets deserves more precision than the headline. Binance valued affected assets at $6.34 billion, but the source gives no final accounting showing how replenished assets, frozen balances and intercepted transfers resolve against that exposure.

Takeaway: Binance reported substantial replenishment, not a final legal or accounting resolution.

How did Aave respond?

The source further reports that, during the incident, an attacker supplied $60 million in Tether (USDT) to Aave V3 Ethereum Core and borrowed 19,762 wrapped Ether (WETH), then worth about $44.6 million. Aave froze reserves across its networks.

The Aave intervention operated through decentralized-finance market controls rather than Circle's issuer freeze. For scale, the $1.1 billion USDC block was roughly 25 times the reported $44.6 million WETH borrowing, although the comparison measures different assets and interventions.

The source also describes an April 18 Kelp DAO bridge exploit that released 116,500 rsETH, then worth about $292 million. Aave froze 11 markets listing rsETH or wrsETH.

The available figures do not establish that the Binance breach caused less decentralized-finance fallout. The incidents involved different assets, mechanisms and response measures, so treating the totals as a direct ranking would overstate what the record shows.

Takeaway: Aave used reserve and market freezes; Circle directly blocked affected USDC.

What remains unresolved?

The provided material identifies no court filing, named law-enforcement agency, transaction hash or final loss allocation for the Binance breach. It relies on company statements and Binance's own recovery estimates, leaving legal authority, customer claims and the disposition of frozen funds outside the record.

That limitation matters because issuer intervention changes the immediate mechanics of a breach. Circle could block affected USDC under a freeze coordinated with law enforcement, but the source does not show whether the freeze covered every implicated balance or how long it will last.

The next checkpoint is Binance's reconciliation of the $2.85 billion frozen-or-intercepted figure and any subsequent law-enforcement action arising from the coordinated Circle freeze. The source provides no deadline for either process. Until both are complete, the market-structure lesson remains that issuer intervention can stop specific assets without determining who bears the final loss.

via tokenpost.com (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

733 articles