Circle faces a class action lawsuit alleging it failed to freeze roughly $230 million in stolen USDC routed after the Drift Protocol exploit. Drift plans a $147.5 million recovery effort backed by future revenue. The case questions whether Circle had both the capability and duty to intervene during the transfers.
Circle Internet Group, the issuer of USDC, is facing a class action lawsuit over its alleged failure to stop the movement of stolen funds tied to the Drift Protocol exploit. The suit was filed by Drift investor Joshua McCollum at the US district court in Massachusetts, representing over 100 affected users. The core question is whether Circle had both the ability and the obligation to intervene as the exploit unfolded. The legal action traces back to the April 2026 breach of Drift Protocol, a Solana-based decentralised exchange, where attackers drained roughly $285 million. A significant portion of those funds, estimated at around $230 million, was quickly converted into USDC. From there, the funds were moved across chains, primarily from Solana to Ethereum, using cross-chain infrastructure. These transfers were not instantaneous. They played out over several hours, split into more than 100 transactions. That detail sits at the centre of the lawsuit. Plaintiffs argue that Circle had a clear window to act. According to the claim, the company could have frozen the affected wallets or halted the transfers, limiting the damage. Instead, the funds kept moving until they were fully out of reach. The case accuses Circle of negligence and of indirectly facilitating the loss by failing to act despite having the technical means to do so. I find the argument straightforward: if a stablecoin issuer can freeze assets at the protocol level, there is a reasonable expectation that they should, especially when exploit-related activity is visible on-chain. Drift has separately announced a $147.5 million recovery plan backed by future revenue, aiming to make affected users whole regardless of the lawsuit's outcome. That plan deserves its own scrutiny, but it does not remove the question of what Circle should have done during those critical hours. For Coincex users and anyone holding or transacting in USDC, this case is worth watching closely. The outcome could set a precedent for what responsibilities stablecoin issuers bear when exploited funds pass through their systems. A practical next step: review how Coincex handles USDC inflows and whether internal monitoring can flag large, suspicious transfers before they clear. Is there a contingency in place if a similar incident occurs on a scale relevant to Coincex operations?
How this page was created
This page was derived from source reporting with automated structuring or translation and reviewed for publication by CoinCex.
