Circle is now facing a serious legal challenge — and it all comes down to one question: should it have stepped in sooner?
A new class action lawsuit claims that Circle failed to stop around $230 million in stolen USDC after the Drift Protocol hack.
The argument from investors is pretty direct. They say the stolen funds didn’t disappear instantly. Instead, they were moved across chains over several hours using Circle’s own system. That window, they claim, was enough time for Circle to act — but it didn’t.
Because of that delay, attackers were able to move and reshuffle the money, making it much harder to recover.
The lawsuit also points to something important: Circle has frozen wallets before. Just days before this hack, the company blocked 16 wallets tied to another case. So, according to the plaintiffs, this proves Circle had both the tools and the precedent to intervene.
At the center of this is a bigger debate in crypto.
Circle does have the power to freeze funds at the contract level. But using that power isn’t simple. Acting too quickly — without legal backing — could create legal risks and raise concerns about control and censorship.
So now it becomes a balancing act:
Act fast and risk overstepping, or wait and risk bigger losses.
Meanwhile, the fallout from the hack is still unfolding. Drift Protocol lost over $285 million in the attack, and trust in the platform took a major hit. Since then, the team has started rebuilding — even shifting toward using USDT instead of USDC going forward.
In the end, this case could set a precedent.
If the court sides with investors, it might push stablecoin issuers to act faster in future hacks. If not, it reinforces the idea that these companies aren’t responsible for stopping every bad transaction — even if they technically can.
