Loading...

Wasabi Protocol Loses $5.5M in Four-Chain Exploit

Wasabi Protocol Loses $5.5M in Four-Chain Exploit

Wasabi Protocol Loses $5.5M in Four-Chain Exploit

Compromised deployer key enabled a UUPS upgrade that drained perpetual vaults across Ethereum, Base, Blast, and Berachain on April 30, 2026.

Four open vault doors labeled ETH, BASE, BLAST, and BERACHAIN with a broken brass key abandoned on the floor beneath them.

Don't scroll Twitter for crypto news
One email. Five minutes. Everything that matters today

Wasabi Protocol Loses $5.5M in Four-Chain Exploit, April 2026

Wasabi Protocol lost $5.5 million across Ethereum, Base, Blast, and Berachain on April 30, 2026, after an attacker seized admin control through the protocol's deployer wallet. CertiK flagged the breach at 08:30 UTC; the exploit used a UUPS contract upgrade to drain perpetual vaults, with no official response from Wasabi hours later.

Wasabi's $5.5M breach is still developing. Web Snack covers DeFi security incidents as they break – subscribe to get the next update before funds move further.

Wasabi Protocol's April 1 Breach Left the Root Cause Intact

Wasabi Protocol is a DeFi perpetuals platform that lets users trade with leverage through liquidity pools on Ethereum and several Layer 2 networks. On April 1, 2026, the protocol suffered a $4.55 million drain after an attacker compromised its deployer admin key across Ethereum and Base – a breach CoinDesk reported used the same playbook as the Drift Protocol's $285 million exploit.

Despite that incident, Wasabi did not secure the root vulnerability: a single deployer wallet holding admin rights over upgradeable contracts, with no timelock or multisig requirement. The April 30 attack hit a broader surface – Ethereum, Base, Blast, and Berachain – across four chains instead of two.

April 2026 has been a brutal month for DeFi security. The sector lost over $606 million in the first 18 days alone, headlined by the $293 million Kelp DAO exploit and the $285 million Drift Protocol breach. The Wasabi incident pushes April's toll higher.

UUPS Upgrade Attack: How One Admin Key Drained Four Networks

CertiK raised the alarm at 08:30 UTC on April 30, with an initial estimate of approximately $2.9 million in losses. That figure climbed to around $5.5 million as researchers confirmed outflows across all four affected networks.

Using the Wasabi deployer wallet, the attacker granted ADMIN_ROLE to a malicious helper contract. That contract executed a UUPS upgrade of the protocol's perpetual vaults and LongPool, replacing the core smart contract logic with a harmful implementation designed to redirect funds.

UUPS (Universal Upgradeable Proxy Standard) architecture lets a single authorized address swap out a protocol's entire logic layer. When that authority rests on an unprotected deployer key – with no multisig and no timelock – one compromised wallet is enough to drain every connected contract.

What a Repeat Admin Key Exploit Means for Liquidity Providers

Wasabi is the third protocol this month to lose funds to an admin key compromise. Protocols often deploy with a single admin key controlling upgrade logic, then fail to rotate or restrict that access after an initial breach. When the deployer key is the only check on a UUPS proxy, there is no governance buffer between a stolen key and a full protocol drain.

Anyone with funds in Wasabi Protocol faces total loss of those assets. No insurance mechanism has been reported, and the protocol issued no statement in the hours following the breach. Security researchers have publicly advised all users to revoke any approvals granted to Wasabi contracts without waiting for an official response.

April's three largest DeFi hacks – Kelp DAO, Drift, and Wasabi – all trace back to a compromised key or trust relationship at the admin layer, not a flaw in core business logic. That pattern makes access control failures the clearest security story of 2026 so far.

Stolen Funds Moving as Protocol Stays Silent and Investigation Continues

As of April 30, 2026, blockchain security teams are tracking stolen funds across the four affected chains. No on-chain recovery has been reported, and Wasabi Protocol has made no public statement – unusual given that combined losses across the April 1 and April 30 exploits now exceed $10 million.

Users with open positions or deposited liquidity in Wasabi should treat their funds as at risk and revoke all protocol approvals immediately. The protocol's contracts remain deployed on all four chains as investigations continue.

No confirmed timeline exists for any protocol response, recovery attempt, or audit announcement. The incident remains active.

Admin key exploits hit Wasabi Protocol twice this month for a combined $10M+. Subscribe to Web Snack to follow the security incidents reshaping DeFi access control in 2026.

P.S. This article is for informational purposes only and does not constitute investment advice. Always conduct your own research and make independent decisions.

Like this story? There's more tomorrow

Join Web Snack – no fluff, just value