#DriftProtocolHacked

#Gate广场四月发帖挑战

The $285 Million Heist That Took 10 Seconds to Execute and Eight Days to Plan

The DRIFT token is trading at $0.0407 right now. Down 27.88% in the last 24 hours. Down 40.35% over the last week. Down 75.57% over the last 90 days. SOL is at $81.38, clinging to a modest 2.37% daily bounce that means very little in the context of what happened on April 1, 2026. Because on that day, Drift Protocol — one of the most prominent decentralized derivatives exchanges on Solana, a platform processing billions in trading volume and holding hundreds of millions in user deposits — was drained of somewhere between $270 and $285 million in under 10 seconds. Not by a brute force attack. Not by a code vulnerability in the traditional sense. But by one of the most methodically premeditated exploits in the history of DeFi: a heist that began eight days before a single dollar was stolen, exploited a legitimate Solana feature in a way its designers never anticipated, and was executed with military precision by what blockchain security firm Elliptic assessed was likely a North Korean threat actor. This is the full story of what happened, how it worked, what it means for Solana DeFi, and what every person participating in on-chain protocols needs to understand before putting another dollar into a smart contract they do not fully understand.

The attack represents more than 50% of Drift Protocol's total value locked at the time of the exploit. It ranks as the second-largest exploit in Solana's entire history. By the time Drift's team confirmed the breach publicly and suspended deposits and withdrawals, the funds — JLP tokens, USDC, wrapped Bitcoin, and native SOL — had already been drained from five separate vaults. The stolen assets began moving through multiple wallets almost immediately, with $232 million in USDC transferred through Circle's cross-chain protocol despite public calls to freeze the funds. The remainder was routed through Wormhole and Tornado Cash in an asset-laundering sequence that reflected the same level of planning and coordination that characterized the attack itself. This was not someone stumbling onto a bug at 2am. This was an operation with infrastructure, reconnaissance, prepared fallback wallets, and a laundering pipeline that was ready to execute the moment the vault doors opened.

To understand how the attack worked, you need to understand durable nonces — the specific Solana feature that made the entire exploit possible. In most blockchains, a transaction includes a reference to a recent block hash, which means the transaction expires if not submitted promptly, typically within a few minutes. Solana introduced durable nonces as a convenience feature for situations where a transaction needs to be pre-signed and held for later submission — for example, when a hardware wallet is offline, or when institutional processes require human approval before execution but the actual submission happens later. A durable nonce transaction does not expire. Once signed, it remains valid indefinitely, waiting to be submitted at any future time. This is a legitimate and useful feature. It is also, as the Drift exploit demonstrated in the most expensive possible way, a feature that fundamentally changes the security model of any multisig governance system that does not account for it.

Here is exactly what the attacker did, reconstructed from CoinDesk's forensic analysis and Drift's own statements. Approximately 20 days before the attack, the attacker minted CVT — a completely worthless token they created themselves, with no market value, no utility, and no existing protocol integration. The token was not listed anywhere. It existed solely as a component in the attack infrastructure. Eight days before the hack, the attacker set up fresh supporting infrastructure — new wallets, new transaction pipelines — and began preparing a set of durable nonce transactions that, once signed by the right parties, would give them administrative control over Drift's protocol. The genius of the durable nonce approach is that the attacker needed to convince only two of Drift's five Security Council multisig members to sign what appeared to be routine administrative transactions. The signers reviewed what they believed were standard governance actions. They signed. Their signatures were valid — legitimate, cryptographically correct approvals from authorized members of the security council. But because those signatures were embedded in durable nonce transactions, the attacker now held pre-signed authorizations that would remain valid forever, waiting to be used at a moment of his choosing, in a context completely different from the one in which the signatures were obtained.

Twenty-five seconds before the funds were drained, the attacker submitted the pre-signed durable nonce transactions and gained full administrative control of the protocol. In that same 25-second window, they used that admin access to create a fake collateral market for CVT — the worthless token they had minted 20 days earlier — and disabled Drift's circuit breaker, the safety mechanism specifically designed to prevent large, rapid asset drains. With the circuit breaker disabled and a fake collateral market in place, the attacker then systematically emptied five separate vaults in seconds. The entire execution phase, from admin takeover to vault drainage, took approximately 10 seconds. Eight days of preparation. Ten seconds of execution. $285 million gone.

