A Safe wallet transferred about $6.45 million in crypto assets on Monday, with the transaction approved under the wallet’s existing permissions. Zodiac co-founder Johannes Moormann said the available evidence points to a possible compromise of a long-standing role member’s key, rather than a vulnerability in the smart contract. The wallet’s owner has not been identified, and the circumstances remain under investigation.
Transfer moved USDC and syrupUSDC in one transaction
Ethereum records show the wallet sent about 4.39 million USDC and 1.72 million syrupUSDC in a single transaction. Blockchain security firm PeckShield, citing on-chain investigator Specter, said the transfer appeared to involve stolen funds.
Moormann said Zodiac’s team reviewed the transaction and confirmed it was executed through the Zodiac Roles Modifier. The module checks transactions against configured permission policies. This transfer met the wallet’s rules at the time and was therefore approved. It used a key belonging to a long-standing role member, which Moormann said may have been compromised.
He added that the wallet’s custom permissions policy allowed the transfer, almost certainly contrary to the operator’s intentions. However, wallet keys and permissions are controlled by the wallet operator. Zodiac cannot access those settings and did not configure this wallet. Moormann said the information available so far does not indicate a flaw in the Zodiac module, or suggest that other wallets using it are affected.
Funds moved to Hyperliquid; links remain unconfirmed
PeckShield also said the attacker used about $813,000 to buy a token linked to Monero. Blockchain analytics firm Bitquery traced funds from the Safe wallet through multiple addresses to Hyperliquid, where five accounts bought about $1 million worth of XMR1.
Bitquery said some of the on-chain activity resembled transactions seen after Monday’s Lighter incident, including a transfer of 160 ETH and purchases of XMR1. But it found no direct transfers between the two groups of wallets, so it could not establish whether the incidents involved the same actor. Similar transaction patterns alone do not confirm a connection.
Wallet owner and key exposure remain unclear
The owner of the affected Safe wallet has not been identified. Safe and Gnosis Guild have not commented on the incident. Publicly available information so far consists mainly of on-chain transactions, Zodiac’s account of how the permissions module handled the transfer, and analysis of the funds’ movement. How the key may have been exposed, the wallet’s precise permission settings and the funds’ final destination have not been confirmed.