Circle and Tether have each confirmed large asset freezes associated with the Binance incident. Their statements describe intervention to prevent movement of affected tokens; they do not establish that the same assets have already been returned to the exchange or credited to customers.
What the issuers actually announced
Circle chief executive Jeremy Allaire said the issuer froze more than 800 million USDC in coordination with law enforcement. Tether chief executive Paolo Ardoino reported more than 1.567 billion USDT frozen in connection with the potential hack. These are issuer-attributed figures from their respective announcements, not an independent audit by The Token Press.
The two statements are useful precisely because they identify who says it intervened and which token was involved. They should be read alongside their publication context, rather than mixed with later aggregate estimates as though every number represented a separate pool of money.
First Digital also reports an FDUSD freeze
First Digital CEO Vincent Chok separately told Cointelegraph in a written statement that the issuer had frozen FDUSD linked to the attack and was coordinating with Binance. He did not give a frozen amount in that statement.
How blocklisting works
Circle’s own blocklisting guidance says it can prevent an address from sending or receiving USDC in limited circumstances. It also distinguishes that restriction from reversing a completed transaction, which it says it cannot recall. This describes the general mechanism, not an independent reconstruction of every Binance-related transfer.
Why a freeze and a return are different milestones
A freeze concerns the ability to move an asset. Recovery concerns regaining control or possession. Reimbursement concerns the customer’s balance or entitlement. Reporting one of these milestones does not establish the other two. A headline that treats a frozen amount as already recovered skips an important evidentiary step.
To substantiate a completed recovery, readers would need an attributable update identifying the assets returned, their destination and how the accounting was reconciled. A customer-coverage outcome would require a separate account of how affected balances were handled. These are the questions our reporting will use to evaluate subsequent announcements, not assertions that a specific legal procedure has already occurred.
Why evolving totals need timestamps
Early issuer updates and a later exchange-wide estimate can describe overlapping assets. Adding them together can double-count the same intervention. Different valuation times can also complicate comparisons when amounts are presented in dollars rather than token units. The meaningful comparison is between reconciled snapshots with a clear scope, not an improvised running total assembled from unrelated posts.
The practical distinction for readers
News of a successful intervention is significant, but it should not be treated as a signal that every service has reopened. Read our current Binance incident and service-status report for operational notices. Our fake-support and recovery-scam guide explains how to assess unsolicited messages; an asset-freeze announcement does not authorize a stranger to collect account credentials or recovery phrases.
Updated October 30, 2026, 05:46 UTC to add First Digital's statement. Original issuer statements checked at 05:13 UTC. Developing story; issuer statements and completed recovery remain distinct.