Cryptocurrency

Drift

Security

Read

Phantom

<p><strong>Drift exploit admin keys became the central security question after Drift Protocol disclosed a durable-nonce-based attack that let a malicious actor seize Security Council powers during a breach the market had already framed as a more than $200 million hit. For users, the immediate lesson is that governance access and signer controls can fail before any formal code-bug postmortem is available.</strong></p>
<h2 id="what-drift-confirmed-about-the-durable-nonce-attack">What Drift Confirmed About the Durable Nonce Attack</h2>
<h3 id="attack-timeline">Attack timeline</h3>
<p>On <a href="https://x.com/DriftProtocol/status/2039417136729227425" rel="noopener noreferrer nofollow">April 1, 2026</a>, Drift said it was under active attack and suspended deposits and withdrawals while it investigated.</p>
<p>On <a href="https://x.com/DriftProtocol/status/2039564437795836039" rel="noopener noreferrer nofollow">April 2, 2026</a>, the protocol said a malicious actor used a durable-nonce-based attack to gain unauthorized access and quickly take over Security Council administrative powers.</p>
<p>That official sequence is the cleanest confirmed record so far. Drift has described a loss of administrative control, but it has not yet published a full root-cause analysis of every system touched in the breach.</p>
<h3 id="technical-mechanism">Technical mechanism</h3>
<p><a href="https://en.bloomingbit.io/feed/news/109110" rel="noopener noreferrer nofollow">Bloomingbit's summary of Drift's statement</a> said the attack combined delayed execution through durable nonces with stolen multisig approvals, which points readers toward privileged-access abuse rather than a simple contract-bug narrative.</p>
<p>Drift's durable-nonce description and Bloomingbit's summary narrow the conversation to transaction authorization and timing. They do not, on their own, establish a full failure chain for every approval step, which is why this remains an incident update rather than a finished postmortem.</p>
<p>The same official update said Drift was coordinating with security firms, exchanges, bridges, and law enforcement to trace and freeze assets. That matters because the response effort already extends beyond patching code inside one protocol interface.</p>
<h2 id="why-experts-are-focusing-on-admin-keys-not-just-code">Why Experts Are Focusing on Admin Keys, Not Just Code</h2>
<p><a href="https://decrypt.co/363087/solana-drift-protocol-exploited-285-million" rel="noopener noreferrer nofollow">Decrypt reported</a> that Jiang Xuxian said Drift's admin keys were definitely leaked or compromised. That view does not settle the final postmortem, but it fits Drift's own statement that Security Council powers were seized.</p>
<blockquote>
 <p>"The admin keys behind Drift were definitely leaked or compromised."</p>
 <p>Jiang Xuxian, quoted by Decrypt</p>
</blockquote>
<p>Drift's disclosure of seized administrative powers and Jiang Xuxian's quoted comment both shift the security lesson toward privileged controls. Code reviews still matter, but the evidence reviewed here points more directly to signer security, approval paths, and governance access.</p>
<h3 id="why-privileged-controls-can-become-the-real-attack-surface">Why privileged controls can become the real attack surface</h3>
<p>The admin-power takeover described by Drift also helps explain why the fallout quickly expanded into debates over emergency powers and freezes, the same issue running through <a href="https://trustscrypto.com/tommy-shaughnessy-criticizes-circle-over-usdc-freeze-in-drift-exploit/" rel="noopener noreferrer nofollow">Tommy Shaughnessy's criticism of Circle over a USDC freeze in the Drift exploit</a>.</p>
<p>That same official account of compromised control gives the story a policy dimension similar to <a href="https://trustscrypto.com/feds-barr-warns-stablecoin-risks-persist-as-genius-oversight-rules-begin/" rel="noopener noreferrer nofollow">Fed's Barr warning that stablecoin risks persist as GENIUS oversight rules begin</a>, because both cases turn on who holds critical keys, approvals, and intervention rights when crypto systems fail.</p>
<p>For investors, the practical trust question is no longer limited to whether Drift's code had been audited. The official incident update, the expert comment carried by Decrypt, and <a href="https://x.com/phantom/status/2039416046227218523" rel="noopener noreferrer nofollow">Phantom's warning to users</a> all point to a wider operational chain that includes signers, governance permissions, wallet integrations, and crisis-response controls.</p>
<h2 id="how-the-drift-exploit-hit-users">How the Drift Exploit Hit Users</h2>
<h3 id="user-warnings-and-confirmed-losses-are-different-signals">User warnings and confirmed losses are different signals</h3>
<p>Phantom said users trying to access Drift through Phantom would see a required warning while its security team investigated. That turned the breach into a wallet-level risk message, not just a backend incident report.</p>
<p>For retail users, the practical effect of Phantom's warning and Drift's halt on deposits and withdrawals was immediate: access could be interrupted even before the market had a verified final accounting of what was lost.</p>
<p>That is also why an in-product wallet warning matters beyond public relations. When an ecosystem counterparty changes user flow during an active investigation, it signals that the threat is being treated as a broader safety issue rather than a single-app outage.</p>
<p><a href="https://x.com/PeckShieldAlert/status/2039416872722964741" rel="noopener noreferrer nofollow">PeckShield's initial estimate</a>, Phantom's warning, and Drift's admin-control disclosure describe three different kinds of fallout: possible losses, user-risk messaging, and attack mechanics. Treating them as interchangeable figures would overstate what has actually been confirmed.</p>
<h2 id="what-is-still-unconfirmed-about-the-losses-and-recovery">What Is Still Unconfirmed About the Losses and Recovery</h2>
<p>PeckShieldAlert estimated the initial loss at about $285 million, but the post described that number as an initial estimate rather than a final total.</p>
<figure>
 <div class="stat-callout">
  $285 million
 </div>
 <figcaption>
  Initial loss estimate cited during the Drift exploit response.
 </figcaption>
