Safe: Contracts Unaffected After $6.45M Multisig Theft
In this article
About $6.45 million left a single Safe multisignature wallet on Nov. 16, 2026, after a transaction that no wallet owner signed, according to a statement from Safe and a separate review by permission-framework developer Zodiac. The loss passed through a third-party Zodiac Roles module installed outside the Safe{Wallet} interface, Crypto.news reported.
Safe said its contracts and wallet interface remained unaffected, and Zodiac stated that it found no contract vulnerability in the Roles Modifier. Neither organisation named the person or entity controlling the affected wallet. The findings were first flagged by on-chain analyst Specter and published by security firm PeckShieldAlert, as reported by Crypto.news.
How a role key bypassed owner signatures
Zodiac’s documentation describes the Roles Modifier as a way for smart accounts to grant individual addresses narrowly defined permissions. Authorised role members can execute transactions without the owners approving every action. Permissions can be scoped by allowed addresses, callable functions, parameter values, usage limits and thresholds, and Zodiac positions the tool for tasks such as treasury management delegated beyond a group of signers.
In this case, Safe’s account limits the blast radius to one multisig, while Zodiac places the failure at the key level paired with a policy condition that authorised the transfer. Neither post explained how the key may have been obtained or identified the specific policy clause that let the transaction through. Zodiac invited users to have their own policies reviewed.
Why it matters
Multisig wallets are marketed to treasuries and DAOs precisely because no single signer can move funds. A delegated role key weakens that assumption, and organisations using permission modules may need to audit which addresses hold roles and what parameters those roles permit. This is not the first time a third-party module sat at the centre of a Safe-related incident: in May, a module exploit affected 86 Safe wallets on Ethereum and Base, and in June, a Gnosis Pay incident involved the Zodiac Delay Module. The pattern is a reminder that crypto held on any platform or contract depends on the permissions layered on top of it. PeckShield also traced part of the proceeds into Monero purchases on Hyperliquid, though neither statement suggested a compromise of Maple’s lending contracts or Hyperliquid’s infrastructure.
What to watch
The open questions are whether the affected USDC is frozen or the wallet is reimbursed, and whether Safe or Zodiac publishes a more detailed post-mortem naming the policy condition. A clearer response to Zodiac’s offer to review user policies would also indicate how many other accounts share the same configuration.
Frequently Asked Questions
Who has to sign a transaction on a Safe multisig normally?
Ordinarily the wallet’s owners must approve transactions, but with Zodiac’s Roles Modifier an authorised role member can execute specific actions without a fresh owner signature each time.
Was the Safe smart contract itself hacked?
No. Both Safe and Zodiac said they found no contract vulnerability; the loss passed through a third-party module and a compromised key, according to their statements.
What assets were reportedly stolen in the $6.45 million theft?
PeckShield reported about $4.3 million in USDC and $1.7 million in syrupUSDC, with roughly $813,000 later spent to buy Monero on Hyperliquid.
Did this affect every Safe wallet?
Safe limited the impact to one multisig and said its smart contracts and the Safe{Wallet} interface were unaffected.
Source: crypto.news





