In this article5 sections
A Safe multisignature wallet lost about $6.45 million in cryptocurrency on Monday, Nov. 16, 2026, after what Zodiac’s co-founder described as a likely key compromise combined with permissive wallet settings. Cointelegraph reported the suspected theft, citing blockchain security firm PeckShield and on-chain investigator Specter.
Ethereum records reviewed by CoinPulseHQ show approximately 4.39 million USDC and 1.72 million syrupUSDC were moved out of the wallet in a single transaction on Monday. crypto.news reported the same incident, describing the split as roughly $4.3 million in USDC and $1.7 million in syrupUSDC, with the attacker converting part of the proceeds into Monero.
Also read: BTCPay Server urges shutdown after hot wallet drains
Key facts
- PeckShield flagged the incident on Nov. 16, 2026, citing Specter’s findings of suspicious transfers from a Gnosis Safe wallet, per crypto.news.
- Johannes Moormann, co-founder of Zodiac, said the transaction passed through the Zodiac Roles Modifier, which checked it against its configured permissions policy and allowed it.
- Moormann said the transaction came from the key of a long-standing role member, “which was most likely compromised,” in a statement to CoinPulseHQ.
- PeckShield reported the attacker spent roughly $813,000 purchasing Monero-linked tokens on Hyperliquid, per Cointelegraph.
- Specter separately indicated about $1.2 million was converted into Monero through Wagyu, crypto.news reported; the two figures describe different reported transactions.
How the Zodiac module works
According to Zodiac’s developer documentation for the Roles module, wallet owners can define which contracts an authorized address may interact with, which functions it can call, and which transaction parameters are permitted. Once a role is assigned, its holder can execute approved transactions without renewed signatures from the Safe’s owners. Moormann said the wallet’s custom permissions policy almost certainly allowed the transfer unintentionally, and that the wallets’ operators — not Zodiac — controlled its keys and permissions. Zodiac had no access to them and was not involved in the setup, and it has not been in contact with the affected team.
PeckShield also reported that the attacker used roughly $813,000 to buy Monero-linked tokens on Hyperliquid. Bitquery traced funds through multiple addresses to Hyperliquid, where five accounts purchased about $1 million in XMR1 tokens, and noted similarities with fund movements following Monday’s Lighter incident, including a 160 ETH transfer and XMR1 purchases. Bitquery said it found no transfers connecting the two wallet groups and could not establish whether the same actor was involved.
Earlier Safe module incidents
The incident is the latest in a run of compromises touching Safe wallets through third-party modules, as catalogued by crypto.news. In October, a FlashLoopAdapter exploit affected two Safe wallets tied to Aave positions, with estimated losses of $305,000. In May, Blockaid identified a $3 million exploit involving the SquidRouterModule that hit 86 Safe wallets across Ethereum and Base; Squid later said the affected module was third-party code. Gnosis Pay faced a June incident involving the Zodiac Delay Module that traced to a software flaw from October 2023; Gnosis Pay said affected users were reimbursed, with a small portion still under recovery at its July disclosure.
Moormann told CoinPulseHQ the latest incident did not indicate a vulnerability affecting other wallets using the Roles module. The identity of the wallet owner has not been established; CoinPulseHQ contacted Safe and Gnosis Guild for comment and had not received a response by publication.
Why it matters
Safe is a common custody layer for teams holding treasury funds, and delegated-permission systems such as Roles are designed to reduce friction by letting role holders act without collecting a fresh quorum of signatures. This incident shows how that convenience can fail when a role key is compromised and the policy attached to it is broader than intended. Because Zodiac says the module executed as designed, the fix sits with wallet operators: tighter permission policies and better key management rather than a contract patch.
What to watch
Attribution of the wallet owner, any statement from Safe or Gnosis Guild, and further tracing from PeckShield and Bitquery on where the funds on Hyperliquid move next.
Reported by Cointelegraph.
Sources: Cointelegraph, crypto.news

