The Drift Protocol Exploit Explained: Durable Nonces, Social Engineering, and Recovery

On April 1, 2026, an attacker took control of Drift Protocol’s administrative permissions and drained assets from the Solana-based trading platform. Chainalysis estimated losses at about $285 million. Drift’s April recovery update itemized roughly $295.7 million at its own valuation. These are separate reported estimates; neither should be treated as a precise current dollar value.

The incident is often called a “hack,” but published accounts describe more than a software bug. They point to a combination of social engineering, authorized signatures used out of context, weak administrative safeguards, and collateral rules that the attacker could change after gaining control.


How the attack unfolded

According to Drift’s investigation as summarized by Chainalysis, the operation began months before the withdrawals. People posing as a quantitative trading firm built relationships with Drift contributors and took part in integration discussions. The reporting says signers were induced to approve transactions in advance; it does not establish every alleged device-infection detail as confirmed fact.

Those approvals used Solana durable nonces. Chainalysis’s transaction analysis says the prepared transactions were later used to transfer administrative control. Once in control, the attacker changed protocol settings to accept a low-value token called CarbonVote Token (CVT) as collateral. Chainalysis reports that CVT’s price had been artificially supported and an attacker-controlled price feed reported it to Drift. The attacker then used CVT collateral to withdraw real assets.

Drift’s April report gives a total of about $295.7 million, while Chainalysis estimated about $285 million. Theft estimates can differ with asset prices, valuation times, and reporting methods; a headline dollar figure is not a separate on-chain transfer.


What a durable nonce does—and does not do

A durable nonce is a normal Solana feature for transactions that cannot be submitted immediately. It replaces the short-lived recent blockhash with a stored nonce, allowing a transaction to be signed offline and submitted later. Solana’s documentation says the nonce advances when the transaction is processed, preventing reuse of that nonce transaction.

The feature is not itself a vulnerability or proof that Solana consensus was broken. The security problem was how privileged approvals were obtained, what signers understood they were approving, and the controls that allowed valid signatures to change protocol authority. A signature proves that a key signed a transaction; by itself, it does not prove the signer understood its full effect.


What is known about attribution

Early April coverage described a North Korean connection as preliminary. Drift’s June 3 update later said Mandiant’s independent forensic investigation had conclusively attributed the attack to UNC6862, which Drift described as a North Korean threat group. This is Drift’s public summary of Mandiant’s finding and is more current than the preliminary attribution repeated in older coverage.

Attribution helps explain the operation, but the technical lesson remains: contributor devices, code repositories, wallet applications, transaction review, and administrative permissions are all part of protocol security.


What Drift announced about security and recovery

In its April 16 update, Drift said it was rebuilding the protocol and listed planned relaunch safeguards: independent audits, a community-governed multisig, dedicated signing devices, verification of transaction contents outside the primary signing interface, timelocks and alerts for critical administrative actions, and disabling durable nonces for signers. These were announced plans; that update alone does not prove each measure was later deployed.

Drift’s recovery process has since advanced. On October 1, it announced that DFX claims and redemptions were open. Under the published terms, an eligible user receives one DFX for each USDT of verified loss. DFX is a transferable recovery token, not USDT and not a promise of immediate dollar-for-dollar repayment. Its redemption amount depends on the recovery-pool balance and outstanding DFX supply; the pool is funded over time from protocol revenue and other announced sources. Drift says the claim window closes January 1, 2028. Insurance Fund claims are separate.

Users checking recovery should consult Drift’s official DFX claims and redemptions instructions and verify the wallet and terms there. A token’s market price can differ from its redemption amount, and both can change.


What the incident shows

The Drift exploit was not simply “a Solana bug” or “a careless signer.” It combined a legitimate transaction feature with a compromised approval process and administrative powers that could make high-impact changes quickly. Durable nonces can support offline and multisig workflows, but make careful transaction review and signer controls especially important.

For users, useful questions include who controls protocol upgrades, whether critical actions have meaningful delays, how signers verify transaction contents, and what recovery terms actually promise. Those checks are more useful than treating “audited,” “multisig,” or “decentralized” as guarantees by themselves.


Social Media Sentiment

An April 2026 discussion on r/solana included replies framing the incident as a custody and signer-process failure, alongside concern for affected users and speculation about SOL’s price move. This is one early thread, not a representative survey or evidence about the exploit’s mechanics.

Last updated: 2026-10


Related Terms


Related Articles


See Also


Sources