Cc9f267dcClaimDrift Protocol launched claims for its DFX recovery token on October 1, 2026, issuing one DFX token per USDT of verified user loss across roughly 299.5 million tokensAgreeDisagree
Cc9f267dcClaimAttackers drained Drift Protocol in under 12 minutes by exploiting a code execution vulnerability in developer tooling, using a fake wallet application, and seizing Security Council administrative powersAgreeDisagree
Cc9f267dcClaimThe October 20, 2026 deposits to Tornado Cash from the Drift Protocol exploiter's wallet were made in fixed tranches of 100 Ether and 10 Ether to match mixer pools and obscure the sender's identityAgreeDisagree
Cc9f267dcClaimAccording to Arkham Intelligence data, 71 tracked wallets belonging to the exploiter behind the April 1, 2026 Drift Protocol exploit retain approximately 81,454 Ether, valued between $194 million and $198.58 millionAgreeDisagree
Cc9f267dcClaimOn October 20, 2026, an Ethereum wallet labeled Drift Exploiter 5 deposited 25,700 to 25,710 Ether, valued at $61.5 million to $63.1 million, into Tornado Cash over approximately two hoursAgreeDisagree
Cc9f267dcClaimEarly redemptions from the Drift Protocol DFX recovery pool on October 1, 2026 paid approximately 0.0104 USDT per DFX token, yielding victims roughly one cent on the dollarAgreeDisagree
Cc9f267dcClaimOn July 23 and 24, 2026, an address labeled Drift Exploiter 4, linked to the Drift Protocol exploit, deposited 23,095 Ether, valued at approximately $44.4 million, into Tornado CashAgreeDisagree
Cc9f267dcClaimBeyond Ether, accounts belonging to the exploiter behind the April 1, 2026 Drift Protocol exploit hold roughly $561,600 in stablecoins and alternative crypto tokens including USDT, USDC, Solana, and USDYAgreeDisagree
Cc9f267dcClaimThe April 1, 2026 attack on Drift Protocol followed a six-month social engineering operation where attackers posed as a quantitative trading firm, deposited $1 million, and met contributors at conferencesAgreeDisagree
Cc9f267dcClaimChainalysis reported that on April 1, 2026, the Drift Protocol exploiter moved funds from five initial exploit wallets to a single stopover wallet across 13 transactions before depositing into Tornado CashAgreeDisagree
Cc9f267dcClaimAccording to DeFiLlama's tracker, the April 1, 2026 Drift Protocol breach was the third-largest crypto exploit of 2026, behind the $387.5 million Bitget exploit and $320 million Liquid Network exploitAgreeDisagree
Cc9f267dcClaimThe April 1, 2026 exploit of Drift Protocol resulted in $295.7 million in stolen crypto assets, including $159.3 million in Jupiter Liquidity Provider tokens and $71.4 million in USDCAgreeDisagree
Cc9f267dcClaimEcho Protocol responded to the May 2026 exploit on its Monad deployment by pausing cross-chain activity, updating smart contracts, and burning 955 eBTC traced to the attackerAgreeDisagree
Cc9f267dcClaimHypurrFi announced its operational wind-down on May 15, 2026, with Euler Finance maintaining HypurrFi's contract stack on the Hyperliquid EVMAgreeDisagree
Cc9f267dcClaimEcho Protocol required debt repayment by November 14, 2026, and set November 19, 2026, at 23:59 UTC as the final deadline for repayments, withdrawals, and unstaking before collateral liquidation, creating risks and delaysAgreeDisagree
Cc9f267dcClaimEcho Protocol users can process asset withdrawals, release collateral, exit strategy positions, and process unstaking claims through existing procedures.AgreeDisagree
Cc9f267dcClaimEcho Protocol announced on October 19, 2026, that it is winding down operations after nearly two years.AgreeDisagree
Cc9f267dcClaimThe Aptos-to-B² Bridge used for aBTC redemptions will remain available after Echo Protocol concludes its wind-down.AgreeDisagree
Cc9f267dcClaimOn September 15, 2026, Balancer published a forum proposal authored by former CEO Marcus Hardt to wind down the protocol and return treasury assets to BAL holders.AgreeDisagree
Cc9f267dcClaimUnder TokenLogic's October 15, 2026 proposed entry route, an approved counterparty supplies USAT to Aave V4's Tokenization Spoke to receive waUSAT receipt tokens before swapping them for GHOAgreeDisagree