Drift Protocol Hack

TOTAL LOST $280M
Critical #39 All-Time Access Control

Summarize with AI

Affected Chain 2026 Incident surface
Recovered - No recovery reported
All-Time Rank #39 By amount stolen
Protocol Type Dexs Target category

Incident Overview

On April 1, 2026, Drift Protocol on Solana suffered the largest hack of 2026 with over $280M stolen. An attacker spent weeks preparing a sophisticated operation using durable nonce accounts to pre-sign transactions, obtained 2/5 multisig approvals through social engineering, then executed an admin takeover and drained over half the protocol's funds before bridging everything to Ethereum.

This wasn't a smart contract bug or stolen seed phrase. The attacker planned this for weeks. On March 23, they set up four durable nonce accounts. Two were linked to real Drift Security Council multisig members and two to attacker wallets. Durable nonces are a Solana feature that lets you pre-sign transactions and execute them later without expiring.

Over the next week, the attacker tricked 2 out of 5 multisig signers into approving what looked like legitimate transactions. These were actually malicious pre-signed transactions waiting to execute. On April 1, Drift ran a normal test withdrawal from their insurance fund. Just one minute later, the attacker triggered their pre-signed transactions. Within 4 slots, they transferred admin control to themselves and took over the entire protocol.

With admin access, they drained user deposits from borrow/lend positions, vaults, and trading accounts. The haul was massive, over $280M in a dozen different tokens. They moved fast, bridging 129K ETH (about $270.9M) from Solana to Ethereum using Circle's bridge. Another 2.5M USDC got bridged and swapped for more ETH. The DRIFT token crashed 37%. Only assets not deposited in Drift stayed safe, including staked DSOL and the insurance fund which was pulled to safety.

Main Attacker Wallet (Solana): 7RoMqGAcU7S6ESAhPDvB9iSXvASUhuoE8u7dYRxGBew9

Incident Report

Protocol / Project Drift Protocol
Date of Incident
Attack Technique Access Control
Classification Yield Aggregator,Borrowing and Lending

Protocol Information

Protocol Type Dexs
Official Website app.drift.trade/
Protocol Twitter/X @DriftProtocol
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Price at Hack $0.0682
Market Cap at Hack $39.6M
% of Market Cap Stolen 100.00%
Token Categories
Decentralized Finance (DeFi) Derivatives Prediction Markets Perpetuals Solana Ecosystem Binance Alpha Spotlight Governance

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Drift Protocol's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Access Control audit checklist and test coverage

If you're auditing a protocol with similar architecture to Drift Protocol, these are the critical security checks that could have prevented this incident (April 2026).

  • Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Drift Protocol

The Drift Protocol hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial