Drift Protocol, the largest decentralized perpetual futures exchange on Solana, lost approximately $285 million in user assets on April 1 in what is now the biggest DeFi exploit of 2026. The entire drain took roughly 12 minutes. TRM Labs and Elliptic have both assessed the attack as likely perpetrated by threat actors affiliated with the Democratic People’s Republic of Korea (DPRK), based on on-chain staging patterns, laundering methodologies, and network-level indicators consistent with known DPRK tradecraft.
What Happened
The attack combined three distinct techniques into a single kill chain: abuse of Solana’s durable nonce mechanism, fabrication of a fictitious collateral token, and social engineering of Drift’s governance multisig signers.
Phase 1: Staging (March 11–30). On-chain activity shows that preparation began on March 11 with a 10 ETH withdrawal from Tornado Cash. These funds moved hours later—around 09:00 Pyongyang time—and were used to deploy CarbonVote Token (CVT), a completely fabricated asset. The attacker seeded a Raydium liquidity pool with roughly $500 and then wash-traded CVT between controlled wallets to build a fake price history near $1. Over two weeks, on-chain price oracles picked up this artificial price and began treating CVT as legitimate collateral.
Between March 23 and March 30, the attacker created multiple durable nonce accounts on Solana. Durable nonces are a legitimate Solana feature that replaces the normal transaction expiry mechanism (which uses recent blockhashes that expire after about 90 seconds) with a fixed nonce stored in an on-chain account. This keeps a pre-signed transaction valid indefinitely until someone submits it—and critically, the original signer has no way to revoke their approval unless the nonce account is manually advanced.
Phase 2: Governance Hijack. The attacker used social engineering to induce two of Drift’s five-member Security Council multisig signers into pre-signing transactions that appeared to be routine operational actions. These transactions actually carried hidden authorizations for critical admin functions. Because the transactions used durable nonces instead of standard blockhashes, they remained valid for over a week after signing—far beyond the window the signers likely assumed.
Phase 3: Execution (April 1). With pre-signed governance transactions in hand and CVT established as “legitimate” collateral in the oracle, the attacker executed the drain in roughly 12 minutes. They submitted the pre-signed transactions to seize protocol-level control, used the inflated CVT as collateral to borrow against real assets, and drained approximately $285 million in user funds. Most of the stolen funds were bridged to Ethereum within hours.
Technical Impact
The attack exposes fundamental risks in three areas:
Durable nonce safety. Solana’s durable nonces were designed for convenience—offline signing, scheduled transactions, custodial workflows. But they create an asymmetric risk: once a transaction is signed, it cannot be revoked without explicit action on the nonce account. Most governance signers do not monitor nonce account state, creating a window where seemingly expired approvals remain live and exploitable.
Oracle trust assumptions. Drift’s oracles accepted CVT’s manipulated price without sufficient validation of the token’s legitimacy, liquidity depth, or trading history. A few thousand dollars in wash trading was enough to establish a price feed that the protocol treated as backing for hundreds of millions in collateral.
Multisig social engineering. A 2-of-5 multisig provides limited protection when signers can be tricked into pre-approving transactions whose full implications are obscured. The durable nonce mechanism made this worse by decoupling the moment of signing from the moment of execution.
Who Is Affected
Anyone with funds deposited in Drift Protocol vaults or open positions on the platform. Drift has paused all protocol operations. The $285 million figure makes this the second-largest exploit in Solana’s history, behind only the $326 million Wormhole bridge hack in February 2022.
Mitigation and Recommendations
For Solana protocol teams:
- Audit all governance transactions for durable nonce usage. Consider requiring standard blockhash-based expiry for admin-level operations.
- Implement nonce account monitoring. Alert when nonce accounts associated with governance keys are created or when pre-signed transactions remain unsubmitted.
- Add time-locks to critical governance actions. Even with valid signatures, admin operations should enforce a mandatory delay before execution.
For multisig signers:
- Verify the full transaction payload before signing, including whether durable nonces are being used.
- Treat any request to pre-sign transactions for “later execution” as a red flag.
- Implement out-of-band verification for any governance action that touches protocol parameters or admin controls.
For DeFi users:
- Assess counterparty risk. Governance security is only as strong as the operational security of individual signers.
- Monitor protocol governance proposals and multisig activity through on-chain explorers.