Skip to content
Latest alertOptimizely Web supply-chain attack served crypto address swapper and card skimmer on 178 sites incl. Ledger
0xCERT
All advisories
High0xCERT-2026-0363·

Safe multisig drained of about $6.45M via Zodiac Roles module after a role member key was likely compromised

A Safe multisig on Ethereum lost about 4.39M USDC and 1.72M syrupUSDC (~$6.45M) on 16 November 2026 through a transaction sent by a likely compromised Zodiac Roles member key that a custom policy permitted. Safe and Zodiac report no contract vulnerability. Teams using Roles modules should review role members and policies.

Vuln-watch · relayed from a public source; see Source & attribution below

Affected chainsEthereumOther / Multi-chain

Summary

On 16 November 2026 a single Safe multisig on Ethereum (0x595362a906a0b4e90aee1430b1f80fdde2be80de, victim) lost about $6.45M, including roughly $4.3M in USDC and $1.7M in syrupUSDC, according to PeckShield citing on-chain investigator Specter. Safe says a role member's key, likely compromised, sent the transaction through a third-party Zodiac Roles module installed outside Safe{Wallet}, and that no Safe owner signed it. Zodiac says it found no contract vulnerability and that a custom policy allowed a transaction it likely never intended to allow. The owner of the Safe has not been publicly identified.

Affected

  • One Safe multisig with a Zodiac Roles Modifier installed outside Safe{Wallet}
  • Safe smart contracts and Safe{Wallet} are unaffected, per Safe
  • No contract vulnerability in Zodiac Roles, per Zodiac; the cause is a likely compromised role member key combined with an overly broad custom permissions policy

Impact

In transaction 0x6c7cce68b6373dd0e645e6667d46788f49da5a4afc286bc363a2bf34f0a8c9c5, USDC withdrawn from a Morpho vault and syrupUSDC left the Safe for a fresh wallet. Bitquery traced the funds through a second wallet and on to five Hyperliquid accounts that received 100-160 ETH each and bought XMR1; PeckShield reports about $813K was used to buy XMR on Hyperliquid. Bitquery notes behavioural similarities with the same-day Lighter incident (same route, token and hour) but found no on-chain transfer linking the two, and attributes the wallets to no one. Links between wallets are money flows and do not by themselves prove control.

Recommended actions

  • Teams using Zodiac Roles (or any module) on a Safe: audit every role member key and every custom policy; scope permissions to explicit recipients and amounts, and remove stale role members.
  • Treat module-held permissions as equivalent to owner signing power when designing key custody.
  • Exchanges, bridges and Hyperliquid integrators: screen the indicators below and flag inbound flows from them.

Source & attribution

This 0xCERT advisory summarises statements by Safe (https://x.com/safe/status/2122379948417581059) and Zodiac (https://x.com/zodiaceco/status/2122360804661940545), the alert by PeckShield crediting Specter (https://x.com/PeckShieldAlert/status/2122340442486571370), and the on-chain trace by Bitquery (https://bitquery.io/investigations/lighter-hack, "second trail"). Indicators are copied from Safe's post and Bitquery's address record; the victim Safe, the role member key and Morpho/token contracts are deliberately excluded. Details may change; refer to the original sources for the authoritative record.

Indicators of compromise

All IOC feeds →
  • address0x0ee230bce32d0e7a6a39dfdac5acf01e0a69d5ef
  • address0x2b02c38022fee2f3c805055f49cd8d24a90cb9e1
  • address0x44390eba944bd97bf0db86de012a65feac84166a
  • address0x67e0baaf638513c411e25bd39b1d2e3591db0668
  • address0x6c0d3fd53fd1013a32bc1af72ec3b432a66629b2
  • address0x836ccd122d1b50c49ad3aef13ee053f247ad6649
  • address0xe804fc0c7756977e0c512b7a1c392693f4f36198
  • tx0x6c7cce68b6373dd0e645e6667d46788f49da5a4afc286bc363a2bf34f0a8c9c5

OpenPGP-signed. The signed text of this advisory verifies against the 0xCERT key CCC7 D9EC 9415 723D.

Published 2026-11-16 · last updated 2026-11-17

curl -s https://www.0xcert.com/pgp.asc | gpg --import && curl -s https://www.0xcert.com/advisory/0xCERT-2026-0363/signed.txt | gpg --verify