The Industry Spread

Follow

XFacebookLinkedIn

Digital Assets

Safe multisig loses $6.44 million with no owner signature

A Safe multisig lost about $6.44 million on November 16 after a role key moved USDC and syrupUSDC. No owner signed, Safe says, and the contracts held.

Safe multisig loses $6.44 million with no owner signature

A Safe multisig lost about $6.44 million on November 16, 2026, and the signature that counted was not an owner's. The loss sits next to contracts both vendors say held: one delegated role key sent a transaction the wallet's own policy accepted. The dollar reading only meets the $6.45 million figure PeckShield circulated once Maple Finance's yield token is marked above par, instead of being counted as another dollar of USD Coin (USDC).

The transaction landed at 11:35:23 UTC. A caller beginning 0x065F invoked execTransactionWithRole on a module attached to the Safe beginning 0x5953, which Etherscan labels as a smart account by Safe. The call redeemed 3,851,642.22 gtUSDC, a Gauntlet vault-share token, and the Safe received 4,387,188.43 USDC from Morpho. It then sent that USDC, plus 1,717,918.96 syrupUSDC, Maple's yield-bearing USDC token, to an address beginning 0x2b02. DefiLlama printed syrupUSDC at $1.193 at 11:23 UTC, about 12 minutes earlier. At that mark the syrup leg was about $2.05 million. Marking the USDC at $1, the two legs sum to about $6.44 million.

Safe's own account is narrower than the round-number alerts. On November 16 the firm posted that this "affected one multisig," that "Safe smart contracts and Safe{Wallet} are unaffected," and that "No owner signed it." A role member's key, "likely compromised," sent the transaction through a third-party Roles module "installed outside Safe{Wallet}." Zodiac, maker of the Roles Modifier, said it found no contract vulnerability, and that "a role member key, probably compromised, sent a transaction that a custom policy allowed but likely never intended."

The modifier is built for that delegation. Owners define a role and the calls it may make, and a member sends those calls without owner signatures. Zodiac's security notes call a module a path into the Safe without signatures, and they say role conditions check calldata, not outcomes: prices, balances, and slippage are invisible to the rule. A policy that allows a Morpho redemption and a syrupUSDC transfer will not revert when the key does both. Morpho and Maple are not quoted in Safe's post, Zodiac's post, or Cointelegraph's account. Galaxy's Morpho vaults for Fireblocks clients raise the same question: which key is allowed to redeem.

Johannes Moormann, co-founder of Zodiac, told Cointelegraph the review matched those posts. "There is no vulnerability in the module. The contracts worked correctly. The transaction came from the key of a long-standing role member, which was most likely compromised," he said. He added that the custom policy permitted the transaction, almost certainly unintentionally, and that the operators, not Zodiac, controlled the keys. Zodiac had not been in contact with them. The holder of the Safe multisig has not been identified, and Safe's posts do not offer to cover the loss.

PeckShield, citing on-chain analyst Specter, put the loss at $6.45 million, about $4.3 million of USDC and $1.7 million of syrupUSDC, and said the hacker spent about $813,000 buying XMR on Hyperliquid. Those components add to $6 million, short of the headline, because they price syrupUSDC near face value rather than at the $1.193 print. The token amounts on the transaction do not change. Only the premium on the yield token separates a $6.44 million sum from the $6.45 million alert.

The same Monday, Lighter halted withdrawals after a leaked API key. Cointelegraph reported that Bitquery saw similarities with those fund movements, including a 160 Ether (ETH) transfer and purchases of XMR1, and found no transfers linking the two groups of wallets. A sound contract still pays out when the trusted credential leaks. That is a different failure from a case in which spoofed approvals, rather than signer keys, moved the funds.

It is also not the June code bug. Zodiac's notes record an ERC-1271 authorization bypass on June 1, 2026 in Roles Modifier v2.1.0 and Delay Modifier v1.1.0, with Gnosis Pay the main deployment hit and patched releases on June 19, 2026. Neither vendor ties this outflow to that bug or names the mastercopy this Safe ran.

Safe has limited the case to one multisig, a module installed outside Safe{Wallet}, and no owner signature. Zodiac called it a potential theft the policy likely never intended. Neither post shows the allow-list, so another desk cannot tell whether its own Safe multisig wrote the same scope. An owner threshold does not see a call the role may send alone, and neither firm has offered to cover the tokens. Funds left this Safe multisig, and the owners did not sign.

This article is informational analysis only and is not financial, investment, or trading advice. Cryptocurrencies are highly volatile and can lose substantial value rapidly. Past performance and historical patterns do not guarantee future results. Do your own research and consult a regulated financial adviser before making any investment decision.

Reporting by Karthik Subramanian. Filed 18 November 2026, 07:48 GMT.

Digital Assets Correspondent

Karthik Subramanian is a founder, writer, and technology consultant with nine years in the crypto ecosystem.

All 1,857 stories by Karthik Subramanian