News
DeFiGeneral News 2 min

Gnosis Safe Wallet Reportedly Loses $6.45 Million in Suspected Module Exploit

A Gnosis Safe multisignature wallet reportedly lost approximately $6.45 million on November 16 in a suspected exploit involving its Zodiac Roles permission module. Blockchain security firm PeckShield amplified an alert from on-chain analyst Specter, who linked the transfers to permissions already enabled on the wallet.

The reported outflows included approximately $4.3 million in USDC and $1.7 million in syrupUSDC. Those figures total about $6 million, below the headline loss estimate. The available reports do not fully reconcile the difference, leaving the precise breakdown of the suspected theft uncertain.

Funds Move Into Monero

Specter said the attacker subsequently exchanged the assets and converted approximately $1.2 million into Monero through Wagyu. Separately, PeckShield identified roughly $813,000 spent buying XMR on Hyperliquid. The differing figures reflect the reported observations; the available evidence does not establish whether they cover exactly the same transactions.

The conversions add another layer to the investigation because Monero emphasizes transaction privacy. However, the movement of funds alone does not establish how the attacker first gained access. Initial alerts describe suspected abuse of existing module permissions rather than a confirmed explanation of the underlying security failure.

How Wallet Permissions Work

Safe wallets typically require approval from multiple owners before executing transactions. However, optional modules introduce separate authorization rules that can allow certain actions without collecting the usual signatures. Safe’s documentation explains that these extensions support functions such as spending allowances, recurring payments and automated transactions.

Zodiac Roles lets wallet owners assign specific permissions to designated addresses, including limits on contracts, functions and transaction parameters. For example, a treasury manager can receive authority for approved operations without seeking every signer’s approval each time. That flexibility makes the scope of delegated access central to understanding this incident.

The preliminary findings leave several questions unresolved, including whether compromised credentials, permission settings or a software flaw enabled the transfers. They also do not establish a vulnerability across Safe’s core contracts. A fuller technical account would need to explain both the authorization path and the complete loss calculation.