Circle Faces Class Action Over Handling of $280 Million USDC Drift Exploit

Circle is facing a class action lawsuit alleging it botched its response to a major exploit of the Drift protocol, after plaintiffs say $280 million in stolen USDC remained accessible while the company delayed freezing the funds.

What Went Down With the Drift Exploit

The lawsuit centers on the aftermath of the Drift protocol exploit, in which an attacker allegedly took $280 million in USDC. Plaintiffs argue that Circle had the ability to lock down the stolen stablecoin but did not act quickly enough once the theft occurred.

According to the complaint, USDC differs from decentralized cryptocurrencies because Circle can freeze tokens associated with specific wallet addresses. The lawsuit says Circle has used this capability previously in connection with law enforcement requests and sanctions compliance.

Plaintiffs contend that Circle’s delay left the stolen funds liquid, potentially allowing the exploiter to move, swap, or route the assets through other services. They argue that faster action could have limited the damage.

Circle’s Silence and the Legal Questions Ahead

Circle has not issued a public statement addressing the lawsuit, according to the article. The lack of a response, the complaint’s framing, and the absence of a visible defense strategy raise questions about whether Circle had relevant protocols in place and whether they were followed during the critical period after the exploit.

The lawsuit also points to the role of internal decision-making, including what information Circle had during the delay and what procedures, if any, slowed action. Legal experts cited in the article view the case as potentially influential for how stablecoin issuers handle security breaches, including expectations for response times and decision-making processes.

What the Court Will Likely Examine

The case will move through the class action process, with discovery expected to surface internal communications from Circle during the hours after the Drift exploit. The article notes that discovery could include emails, Slack messages, and meeting notes.

Gibbs Mura, the law firm behind the case, is described as arguing that the evidence will show negligence. Circle, by contrast, is described as likely arguing that it followed reasonable protocols based on the information available at the time.

Potential Impact on Stablecoin Governance

The lawsuit raises broader questions about centralization in crypto and the responsibilities that come with it. Circle’s ability to freeze USDC is described as a key feature that supports institutional and regulatory use of stablecoins, but it also creates the possibility that freezes may be delayed or handled inconsistently during fast-moving incidents.

The article highlights the central issue the lawsuit appears to raise: whether Circle should freeze funds immediately when an exploit occurs, what the threshold for action should be, and who decides.

What Happens Next

No timeline is provided for when the court might rule on substantive issues. The article notes that class actions typically proceed through preliminary motions, discovery, and potentially settlement discussions before any decision is reached. It also suggests Circle could attempt to resolve the matter through settlement or continue to contest the claims.

Overall, the article frames the case as distinct from other exploit stories because it targets the response to the hack rather than only the breach itself.

Frequently Asked Questions

• How much USDC was stolen in the Drift protocol exploit? The lawsuit alleges that $280 million in USDC was stolen.
• Did Circle allegedly fail to freeze the funds promptly? Yes. Plaintiffs allege Circle did not freeze the stolen USDC quickly enough.
• Can Circle actually freeze USDC tokens? Yes. The article states Circle has the technical ability to freeze USDC tied to specific wallet addresses and has done so previously in law enforcement and sanctions-related contexts.
• Who filed the lawsuit against Circle? The class action was filed by Gibbs Mura, representing plaintiffs affected by the alleged delayed response.