0x76329cc27632…76329cc5
Safe Says Contracts Unaffected After $6.45M Multisig Theft Tied to Role Key
A Safe multisig lost $6.45M after a likely compromised role-member key executed a transfer under a custom Zodiac policy; Safe says contracts and Safe{Wallet} remain unaffected.

Outputs
A Safe multisig lost an estimated $6.45 million in a suspected theft disclosed Nov. 16.
PeckShield attributed $4.3 million to USDC and $1.7 million to syrupUSDC.
The suspected attacker spent roughly $813,000 buying Monero through Hyperliquid.
Zodiac found no contract vulnerability; a custom Roles policy allowed the transaction without an owner signature.
In May, a separate module exploit affected 86 Safe wallets with $3M–$3.2M in losses.
A Safe multisignature wallet lost an estimated $6.45 million in a suspected theft that both Safe and Zodiac have traced to a likely compromised role-member key operating under a custom transaction policy — not to a flaw in Safe's contracts, the two teams said in statements dated Nov. 16.
Safe's position is categorical: “Safe smart contracts and Safe{Wallet} are unaffected.” The company limited the reported impact to a single multisig and identified the transaction route as a third-party Zodiac Roles module installed outside the Safe{Wallet} interface. No owner of the wallet signed the transaction, according to Safe.
How the transaction executed without an owner signature
Zodiac, whose Roles Modifier was installed on the affected account, reviewed the incident and said it found no contract vulnerability. In its account, a role member submitted the transaction using a key that was probably compromised. The wallet's custom policy permitted the action, even though the permission likely never intended to cover it.
The architecture explains why. According to Zodiac's documentation, the Roles Modifier lets smart accounts assign customized permissions to individual addresses. Authorized role members can execute transactions on an account's behalf without owners approving every action. Permissions can specify which addresses a role may interact with, which functions it may call and which parameter values are allowed, with limits on frequency and thresholds on transaction parameters.
For treasury management, this lets an organization delegate defined tasks beyond its owners or signers. It also means the security perimeter shrinks to the hygiene of individual keys. Neither Safe's statement nor Zodiac's explanation identified the person or organization controlling the affected wallet, explained how the key may have been obtained, or named the specific policy condition that permitted the transfer.
What does this change for teams using role-based modules?
The core lesson is operational: a permissioning system is only as strong as its narrowest policy and the key security of its role members. Zodiac invited users to act accordingly, writing: “As always, we're glad to review policies with you.” For practitioners running delegated treasury operations on Safe, an external policy audit moves from good practice to an immediate priority.
On-chain trail: USDC, syrupUSDC and a Monero purchase
Security firm PeckShieldAlert flagged the suspected theft, crediting on-chain analyst Specter with the initial findings. Its estimate included:
- $4.3 million in USDC
- $1.7 million in syrupUSDC, a token associated with Maple's lending products
Those rounded amounts total $6 million; the alert did not provide an asset-by-asset breakdown explaining the remaining $450,000 in the $6.45 million headline figure. Both Safe and Zodiac pointed to the same Ethereum transaction in their posts.
PeckShield also reported that the suspected attacker spent approximately $813,000 buying Monero through Hyperliquid, roughly 13% of the estimated haul converted in a single step to a privacy coin whose design resists tracing. The alert included an account screenshot showing an XMR position.
No recovery has been announced. Neither statement disclosed an asset recovery, a freeze of the stolen USDC, or reimbursement of the affected wallet. The posts also did not describe any compromise of Maple's lending contracts or Hyperliquid's infrastructure.
A pattern of module-level failures
The incident fits an established pattern in which Safe's core contracts hold while third-party extensions fail. In May, a module exploit affected 86 Safe wallets on Ethereum and Base, with losses estimated at $3 million to $3.2 million; Blockaid identified the module as SquidRouterModule, and Squid said its core routing contracts were unaffected.
In June, the Gnosis Pay incident involved the Zodiac Delay Module. Co-founder Martin Köppelmann urged users to withdraw EURe and GNO, Gnosis asked bridge validators to pause activity and pledged to cover customer losses. Gnosis Pay's July disclosure traced that $1.5 million exploit to a software flaw dating to October 2023, with all affected balances restored and roughly $300,000 still under recovery at disclosure time.
For Safe-based treasury operators, the practical question now is whether every installed module and role policy still matches its intended scope — before an attacker answers it first.
via crypto.news (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles