Wasabi Protocol Suffers $4.5 Million Loss Due to Admin Key Breach

The DeFi sector continues to experience significant losses, with Wasabi Protocol being the latest victim, losing approximately $4.55 million on Thursday after its deployer key was compromised, according to a report by security firm Blockaid. This recent hack follows a string of incidents this month, totaling over $605 million in losses across more than 12 separate incidents. The Wasabi Protocol breach bears a striking resemblance to the Drift Protocol exploit, where attackers utilized a compromised admin key to drain $285 million from the Solana-based perpetuals exchange on April 1. The attack on Wasabi Protocol was carried out through an externally owned account, or EOA, known as wasabideployer.eth, which held the sole ADMIN_ROLE within the protocol's permission system. An EOA is a wallet controlled by a private key, and the individual in possession of the key has complete control over the wallet. Once the attacker gained access to the deployer key, they granted themselves admin privileges without any delay by invoking the grantRole function on the permission contract. The attacker then utilized a helper contract to upgrade Wasabi's perp vaults and Long Pool to malicious implementations, resulting in the draining of the balances, as reported by Blockaid. The exploit took advantage of the Universal Upgradeable Proxy Standard (UUPS), which enables a smart contract to modify its underlying code while retaining the same address. UUPS is widely adopted due to its ability to allow developers to fix bugs without requiring users to migrate. However, a significant drawback is that if an attacker gains control of admin permissions, they can replace the contract's logic with any code they desire, including malicious code designed to steal funds. According to Blockaid, Wasabi Protocol lacked a timelock or multisig to protect the admin role. A timelock imposes a delay between the announcement and execution of an admin action, providing users with time to respond. A multisig, on the other hand, requires multiple signers to approve a change. The absence of these security measures left a single key in control of the entire protocol. Blockaid's exploit detection system identified an ongoing admin-key compromise exploit on Wasabi Protocol across both Ethereum and Base. The Wasabi: Deployer EOA was used to grant the ADMIN_ROLE to an attacker helper contract, which then UUPS-upgraded the perp vaults and LongPool to malicious contracts. 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, as per Blockaid's report. 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 sector this month. In the case of Drift, the 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 that figure. Smaller breaches this month have affected CoW Swap ($1.2 million), Grinex ($13.74 million), Resolv Labs ($23 million), Volo Protocol ($3.5 million), among others. What ties these incidents together is not a new vulnerability, but rather the same post-mortem language about lessons learned, only to be followed by the next exploit before the lessons are implemented. Wasabi Protocol has not yet released a public statement regarding the incident. UPDATE (April 30, 11:34 UTC): General edits have been made throughout, and the Drift Protocol exploit has been moved to the third paragraph.