Wasabi Hack

TOTAL LOST $5.5M
Medium Access Control

Summarize with AI

Affected Chain 2026 Incident surface
Recovered - No recovery reported
All-Time Rank #413 By amount stolen
Auditors 1 Prior security audit

Incident Overview

On April 30, 2026, Wasabi Protocol lost $5.5M across Ethereum, Base, Blast, and Berachain when the deployer wallet was compromised and the attacker granted themselves a privileged admin role. The attacker drained funds from EVM deployments while Solana contracts remained unaffected.

The Wasabi Protocol deployer wallet was compromised, giving the attacker access to admin controls. They used this access to grant themselves a privileged role across all EVM chain deployments. With admin permissions, they drained approximately $5.5M in assets from contracts on Ethereum, Base, Blast, and Berachain.

The attack was initially detected at $2.9M but the final tally reached $5.5M as draining continued across all four chains. The funds were distributed to multiple attacker wallets.

Malicious Admin Grant Transaction:

0x11ff84ff…5f1ded

Exploit Transactions:

Ethereum: 0xcd77423f…a70116

Base: 0x10b37160…cb7e40

Blast: 0xaf0f58cb…2850c6

Berachain: 0xf4934fe89ea19a9d5428c64b41319a33804e8158d84c38ad4f6885c270dbf5e

Attacker Wallets:

0xb8Bb8aDD…ca70dB (~$677K)

0x6244117E…3Cf906 (~$1.1M)

Incident Report

Protocol / Project Wasabi
Date of Incident
Attack Technique Access Control
Classification Exchange (DEX)

Protocol Information

Protocol Type Yield
Official Website wasabi.xyz/
Protocol Twitter/X @wasabi_protocol
Team Anonymous
Source Code Unverified

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Wasabi's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Access Control audit checklist and test coverage
Audited by Audit Report 1 — still lost $5.5M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Wasabi, these are the critical security checks that could have prevented this incident (April 2026).

  • Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Security Audit History

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Wasabi

The Wasabi hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial