CVE Index中文
L4 · Septic Tank BlewSafe · Zodiac · Ethereum · cryptosafe-zodiac-role-outflow

A Safe multisig lost assets through a permitted Zodiac Roles transaction

A transaction through a Safe’s enabled Zodiac Roles module transferred about 4.39 million USDC and 1.72 million syrupUSDC. Safe and Zodiac point to a role-member key that was likely compromised and a custom policy that permitted the call.

Disclosed
Nov 16, 2026
Updated Nov 17, 2026
Severity
Septic Tank Blew
No CVE: a breach, not a bug
Splash zone
One Ethereum Safe with a third-party Zodiac Roles module and a role-member policy that allowed the action.
Safe · Zodiac · Ethereum · crypto
In the wild
Yes
The transfer is on-chain. Safe and Zodiac describe likely compromise of a role key.

What happened

The Ethereum receipt for 0x6c7cce68b6373dd0e645e6667d46788f49da5a4afc286bc363a2bf34f0a8c9c5 records an ExecutionFromModuleSuccess event from Safe 0x595362a906a0b4e90aee1430b1f80fdde2be80de for module 0x729c87d1b6939c9b2b0858ac25e235e83e5e6410. Transfer logs record 4,387,188.426175 USDC and 1,717,918.961706 syrupUSDC moving from that Safe to 0x2b02c38022fee2f3c805055f49cd8d24a90cb9e1. These are observed token quantities. The receipt establishes the transfer path. It does not establish how the caller’s key was obtained, who controls the addresses, the aggregate dollar loss or any recovery.

Safe says the module was installed outside Safe{Wallet}, no owner signed the transaction and its core contracts and wallet interface were unaffected. Zodiac says the transaction used a role-member key and that the custom policy permitted an action the wallet operator likely did not intend. Zodiac says it found no contract flaw. The key compromise remains a working explanation. A Safe can execute through an enabled module without the signatures used for a normal owner transaction, so owners reviewing similar exposure should check module permissions as well as their signing thresholds.

Bitquery reconstructed a Morpho vault redemption followed by two ParaSwap calls. The Safe had given the ParaSwap spender unlimited allowances for both transferred tokens. The calls passed the assets to a new executor address and returned no proceeds to the Safe. Bitquery observed the Safe change one owner and move its remaining tokens to another Safe. At 06:32 UTC on November 17, its snapshot still showed both token allowances and the enabled Roles module, even though the Safe no longer held the two tokens. Check and revoke outstanding access before depositing back into the original Safe.

Bitquery estimated the transferred tokens were worth about $6.44 million at the prices it used. It traced about $1.89 million to 12 orders for XMR1 on Hyperliquid and observed 1,833 ETH across three linked addresses at the November 17 snapshot. That describes movements and balances at a point in time. Any eventual Monero payout, recovery or link to the separate Lighter incident remains unverified.

Crime-scene timeline

  1. Nov 16, 11:35 UTC

    A transaction through the enabled module transfers assets

    Ethereum logs record a successful module execution and transfers of USDC and syrupUSDC from the Safe.

  2. Nov 16, 2026

    Zodiac and Safe describe the scope and suspected access path

    Zodiac says a custom policy authorized the action and it found no contract vulnerability. Safe says one multisig was affected and no owner signed the transaction.

  3. Nov 17, 2026

    Bitquery documents approvals and follows the proceeds

    Bitquery traced the Morpho redemption and ParaSwap calls. Its November 17 snapshot still showed unlimited ParaSwap allowances for both tokens and an enabled Roles module.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.