Hacker Drains $6.4 Million From a Safe Multisig Using Permissions Its Owners Set
Hacker drains $6.4 million from a Safe multisig through a role permission
An attacker moved about $6.4 million out of a Safe multisig early Monday, according to the security firm PeckShield. A multisig is a shared wallet that normally needs approval from several owners before funds can move. In this case, no owner signed the transfer.
The funds left through Zodiac's Roles Modifier. This is a third-party add-on that lets a Safe's owners give other addresses, called role members, limited power to act for the wallet without owner signatures.
Key points
- About $6.4 million in USDC and a related yield token was drained from a Safe multisig early Monday.
- Zodiac says it found no flaw in its code. It says a role member key, probably compromised, sent a transaction a custom policy allowed but likely never intended.
- Safe says no owner signed the transfer and that its contracts and Safe{Wallet} app were not affected.
- Nobody has publicly identified who controls the wallet.
One transaction moved two tokens
The transaction landed at 6:35 a.m. ET and ran through the Roles module, according to Etherscan, a public blockchain record site. In one step, it withdrew about 4.39 million USDC, a US dollar stablecoin, from a lending vault on the protocol Morpho. It also sent about 1.72 million syrupUSDC to a single address.
SyrupUSDC is Maple Finance's yield-bearing USDC token, so each unit is worth more than a dollar. At the price DefiLlama recorded minutes before the transfer, about $1.19, those tokens were worth roughly $2.05 million. That brings the total to about $6.44 million by Unchained's math, close to PeckShield's figure of $6.45 million.
Part of the stolen funds then went into XMR1, a token traded on the Hyperliquid exchange that takes its name from the privacy coin Monero. PeckShield counted about $813,000 in purchases. Blockchain data firm Bitquery tallied about $1 million across five Hyperliquid accounts.
Zodiac says a role key was likely compromised
Johannes Moormann, a Zodiac co-founder, told Cointelegraph that "there is no vulnerability in the module." He said the transaction "came from the key of a long-standing role member, which was most likely compromised." According to Moormann, the keys and the permissions belonged to the wallet's operators. Cointelegraph reported that Zodiac had not been in contact with them.
Safe said in a statement on X that the incident affected one multisig, that its smart contracts and Safe{Wallet} app were not affected, that the module had been installed outside Safe{Wallet}, and that no owner signed the transfer.
A different situation from a June bug
The situation differs from June, when a bug in Zodiac's Delay and Roles modules let an attacker take about $1.5 million from the wallets of Gnosis Pay users. Gnosis Pay said at the time that it absorbed those losses.
A possible link to the Lighter drain remains unproven
Bitquery found that five wallets funded from the Safe sent money along a route to Hyperliquid similar to the one used after a separate drain at the derivatives exchange Lighter on Monday. Lighter blamed that drain on a trader's leaked API key, a credential used for automated trading. Bitquery found no transfers linking the two incidents and did not name an attacker.
What is confirmed and what is not
Confirmed: the transaction details, the amounts, the tokens, and the timing come from Etherscan and DefiLlama data. PeckShield, Zodiac, and Safe all publicly acknowledged the drain.
Still unclear: nobody has publicly identified who controls the drained wallet. The claim that a role member's key was compromised comes from Zodiac and is described as likely, not proven. Any connection between this drain and the Lighter incident has not been established.
Why this matters for multisig users
The case shows that a Safe wallet can lose funds without any owner signature when its owners grant broad permissions to role members. If a role member's key is stolen, the permissions the owners set decide how much an attacker can take. Both Zodiac and Safe say their own software worked as designed in this case, which puts the focus on how the wallet's operators configured access.