ZachXBT Says $12.6 Million in Zama cUSDC May Have Been Frozen After Circle Blacklisting

A new controversy is making the rounds in crypto after blockchain investigator ZachXBT said Circle may have blacklisted a contract tied to Zama’s confidential USDC, or cUSDC, on Ethereum, freezing around $12.6 million in user funds.

According to ZachXBT, the blacklist action happened roughly seven hours before he shared the update, and it appears to have locked the contract address used for Zama’s privacy-focused stablecoin setup. If accurate, that would mean users suddenly lost access to a very large amount of funds without much warning, which is exactly the kind of thing that tends to set off alarms in the crypto world.

What makes the situation even messier is the fact that the address allegedly froze after recently taking part in an Overnight Finance governance vote about treasury allocation. That detail matters because it suggests the contract wasn’t sitting idle in the background. It was active and apparently involved in another DeFi protocol’s governance process not long before the freeze.

ZachXBT also said some users had already been accusing the Zama team of a rug pull before this latest development. Those claims are still just accusations at this stage, but they have added to the confusion around what the contract was doing, who controlled it, and whether users fully understood the risks involved. In crypto, once people start throwing around the words “rug pull,” the conversation tends to spiral fast, even when the facts are still unclear.

He further pointed to a civil lawsuit involving Overnight Finance, saying one of the plaintiffs is Patagon Management, an entity he described as being known for hostile DAO takeovers and attacks on protocol residual value. ZachXBT suggested the plaintiff may have presented the relationship between the frozen address and the Zama contract in a misleading way to the court.

Major Concern for Industry

That is a serious claim, but at this point it remains part of the public dispute rather than something independently confirmed. Still, it raises an obvious question: was the address blacklisted because of a genuine risk issue, or because someone misunderstood how the contract was connected to the broader protocol?

Another important part of ZachXBT’s claim is that the Zama team may not have received any prior notice before the freeze was carried out. If that is true, it would mean the team was left in the dark while a huge amount of user funds became inaccessible almost instantly. For a privacy protocol, that kind of event is especially sensitive because trust is already fragile in that corner of the market.

The situation also highlights one of the biggest contradictions in crypto. Stablecoins and DeFi are often marketed as open, borderless, and decentralized, but in practice, there are still centralized levers that can change everything in an instant. When a company like Circle has the ability to blacklist a contract, it can protect users in some cases. But it can also freeze funds in ways that many crypto users would never expect.

For now, the full picture is still not clear. It is not obvious exactly how the contract was linked to Zama, what role Overnight Finance played, or whether the legal dispute mentioned by ZachXBT will change how the incident is interpreted.

What is clear, though, is that the reported freeze has triggered another round of debate about control, custody, and how much power stablecoin issuers really have over funds on-chain. If nothing else, the episode is a reminder that in crypto, a single blacklisting event can quickly turn into a much bigger story about trust, governance, and who actually has the final say over user assets.