Safe Wallet Reportedly Loses $6.45M in Transfers Linked to Zodiac Roles Permissions

Daily Feed
Safe Wallet Reportedly Loses $6.45M in Transfers Linked to Zodiac Roles Permissions

A Safe multisignature wallet reportedly lost $6.45 million in transfers linked to permissions already set up through its Zodiac Roles module. The incident is a reminder that wallet security depends not just on who can sign, but on what delegated permissions let them do.

  • Reported loss: $6.45 million, including about $4.3 million in USDC and $1.7 million in syrupUSDC.
  • Suspected mechanism: On-chain analyst Specter linked the transfers to existing Zodiac Roles permissions.
  • Unresolved details: The listed asset values do not add up to the reported total, and reports of Monero conversions give different figures.

What is known about the reported loss?

PeckShield flagged the incident on Nov. 16, citing findings from Specter. The year was not specified in the available reporting. The wallet reportedly lost $6.45 million, including about $4.3 million in USDC and $1.7 million in syrupUSDC, a yield-bearing token associated with Maple Finance’s lending products.

The two asset figures add up to about $6 million. They are estimates, and the reported breakdown does not identify every asset included in the $6.45 million total. The difference is not a separately confirmed loss. The figures simply do not fully match.

Specter linked the transfers to permissions already set up through the wallet’s Zodiac Roles Modifier, a module that lets Safe owners delegate specific transaction capabilities to other addresses. The available information does not identify the wallet’s owner, the address or role involved, or the exact permissions in place.

How Zodiac Roles permissions work

A Safe is a multisignature wallet. Standard transactions generally need approval from multiple authorized owners. The Zodiac Roles Modifier can provide a more limited way to execute transactions, letting a designated address act within set permissions without getting fresh owner signatures for every transaction.

Permissions can limit which contracts an address interacts with, which functions it calls, and which transaction parameters it can use. That can make routine operations more efficient, but it creates another layer of authority that needs protection. The role member’s key and the limits on its permissions matter just as much as the Safe owners’ keys.

The reported transfers point to an existing permission, but the available details do not show how that permission was configured or how the transactions were authorized. Without those details, it is not possible to tell whether the incident involved an overly broad policy, compromised credentials, or another cause. A separate report said the contracts were unaffected.

Different reports describe Monero conversions

PeckShield reported that roughly $813, 000 was spent buying Monero (XMR) on Hyperliquid. Specter separately said about $1.2 million had been converted into XMR through Wagyu. The reports do not explain how the figures relate, so they should not be added together or treated as a complete accounting of the funds.

Monero is designed to hide transaction details, including the sender, recipient, and amount transferred. That can make funds harder to trace once they enter its network, including in cases involving criminal networks tied to Monero. But the reported conversion figures do not show what happened to the XMR afterward or whether anyone successfully laundered the funds.

Other Safe-related incidents involved different modules

Past incidents involving Safe wallets and related modules underline the need to review delegated permissions and smart-contract components. They do not, on their own, show that the incidents shared a flaw.

In October, a FlashLoopAdapter exploit affecting two Safe wallets connected to Aave positions caused estimated losses of $305, 000. In May, a SquidRouterModule exploit affected 86 Safe wallets on Ethereum and Base, with losses of $3 million. Squid said a third party developed the vulnerable module and that it was not part of Squid’s core routing contracts.

A separate Gnosis Pay incident in June involved the Zodiac Delay Module. A later investigation traced the $1.5 million exploit to a software flaw that dated back to October 2023. Gnosis Pay said affected users had been reimbursed. About $300, 000 was still being recovered when the company disclosed the incident in July.

These incidents involved different modules and reported causes. They do not show that every Safe module, or Zodiac Roles specifically, has the same vulnerability.

Key questions about the Safe wallet incident

  • How much was reportedly lost?

    The reported estimate is $6.45 million. The cited USDC and syrupUSDC amounts add up to about $6 million, and the available breakdown does not account for the full estimate.

  • How were the transfers reportedly enabled?

    Specter linked them to permissions configured through the wallet’s Zodiac Roles module. The available information does not identify the specific role, address, or permission settings.

  • Were Safe owners required to sign each transaction?

    Zodiac Roles can let a role member execute transactions within its permissions without fresh owner signatures for each action. The available information does not establish the approval path used in this incident.

  • How much was converted into Monero?

    PeckShield reported about $813, 000 in XMR purchases on Hyperliquid, while Specter separately said approximately $1.2 million was converted through Wagyu. The figures have not been reconciled.

  • Were any funds recovered?

    The available incident reporting does not say whether any funds were recovered.

What Safe users can check

Safe owners and treasury operators should review which modules are installed and what each one can authorize. For every delegated role, check the permitted contracts, functions, and transaction parameters. Confirm who controls the role’s keys, and know how to revoke access if those keys or permissions are no longer trusted. Guidance on how to lower the threshold for routine transactions can help teams assess how permissions affect day-to-day operations.

Where possible, limit permissions and spending to what a role needs for its tasks. Test the revocation process before an emergency. Delegation can reduce operational friction, but it still needs oversight. A multisig is only one part of a wallet’s security model. The permissions attached to it matter, too.

Share this article

Powered by ADBYTES

Advertise smarter.

Adbytes.Media is a transparent advertising network where advertisers reach real audiences and publishers, affiliates & everyday members earn ADBYTES tokens. Join the community and start earning today.

Back to Blog