0x4100250f4100…4100250c

ConfirmedSecurity614 vB119 sat/vB3 min decode

Safe Wallet Lost $6.45M in Suspected Key Compromise Attack

About $6.45 million left a Safe wallet on Ethereum. Zodiac says a compromised role-member key and permissive settings, not a module flaw, enabled the suspected theft.

Safe wallet reportedly drained of $6.5M after likely key compromise
WitnessSafe wallet reportedly drained of $6.5M after likely key compromiseRoyBuri / pixabay

By Tom Whitfield

About $6.45 million left a Safe wallet on Ethereum on Monday, according to blockchain records reviewed by Cointelegraph and a PeckShield alert citing on-chain investigator Specter. The records showed approximately 4.39 million USDC and 1.72 million syrupUSDC leaving the wallet in one transaction.

The wallet owner has not been identified. Cointelegraph contacted Safe and Gnosis Guild for comment, but neither had responded by publication.

What enabled the $6.45 million transfer?

Johannes Moormann, Zodiac’s co-founder, said his team reviewed the transaction and confirmed that it passed through the wallet’s Zodiac Roles Modifier. The module checked the transfer against its configured permissions policy and allowed it.

Moormann said: “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.”

Moormann said the wallet’s custom permissions policy permitted the transaction, almost certainly unintentionally. The wallet’s operators controlled its keys and permissions. Zodiac had neither access to those controls nor involvement in the setup.

Zodiac also had not contacted the affected team. Its conclusion rests on the transaction review and the suspected compromise of a role-member key, rather than a first-hand account from the wallet operators.

Does the Zodiac Roles module have a vulnerability?

Specter first flagged the Zodiac Roles module as part of the suspected attack. Moormann said the incident did not indicate a vulnerability affecting other wallets using the module.

The module allows Safe users to assign permissions for specific transactions. In this case, the contract approved an action the configured policy allowed while the role-member key was probably compromised.

Two conditions likely enabled the transfer: compromise of an established role-member key and a custom policy broad enough to authorize it. That combination differs materially from a contract-code failure.

For other Zodiac deployments, the evidence does not establish a broad module vulnerability. It does show how a permissive policy can magnify the operational consequences of one compromised role-member key.

Where did the funds move?

Blockchain security firm PeckShield said the attacker used approximately $813,000 to purchase Monero-linked tokens on Hyperliquid. Blockchain analytics firm Bitquery separately traced the Safe wallet’s funds through multiple addresses to Hyperliquid.

Five accounts linked to that flow purchased approximately $1 million of XMR1 tokens, according to Bitquery. The activity moved the tracked funds from Ethereum balances into Hyperliquid markets, creating a second venue for on-chain tracing.

The documented route now has two stages: the Ethereum transfer and subsequent Hyperliquid purchases. That structure gives investigators separate records for origin and downstream trading activity, although the wallet owner remains unidentified.

Does the Lighter flow establish a connection?

Bitquery noted similarities with fund movements following Monday’s Lighter incident. Those parallels included a 160 ETH transfer and purchases of XMR1.

But Bitquery found no transfers connecting the two wallet groups and could not establish whether the same actor controlled them. The comparison remains a lead rather than evidence of common ownership or a confirmed link.

The absence of a direct transfer leaves the overlap resting on transaction behavior and asset selection. Bitquery’s findings do not support attributing both wallet groups to one actor.

What remains unresolved?

Three items remain open at publication:

  • The wallet owner has not been identified.
  • Safe and Gnosis Guild had not responded to Cointelegraph.
  • Zodiac had not contacted the affected team.

The on-chain path now spans two systems: Ethereum and Hyperliquid. The next checkpoint is owner identification and a response from Safe or Gnosis Guild; without those, the evidence supports a suspected key compromise, not a module-wide flaw.

via x.com (Original)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles