Safe says contracts unaffected after reported $6.45M wallet theft
A Safe multisignature wallet has reportedly lost $6.45 million in a suspected theft that Zodiac has linked to a likely compromised role-member key and a custom transaction policy, while Safe has said its contracts and wallet interface remain unaffected.
- One multisig was affected, according to Safe, with no owner signing the transaction.
- Zodiac found no contract vulnerability and said a custom policy permitted the transaction.
- PeckShield reported $4.3 million in USDC and $1.7 million in syrupUSDC among the losses.
- The suspected attacker spent roughly $813,000 buying XMR through Hyperliquid, according to PeckShield.
Safe said in a Nov. 16 statement that the transaction passed through a third-party Zodiac Roles module installed outside Safe{Wallet}. Its explanation followed an alert about millions of dollars leaving a wallet using the permission tool.
The company described the role member’s key as likely compromised and said no wallet owner had signed the transaction. Neither its statement nor Zodiac’s accompanying explanation identified the person or organization controlling the affected Safe.
Zodiac links the Safe transaction to a custom policy
Zodiac said it had been informed of a potential theft from a Safe using its Roles Modifier. After reviewing the incident, the team said it found no contract vulnerability.
In its account, a role member submitted a transaction using a key that was probably compromised. The wallet’s custom policy allowed the action, even though the permission was likely never intended to cover it.
Safe separately stated: “Safe smart contracts and Safe{Wallet} are unaffected.” Its response limited the reported impact to one multisig and identified the third-party module as the transaction route.
Both teams pointed to the same Ethereum transaction in their posts. Zodiac invited users to have their policies reviewed, writing: “As always, we’re glad to review policies with you.”
The statements did not explain how the role member’s key may have been obtained or name the particular policy condition that permitted the transfer.
Role permissions allow transactions without fresh owner signatures
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 requiring its owners to approve every action.
The permissions can specify which addresses a role may interact with, which functions it can call and which parameter values are allowed. The system supports limits on how frequently permissions can be used and thresholds for particular transaction parameters.
Zodiac describes treasury management as one use for this arrangement, allowing an organization to delegate defined tasks beyond its owners or signers.
For the affected wallet, Safe’s statement identifies a role-member transaction through the installed module. Zodiac’s explanation places the suspected compromise at the key level, alongside a policy that allowed the transaction to execute.
PeckShield traces part of the proceeds to XMR purchases
Security firm PeckShieldAlert flagged the suspected theft, crediting on-chain analyst Specter with the initial findings. Its estimate included $4.3 million in USDC and $1.7 million in syrupUSDC, a token associated with Maple’s lending products.
Those two rounded amounts total $6 million. The alert did not provide a complete asset-by-asset breakdown explaining the remaining $450,000 in its headline estimate.
PeckShield said the suspected attacker had spent approximately $813,000 buying Monero through Hyperliquid. Its alert included an account screenshot showing an XMR position.
Neither the Safe nor Zodiac statement announced an asset recovery, a freeze of the stolen USDC, or reimbursement of the affected wallet. The posts did not describe any compromise of Maple’s lending contracts or Hyperliquid’s infrastructure.
Earlier Safe module incidents involved separate security failures
In May, a third-party 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; Squid said its core routing contracts were unaffected.
During June’s Gnosis Pay security incident, co-founder Martin Köppelmann urged users to withdraw EURe and GNO and said the problem involved the Zodiac Delay Module. Gnosis asked bridge validators to pause activity and pledged to cover customer losses.
As crypto.news previously reported, Gnosis Pay’s July disclosure traced that $1.5 million exploit to a software flaw dating to October 2023. The company said all affected balances had been restored and that roughly $300,000 remained under recovery efforts at the time of the disclosure.