Safe wallet transfer puts role-key and permission settings in focus

For builders configuring a Safe wallet with Zodiac Roles, the distinction between who can initiate a transaction and what the permissions policy allows matters. In reporting published November 17, 2026, Cointelegraph described a suspected theft of about $6.45 million from a Safe wallet.

Ethereum records reviewed by Cointelegraph showed approximately 4.39 million USDC and 1.72 million syrupUSDC transferred from the wallet in one transaction on Monday, November 16. Blockchain security firm PeckShield reported the suspected theft, citing onchain investigator Specter.

Safe wallet transfer puts role-key and permission settings in focus (1)

Johannes Moormann, a co-founder of Zodiac, told Cointelegraph that the transaction passed through the wallet’s Zodiac Roles Modifier. The module checked it against the wallet’s configured permissions and allowed it. Moormann said the transaction came from a long-standing role member’s key that was most likely compromised, and that the custom policy permitted the transfer almost certainly unintentionally. He said Zodiac’s contracts worked correctly, that the incident did not indicate a vulnerability affecting other wallets using the module, and that Zodiac had no access to the wallet’s keys or permissions or involvement in its setup. Zodiac had not been in contact with the affected team.

Safe wallet transfer puts role-key and permission settings in focus (2)

PeckShield said the attacker used approximately $813,000 to buy Monero-linked tokens on Hyperliquid. Separately, analytics firm Bitquery traced funds from the Safe wallet through multiple addresses to Hyperliquid, where five accounts bought approximately $1 million in XMR1 tokens. Bitquery noted similarities to fund movements after Monday’s Lighter incident, but found no transfers connecting the two wallet groups and could not establish whether the same actor was involved.

The wallet owner had not been identified. Cointelegraph said Safe and Gnosis Guild had not responded to requests for comment by publication.

Further reading