Drift Protocol says April 1 exploit followed a months-long social engineering campaign as attorney raises negligence questions
The facts
- Drift Protocol said the April 1 exploit caused losses of about $280 million, with some reports putting the figure closer to $285 million.
- Drift Protocol said the attack was the culmination of a roughly six-month campaign.
- According to Drift Protocol’s update, the attackers first approached contributors around fall 2025 at a major crypto conference while posing as a quantitative trading firm.
- Multiple reports say the operation relied on social engineering and trust-building over time, including repeated in-person or working interactions with Drift contributors.
- Drift Protocol and several reports linked the operation to suspected North Korean or North Korean state-affiliated actors.
- Attorney Ariel Givner said the incident may qualify as civil negligence and argued that standard operational security procedures could have prevented it.
Context
What does Drift Protocol say happened?
Drift Protocol said the exploit was not a quick opportunistic hack but a structured, months-long social engineering campaign. Its account says attackers built relationships with contributors after first contact at a crypto conference, then used malicious software or tools to compromise access before draining funds on April 1 TokenPost,Decrypt,Coingape,Crypto News Flash.
Why are negligence claims being discussed?
Attorney Ariel Givner said Drift may face civil negligence claims because, in her view, the team failed to follow basic security practices, including stronger separation of signing keys and better vetting of outside developers met through conferences Cointelegraph. Another report similarly summarized her argument that Drift failed to take basic steps to protect user funds Cryptopolitan.
Was this caused by a smart-contract bug?
Some coverage says investigators viewed the incident as a human-targeted compromise rather than a traditional code exploit. Reports describe the breach as driven by social engineering and compromised contributors, and one article explicitly said no smart contract bug was identified Decrypt,Cryptopolitan.
The receipts — 16 sources
Wire services (2)
Other coverage (14)
A news briefing built to show both sides.
The day’s biggest stories in one short brief, built to show both sides and the competing values behind the headlines. Free in your inbox.