</figure>
<p>The reviewed material did not include a full official postmortem, a block-explorer-based reconciliation, or a reimbursement plan. Readers therefore have a clear description of the attack method, but not a settled ledger of the eventual damage or recovery.</p>
<p>Drift confirmed the method and the admin-power takeover, while PeckShield supplied only an initial estimate. That split is exactly why quick rewrites risk flattening the story into a generic exploit headline.</p>
<h3 id="what-readers-should-watch-for-in-drift-s-next-updates">What readers should watch for in Drift's next updates</h3>
<p>The next important disclosure is a full technical postmortem from Drift that explains how durable nonces, signer approvals, and administrative powers interacted inside the attack path.</p>
<p>A second checkpoint is any public accounting of traced, frozen, or recovered assets. Until those disclosures arrive, the most reliable facts remain Drift's incident timeline, Phantom's user warning, and PeckShield's provisional estimate.</p>
<p>No regulator statement was identified in the reviewed source set, so the story remains centered on incident response rather than enforcement or restitution.</p>
<h2 id="faq-about-the-drift-exploit-and-admin-key-risk">FAQ About the Drift Exploit and Admin-Key Risk</h2>
<h3 id="what-happened-at-drift-protocol">What happened at Drift Protocol?</h3>
<p>Drift said on April 1, 2026 that it was under active attack and suspended deposits and withdrawals. On April 2, 2026, it said the attacker used a durable-nonce-based method to gain unauthorized access and seize Security Council administrative powers.</p>
<h3 id="was-this-confirmed-as-a-normal-smart-contract-code-bug">Was this confirmed as a normal smart-contract code bug?</h3>
<p>No. Drift's own update centered on a takeover of administrative powers, and Bloomingbit's summary of that statement pointed to delayed execution and stolen multisig approvals rather than a published contract-bug root cause.</p>
<h3 id="how-large-do-the-losses-appear-to-be-right-now">How large do the losses appear to be right now?</h3>
<p>The most widely cited figure in the reviewed material is about $285 million, and it should be treated as provisional because the estimate was not presented as final.</p>
<h3 id="what-did-phantom-tell-users">What did Phantom tell users?</h3>
<p>Phantom said people trying to access Drift through the wallet would see a required warning while its security team investigated.</p>
<h3 id="what-is-the-main-security-takeaway-so-far">What is the main security takeaway so far?</h3>
<p>Drift's description of seized Security Council powers and Jiang Xuxian's quoted comment both point toward admin-key and approval-path risk, which is why the current evidence supports auditing privileged controls as closely as contract code.</p>
<p>Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.</p>
<p>Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making any investment decisions.</p><a href="https://trustscrypto.com/?p=4726" rel="noopener noreferrer nofollow">Read original article on trustscrypto.com</a>

Drift Exploit Puts Admin-Key Audits in Focus After Durable Nonce Attack

Table of Contents

TrustsCrypto

Other articles published on Apr 2, 2026

Join our free newsletter for daily crypto updates!