Wasabi Protocol Loses $4.5 Million in Suspected Admin Key Breach

The DeFi sector continues to hemorrhage funds, with Wasabi Protocol being the latest casualty, having lost approximately $4.55 million on Thursday following the compromise of its deployer key, as reported by security firm Blockaid on X. This incident marks the latest in a string of over 12 DeFi breaches that have resulted in cumulative losses exceeding $605 million within the past month. The attack bears an uncanny resemblance to the Drift Protocol exploit, which occurred on April 1, where attackers, allegedly linked to North Korea, utilized a compromised admin key to drain $285 million from the Solana-based perpetuals exchange. At the heart of the breach was an externally owned account (EOA) known as wasabideployer.eth, which possessed the sole ADMIN_ROLE within Wasabi's permission system. An EOA is essentially a wallet controlled by a private key, as opposed to a smart contract, with the key holder wielding full control over the wallet. Upon gaining access to the deployer key, the attackers swiftly granted themselves admin privileges without any delay by invoking the grantRole function on the permission contract. Subsequently, a helper contract was deployed to upgrade Wasabi's perp vaults and Long Pool to malicious implementations, thereby draining the balances, according to Blockaid. The exploit leveraged the Universal Upgradeable Proxy Standard (UUPS), a widely adopted standard that enables smart contracts to modify their underlying code without altering their address. While UUPS offers the advantage of allowing developers to rectify bugs without necessitating user migration, it also introduces a significant vulnerability: if an attacker gains control over admin permissions, they can replace the contract's logic with malicious code designed to siphon funds. Notably, Wasabi lacked both a timelock and a multisig security mechanism to safeguard the admin role, as highlighted by Blockaid. A timelock would have enforced a delay between the announcement and execution of admin actions, providing users with a window to respond, while a multisig would have required multiple signers to approve changes. The absence of these security measures meant that a single key held absolute control over the protocol. Blockaid's exploit detection system identified an ongoing admin-key compromise exploit on @wasabi_protocol across Ethereum and Base, where the Wasabi: Deployer EOA was utilized to grant ADMIN_ROLE to an attacker helper contract, which then UUPS-upgraded the perp vaults and LongPool to malicious implementations. The compromised contracts include Wasabi's wWETH, sUSDC, wBITCOIN, wPEPE, and Long Pool vaults on Ethereum, as well as its sUSDC, wWETH, sBTC, sVIRTUAL, sAERO, and sBRETT vaults on Base, according to Blockaid. Users holding Wasabi LP tokens were advised to revoke any active approvals to the vault contracts, as the underlying assets backing those tokens were either drained or remained at risk. A series of exploits has plagued the DeFi space this month. In the case of Drift, attackers exploited a single-key admin setup with no governance timelock, listing a fake token as collateral and raising withdrawal limits to drain real assets in approximately 12 minutes. Three weeks later, on April 19, Kelp DAO lost $292 million when an attacker exploited a single-verifier configuration in the protocol's LayerZero bridge, releasing 116,500 unbacked rsETH that was then used as collateral to borrow real ether (ETH) from Aave. The cumulative DeFi loss total for 2026 has now surpassed $770 million across more than 30 reported incidents, with April alone accounting for the majority of this figure. Smaller breaches this month have hit CoW Swap ($1.2 million), Grinex ($13.74 million), Resolv Labs ($23 million), Volo Protocol ($3.5 million), among others. A common thread among these incidents is not a novel vulnerability but rather the recurrence of familiar post-mortem analyses about lessons learned, only to be followed by the next exploit before these lessons can be implemented. Wasabi has yet to issue a public statement regarding the incident. UPDATE (April 30, 11:34 UTC): General edits throughout. Moves Drift Protocol exploit to third paragraph.