According to a report from the Spanish-language outlet CriptoNoticias, Circle froze USDC held in a shared smart contract on a privacy platform without prior notice. The report states the move stemmed from illicit funds flowing into the shared contract, which caused legitimate funds tied to it to be frozen as well — a case of “collateral damage.”
One verification issue needs to be addressed up front: as of this writing, public reporting has not disclosed the name of the frozen contract, its contract address, or any on-chain transaction hash. This means readers currently have no way to independently verify on a block explorer “which contract, how much was frozen, or when it happened.” Circle itself has not issued a separate statement on the matter (its general compliance basis can be found on the Circle Transparency page). Until these gaps are filled, the judgments in this article rest on a single Spanish-language source, and readers should calibrate their confidence in the conclusions accordingly.
What this news means for the U-card in your wallet
Let’s answer the question most readers care about first: if your virtual card balance is held directly in USDT, this incident does not directly affect you. What was frozen is USDC (issued by Circle), and it happened at the level of a shared contract on a privacy protocol — not an individual wallet balance. Tether’s USDT and Circle’s USDC run two separate, independent freeze mechanisms and blacklists.
Two scenarios are worth watching, though:
- Cards funded with USDC: products deeply tied to the USDC ecosystem, such as MetaMask Card and Coinbase Card, are more likely to have funding paths that pass through Circle’s compliance checks. If your top-up path has ever routed through a mixer, a privacy protocol, or a shared contract of uncertain origin, there is theoretically a tail risk of being frozen “by association.”
- Privacy-focused advanced users: routing funds through a privacy protocol before topping up a card already places you under an issuer’s high-risk risk-control tags. This incident shows that even if your own funds are legitimate, sharing a contract pool with illicit funds can still get you frozen along with them.
Timeline to watch:
- Within 7 days: whether Circle issues additional official comment, and whether it discloses on-chain information about the frozen contract. Until the address is made public, we don’t recommend treating this report as established fact when sharing it further.
- Within 30 days: whether affected users publicly appeal, and whether Circle’s unfreezing process is transparent.
- Within 90 days: whether this develops into a regulatory or litigation issue — particularly as, under the EU’s MiCAR framework, the boundaries of stablecoin issuers’ freezing power are under scrutiny.
If you’re choosing a primary U-card, you can start with our 2026 Top 5 Virtual Cards comparison to see how strictly different issuers screen the source of funds.
Historical context: this isn’t USDC’s first “guilt by association” episode
Placing this incident on a timeline makes it easier to read:
- August 2022, Tornado Cash sanctions: after the US OFAC sanctioned Tornado Cash, Circle proactively froze roughly $75,000 worth of USDC held in related contract addresses — the first large-scale instance of a stablecoin issuer freezing on-chain assets in compliance with a sanctions list. The mechanism here is highly similar: legitimate funds in a shared contract got swept up along with the rest.
- March 2023, brief USDC de-peg: the collapse of Silicon Valley Bank affected Circle’s reserves, and USDC briefly dropped to around $0.87 before recovering. That was a reserve-side credit risk event, entirely different from this on-chain freeze risk, and the two should not be conflated.
What this incident has in common with the 2022 Tornado Cash case: both are freezes at the USDC shared-contract layer, and both involve legitimate funds getting caught up. The difference is that Tornado Cash had a clear OFAC sanctions order as legal basis and a publicly disclosed contract address; this report has neither a clear regulatory order nor verifiable on-chain evidence. CriptoNoticias’s wording emphasizes “no prior warning,” but whether the trigger was external sanctions, internal risk control, or a law-enforcement request — none of this can currently be substantiated by any citable source. This is an editorial judgment call, pending confirmation.
Regulatory perspective: the legal boundaries of freezing power
USDC’s freeze capability is written into its smart contract, and the issuer holds blacklist-management authority. This itself is not illegal, and is in fact one of the preconditions many jurisdictions rely on to accept stablecoins. The problem lies in the gray zone touched by “no prior warning” and “collateral damage”: there is currently no unified standard for compensation or appeal when a legitimate holder’s funds get frozen because they shared a contract with bad actors.
In the EU, compliance requirements under the MiCAR framework impose clearer rules on stablecoin issuers’ asset management and user protections, and the room for issuers to unilaterally freeze legitimate users’ assets is narrowing. Comparing the categories:
- Clearly permitted: an issuer freezing specific addresses pursuant to a sanctions list or a court order.
- Clearly gray area: freezing without prior warning, legitimate funds caught up via a shared contract, lack of a transparent appeal channel — this incident falls squarely here.
- Not yet explicitly prohibited: there is currently no regulation that explicitly bans issuers from carrying out this kind of “pool-level” freeze.
Milestones worth watching next
- Whether the address and transaction hash of the frozen contract are made public — this is the precondition for judging the incident’s authenticity and scale.
- Whether Circle issues a separate official statement — watch for updates on its Transparency page.
- Whether affected users file public appeals or lawsuits, particularly regarding MiCAR applicability for EU users.
- Whether Tether comments on similar mechanisms for USDT — if market sentiment spreads, the USDT camp may seize the moment to emphasize its differentiation.
Editorial recommendation
Users holding USTD directly funded on a virtual card don’t need to do anything. This incident doesn’t touch your balance — USDT and USDC run two independent freeze systems.
Users who top up with USDC and whose funds have passed through a privacy protocol, mixer, or a shared contract of unclear origin: this is the only group that genuinely needs to be cautious here. Be sure to keep records of your source of funds, and avoid mixing legitimate funds with high-risk contract pools. This isn’t a prediction that “you will be frozen” — it’s a common-sense way to reduce tail risk.
Until verification information becomes available, don’t spread this single-source report as if it were established fact. Once the contract address and on-chain evidence become public, we will update this article.
If you’re re-evaluating an issuer’s fund-screening style, you can compare the compliance notes in our MetaMask Card review and Coinbase Card review before deciding on your primary card’s funding path.