\n
![](\"https:\/\/media.crypto.news\/2025\/10\/crypto-news-The-centralization-drift-Web3-risks-losing-its-soul-option01.webp\")
<\/p>\n
\n<\/p>\n
Drift Protocol said its insurance fund was not affected by the recent attack and that users who staked into the fund will be able to withdraw their shares normally once the protocol is brought back online.<\/p>\n
\n Summary<\/span>\n <\/p>\n <\/p>\n Drift said in an official post on X<\/a> that users who staked into the Insurance Fund will be able to withdraw their corresponding shares once the protocol is restored. The protocol added that the fund itself was not affected by the attack because Drift was paused before any losses could be completed through \u201cnormal liquidation or bankruptcy processes.\u201d<\/p>\n That distinction matters because Drift\u2019s own documentation defines the Insurance Fund<\/a> as the first backstop for maintaining exchange solvency in the event of bankruptcies. More detailed staking documentation<\/a> says users can unstake from the fund, although withdrawals are subject to a cooldown period of 13 days.<\/p>\n The update follows one of the biggest Solana DeFi breaches<\/a> of the year. In April, crypto.news reported that the Drift hack<\/a> drained about $285 million through a compromised administrator key in what security researchers described as a social engineering attack rather than a smart contract flaw.<\/p>\n Drift\u2019s explanation is straightforward: the insurance mechanism exists to absorb insolvency created by liquidations and bankruptcies, not to retroactively cover an external exploit that was halted before those internal loss pathways finished playing out. In its latest statement, the team said that because the protocol was paused early enough, the Insurance Fund never became part of the loss cascade tied to the vulnerability.<\/p>\n <\/p>\n That aligns with outside reporting on the incident. Elliptic<\/a> estimated the exploit at $286 million and said Drift suspended<\/a> deposits and withdrawals during the attack, while Chainalysis<\/a> described the breach as a privileged-access compromise that led to roughly $285 million in losses over a matter of minutes.<\/p>\n The protocol had already signaled that the fund was being secured as a precaution. Reporting from Binance<\/a> cited Drift as saying the insurance fund assets were unaffected and were being withdrawn to enhance protection after the exploit.<\/p>\n Drift now says assets from the protocol\u2019s own Insurance Fund will be used to support the system restart and broader user recovery, and that it plans to publish the relevant on-chain addresses so the community can track how the funds are used. That is a notable shift from simply ring-fencing the fund toward actively deploying part of it in the recovery process.<\/p>\n The insurance fund is only one part of Drift\u2019s broader rebuilding effort. In April, multiple outlets reported that the protocol had lined up as much as $147.5 million in support for affected users, including up to $127.5 million from Tether and another $20 million from partners, while later recovery plans pointed to recovery tokens tied to verified losses, as covered by CoinMarketCap<\/a> and RootData<\/a>.<\/p>\n For users, the immediate takeaway is narrower and more important: insurance fund stakes were not wiped out in the exploit, and normal withdrawals are expected to resume after Drift\u2019s recovery process is complete.<\/p>\n <\/p><\/div>\n\n\n
Why the fund was spared<\/h2>\n
Recovery and restart plan<\/h2>\n