Circle Faces USDC Freeze Criticism After Drift Exploit
Circle is under scrutiny after criticism over not freezing Drift-linked USDC during the exploit. Here is what happened, why the freeze debate matters, and what it means for DeFi users.
Circle is facing a fresh credibility test after the Drift exploit turned a stablecoin recovery debate into a centralization debate. The direct evidence in the local research shows investigator ZachXBT, not Tommy Shaughnessy, publicly criticizing Circle for failing to stop Drift-linked USDC from moving across chains while the hack unfolded.
The personality-driven framing around Tommy Shaughnessy remains unconfirmed in the local research. The directly accessible post is ZachXBT’s April 2, 2026 statement, which argued that Circle let Drift-linked USDC move via CCTP for hours during the exploit.
What Triggered the Criticism After the Drift Exploit
TLDR Keypoints
- On April 1, 2026, Drift said it was under active attack and halted deposits and withdrawals.
- Decrypt reported that attacker-linked transfers from Drift exceeded $250 million, with estimates as high as $285 million.
- The directly verified criticism came from ZachXBT, while the Tommy Shaughnessy attribution remains unconfirmed in the local research.
- April 1, 2026: Drift disclosed an active attack and suspended deposits and withdrawals.
- Around 11:06 a.m. ET: Decrypt said roughly 41 million JLP, valued at about $155 million, moved from the Drift Vault to attacker address HkGz4K.
- April 2, 2026: ZachXBT wrote that “Circle was asleep while many millions of USDC was swapped via CCTP from Solana to Ethereum for hours…”
Drift’s own statement put the protocol on alert first, but Decrypt’s reporting is what turned the incident into a nine-figure story by saying attacker-linked transfers later topped $250 million and may have reached $285 million.
The wallet trail also became a focal point in ecosystem coverage, including defiliban’s earlier report Drift Protocol Exploit: Reported $270M Sent to HkGz4K, because the criticism of Circle depended on whether exploiter-linked value had enough time to leave Solana before any freeze response arrived.
In that context, ZachXBT wrote that “Circle was asleep while many millions of USDC was swapped via CCTP from Solana to Ethereum for hours…”, turning the argument from exploit damage into a response-speed debate. That distinction matters because the directly verified evidence blames Circle’s inaction, while the Tommy Shaughnessy attribution still lacks a primary-source post or credible secondary confirmation in the local research.
The local research did not directly fetch a full on-chain CCTP trail, so the crosschain movement claim is grounded in ZachXBT’s public post rather than an independently verified explorer tally.
Circle was asleep while many millions of USDC was swapped via CCTP from Solana to Ethereum for hours from the 9 figure Drift hack during US hours.
Value was moved and nothing was done yet again.
Comes days after you froze 16+ business hot wallets incompetently which is still… pic.twitter.com/T0Xwg1HIfO
— ZachXBT (@zachxbt) April 2, 2026
Why Circle’s USDC Freeze Powers Are Under Scrutiny
Critics are focused on Circle because Circle’s USDC Risk Factors say the company can block certain USDC addresses and freeze associated USDC, and may be required to do so under legal order.
Technical capability is documented
Because Circle’s legal terms explicitly describe blacklist and freeze powers, critics argue the company had documented room to act faster than a purely permissionless issuer would during a fast-moving exploit.
USDC market cap at $77.17B shows the scale of the stablecoin whose issuer discretion is being debated.
Discretion is not automatic enforcement
But the same risk disclosure also says nothing in the agreement obligates Circle to track, verify, or determine the provenance of USDC balances for users, which makes intervention discretionary and compliance-driven rather than automatic.
Circle’s USDC documentation describes CCTP as a permissionless onchain utility for moving USDC between supported networks. That matters because critics are not arguing that CCTP itself should ask permission; they are arguing that an issuer with documented freeze powers should decide faster when that permissionless rail is used during a hack.
That timing pressure becomes easier to understand when USDC 24-hour volume of $14.65B is set against an exploit measured in the $250 million-plus range: once stablecoin liquidity disperses across chains, recovery options can narrow quickly.
What the Dispute Means for DeFi Trust and Stablecoin Risk
For DeFi users, the dispute is not only about whether funds were stolen; it is about how much trust to place in an asset that still depends on issuer judgment in crises. The tension comes directly from the data in this story: Circle can freeze USDC, CCTP is permissionless, and the Drift exploit exceeded $250 million.
That is why exploit response speed now sits alongside market structure as a risk variable. Solana-focused readers were already watching spillover behavior in pieces like Drift Protocol Exploit: Reported $270M Sent to HkGz4K and Trader HXiRSK Sells Another 47,401 SOL After $16.04M Buy, because confidence can weaken before a protocol publishes a full post-mortem.
The narrowest defensible conclusion is also the most important one: Circle is under real scrutiny over whether it should have acted faster, but the local research does not verify the headline’s attribution to Tommy Shaughnessy. What it does verify is a documented freeze capability, a permissionless crosschain rail, and a public accusation from ZachXBT that those two facts collided badly during the Drift exploit.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
Defiliban · Oliver Benjamin
Oliver Benjamin
@oliver-benjamin