Incident Overview

Leading blockchain security firm PeckShield issued an alert on April 30th, indicating a potential major security breach within the Wasabi Protocol. Initial evidence points towards a possible compromise of administrative private keys, which granted an attacker critical control over the protocol's core functions.

Attack Vector and Financial Impact

On-chain data reveals that the exploiter executed a single transaction to illegitimately assign an external address admin privileges within the protocol's smart contract. This unauthorized access led to the subsequent drainage of assets. The incident affected multiple blockchain ecosystems, with confirmed losses across:

  • Ethereum Mainnet: Suffered substantial asset depletion.
  • Base Chain: Recorded unauthorized fund movements.
  • Blast Network: Targeted as part of the multi-chain exploit.
  • Bera Chain: Also identified abnormal transaction activity.

The estimated total loss stands at approximately $5.5 million, though this figure is subject to change as the investigation progresses.

Official Response and User Guidance

The Wasabi Protocol team quickly acknowledged the situation via official social media channels, confirming an ongoing internal investigation. They have issued critical safety recommendations for all users:

  • Immediately cease all interactions with Wasabi Protocol smart contracts.
  • Do not approve any new transaction permissions related to the protocol.
  • Await further official updates and a comprehensive post-mortem report.

The team has committed to providing full transparency regarding the root cause, final loss assessment, and planned security enhancements.

Broader Security Implications

This breach underscores the persistent vulnerabilities in private key management and access control within decentralized protocols. It serves as a critical reminder for both developers and users:

  • For Projects: Implement robust multi-signature schemes, enforce regular key rotation, and utilize hardware security modules for sensitive key storage.
  • For Users: Exercise heightened caution, suspend interactions with affected protocols until safety is confirmed, and monitor alerts from reputable security analysts.

Building a resilient Web3 security landscape requires continuous collaboration among projects, security experts, and the broader community.