The forensic implication that most reports have buried but that deserves prominent placement is the question of how two Security Council members came to sign transactions they did not understand. CoinDesk's detailed postmortem framing put it directly: the open question that Drift's forthcoming detailed postmortem will need to answer is how two separate multisig members approved transactions without recognizing what they were approving, and whether any tooling or interface changes could have flagged durable nonce transactions as requiring additional scrutiny. This is the governance failure at the heart of the exploit. The code worked as designed. The cryptography was valid. The attack succeeded because human operators — members of a security council trusted with administrative authority over hundreds of millions in user funds — signed documents that were later used in a context they never intended. That is a social engineering vector as much as a technical one, and it is far harder to patch than a code vulnerability because it requires changing human behavior, improving tooling interfaces, and building institutional processes that can distinguish between routine administrative actions and durable nonce transactions being used as delayed-execution authorization weapons.

The North Korean attribution, while not formally confirmed, adds a layer of geopolitical gravity that positions this attack within a well-documented pattern. Elliptic assessed the attack as likely attributed to North Korean state-sponsored hackers, consistent with a methodology that SecurityWeek described as matching the extreme precision of known Lazarus Group operations: advance infrastructure setup, multi-stage reconnaissance, prepared laundering pipelines, and execution speed that suggests pre-loaded automation rather than manual operation. North Korean hackers were assessed by blockchain security firms to have stolen at least $2 billion in cryptocurrency in 2025 alone, with stolen funds believed to finance the regime's nuclear weapons program and circumvent international sanctions. If the Drift attribution holds, the $285 million figure becomes not just the largest DeFi hack of 2026 but a significant contribution to a state-level funding operation that has direct consequences for international security. That framing — crypto DeFi users inadvertently funding nuclear program development — is an uncomfortable reality that the industry needs to engage with more seriously than the typical post-hack "security lessons learned" discourse allows.

The market consequences were immediate and stark. The DRIFT token hit an all-time low in the days following the attack, as measured by Stocktwits data. The 90-day performance of negative 75.57% captures the compounding effect of a token that was already under pressure from the broader market contraction before the hack added catastrophic reputational damage. The Solana ecosystem impact was real but contained — SOL is down 40.33% over 90 days, reflecting broader market pressure rather than a Drift-specific collapse. DeFi Development Corp., a Nasdaq-listed company with a Solana treasury strategy, was quick to confirm publicly that it had zero exposure to the Drift Protocol exploit, signaling that the DeFi contagion risk was being actively managed at the institutional level. The fact that a publicly listed company felt it necessary to issue that clarification within hours of the hack says everything about how seriously the institutional Solana ecosystem took the potential ripple effects.

The DeFi security model implications go far beyond Drift. The durable nonce vector is not unique to Drift. Any protocol on Solana that uses multisig governance without explicit protections against durable nonce exploitation is potentially vulnerable to the same class of attack. And the broader lesson — that multisig security is only as strong as the understanding, tooling, and processes of the humans operating it — applies across every blockchain ecosystem, not just Solana. Ethereum multisig governance systems, Cosmos validator sets, Polkadot council structures — all of them have the same fundamental dependency on human operators reviewing and understanding what they are signing. The Drift exploit demonstrated that a sophisticated attacker with sufficient patience can find the gap between what a signature authorizes in the moment it is given and what that same signature enables when submitted weeks later in a different context. Closing that gap requires not just technical solutions but institutional processes that treat every governance signature as a high-stakes authorization with long-term consequences — not a routine approval to click through.

For anyone who held funds in Drift Protocol, the immediate practical reality is severe. The protocol confirmed the attack, suspended operations, and is working through what recovery, if any, looks like. History suggests that recovered funds from DeFi exploits are rare, partial, and slow. The attacker's use of Tornado Cash and cross-chain bridges to launder the funds within minutes of the attack demonstrates a deliberate strategy to make tracing and recovery as difficult as possible. Circle's cross-chain protocol transferred $232 million in USDC despite calls to freeze — a reminder that even the most compliance-forward stablecoin infrastructure has limitations when exploited funds move faster than the freeze process can respond.

#DriftProtocolHacked #GateSquare