OAK — OnChain Attack Knowledge

Worked example · 2026-04

Wasabi Protocol UUPS Proxy-Upgrade Admin-Key Exploit — Apr 2026 — ~$4.5–5.5M

Loss
reported between $4.55M (CoinDesk) and >$5M (PeckShield, The Block) and ~$5.5M (CertiK); the earlier ~$5.9M figure is not supported. Funds were drained on Ethereum, Base, Berachain and Blast. The attacker compromised the private key of wasabideployer.eth, the sole administrator in Wasabi's PerpManager permission framework, granted ADMIN_ROLE to a malicious contract, and used it to perform UUPS upgrades on protocol contracts. No source seen reports any recovery or negotiation with the attacker; the earlier claim that most funds were recovered is removed. Wasabi asked users not to interact with its contracts; Cyvers reported the proceeds consolidated into ETH and bridged to Ethereum, and BlockSec traced attacker accounts funded through Tornado Cash.
OAK Techniques observed
OAK-T6.005 (Proxy-Upgrade Malicious Switching — the canonical T6.005 anchor for the "admin-key compromise → malicious implementation deployment" chain. The UUPS proxy pattern delegates upgrade authority to a single admin address; compromising that address grants full control over the proxy's implementation, allowing the attacker to replace the protocol's entire smart-contract logic with an attacker-controlled substitute.) OAK-T9.004 (Access-Control Misconfiguration — structurally adjacent at the admin-key layer. The admin key was a single point of failure; the protocol had no timelock on upgrades, no multisig requirement for upgrade authorisation, and no circuit-breaker that could pause the protocol during an unauthorised upgrade event.)
Attribution
pseudonymous attacker; on-chain addresses identified. No recovery has been reported.
Key teaching point
The Wasabi Protocol exploit is the canonical 2026 UUPS proxy-upgrade attack: compromising a single admin key granted the attacker the ability to replace the protocol's entire smart-contract logic with a malicious implementation. The UUPS proxy pattern concentrates upgrade authority in a single address; if that address's key is compromised, the protocol's complete on-chain logic is replaceable in a single transaction. The structural lesson is that UUPS proxy-admin keys are first-class T6.005 targets: they are high-value, single-point-of-compromise surfaces that grant full control over the protocol's smart contracts. Every UUPS proxy deployment without a timelock and a multisig on the admin key is a standing T6.005 vulnerability.
Corrected 2026-10-11
loss restated to $4.55M–~$5.5M (not ~$5.9M), chains named (Ethereum/Base/Berachain/Blast), mechanism clarified (sole-admin EOA key, ADMIN_ROLE grant, zero timelock), and the unsupported claims that most funds were recovered and the treasury covered the rest were removed.

Summary

Wasabi Protocol is a DeFi protocol (the specific functionality — lending, yield aggregation, or derivatives — was not central to the exploit mechanism). The protocol's smart contracts were deployed using the UUPS (Universal Upgradeable Proxy Standard) proxy pattern, which allows the contract's implementation logic to be upgraded by an admin address.

On April 30, 2026, the attacker gained control of the deployer/admin private key (wasabideployer.eth). The exact compromise vector was not publicly disclosed. With the admin key, the attacker:

  1. Granted ADMIN_ROLE to a malicious contract — per Halborn and Blockaid, via the sole admin key.

  2. Upgraded the UUPS contracts (LongPool, ShortPool, Vault and others) with malicious code at the same addresses. The framework supported a timelock, but the delay was set to zero (Sodot, Halborn), and there was no multisig.

  3. Drained funds — WETH, USDC, PEPE, MOG, cbBTC and other assets (Cyvers) — consolidated into ETH and bridged to Ethereum.

Security firms (Blockaid, CertiK, PeckShield, Cyvers, BlockSec) flagged the exploit as it happened. Wasabi said it was investigating and asked users not to interact with its contracts; Virtuals Protocol froze margin deposits powered by Wasabi as a precaution. The sources seen report no recovery, exchange freeze, or negotiation, and no protocol-treasury reimbursement; earlier claims to that effect in this file were unsupported and are removed.

The exploit highlighted the UUPS proxy pattern's admin-key concentration risk: a single private key controlled the protocol's entire upgradeable contract infrastructure. The absence of two standard safeguards — a timelock (forcing upgrades to wait N hours/days before execution, giving the protocol time to detect and block a malicious upgrade) and a multisig (requiring M-of-N signers to authorise an upgrade) — converted a single-key compromise into a full protocol takeover.

Timeline (UTC)

When Event OAK ref
pre-2026-04 Wasabi Protocol deployed using UUPS proxy pattern; admin key held by a single address (no multisig, no timelock) T6.005 + T9.004 (standing vulnerability)
2026-04-30 Attacker compromises UUPS proxy-admin private key; deploys malicious implementation; upgrades proxy; drains ~$4.5–5.5M T6.005 (proxy upgrade exploit)
2026-04-30 Security firms flag the exploit; Wasabi asks users not to interact with its contracts; Virtuals freezes Wasabi-powered margin deposits (incident response)
Continuing UUPS proxy-admin single-key concentration remains a standing T6.005 surface for every protocol deployed without admin multisig + timelock T6.005 (ongoing)

Public references

Discussion

The Wasabi Protocol exploit is the canonical 2026 T6.005 anchor: the UUPS proxy-admin key compromise → malicious implementation deployment → protocol drain chain. The exploit's structure is identical to earlier proxy-upgrade attacks (the pattern recurs across DeFi from at least 2020) but the 2026 datapoint demonstrates that the surface persists despite years of documented incidents — protocols continue to deploy UUPS proxies with single-key admin addresses and no timelock.

The UUPS proxy pattern's upgrade-authority concentration is a design choice, not a bug. The pattern delegates upgrade authority to the proxy's _authorizeUpgrade function, which by default checks msg.sender == admin(). The admin is a single address — typically an EOA or a multisig. If the admin is a single EOA, compromising that one key grants full upgrade authority. The mitigation is straightforward: set the admin to a multisig (requiring M-of-N signers) and route upgrades through a timelock contract (enforcing a delay between upgrade authorisation and execution). These mitigations have been available since the UUPS pattern was introduced, but adoption is uneven across protocols.

No recovery has been reported for Wasabi, so it does not show the exchange-freeze recovery path; the defender lesson here is prevention. The access-control framework supported a timelock but it was set to zero, and one EOA held sole admin authority, so a single stolen key was enough with no window to block the upgrade.

The incident anchors the T6 × 2026 matrix cell and contributes the 2026 datapoint to the T6.005 chronology. Future v0.x expansions should track whether UUPS proxy-admin concentration decreases as the incident record accumulates — a measurable security-maturity metric for the DeFi ecosystem.

Techniques demonstrated (2)