Market Cap: $2.0293T 4.29%
Volume(24h): $87.3584B -36.36%
  • Market Cap: $2.0293T 4.29%
  • Volume(24h): $87.3584B -36.36%
  • Fear & Greed Index:
  • Market Cap: $2.0293T 4.29%
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
Top News
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
bitcoin
bitcoin

$59006.193129 USD

1.28%

ethereum
ethereum

$1661.332716 USD

1.61%

tether
tether

$0.997851 USD

-0.06%

bnb
bnb

$538.955253 USD

2.39%

usd-coin
usd-coin

$0.999902 USD

-0.01%

xrp
xrp

$0.913476 USD

1.80%

solana
solana

$69.040176 USD

1.64%

tron
tron

$0.303101 USD

0.21%

hyperliquid
hyperliquid

$60.025698 USD

1.96%

zcash
zcash

$780.730135 USD

5.97%

monero
monero

$484.151346 USD

10.50%

dogecoin
dogecoin

$0.054064 USD

1.42%

unus-sed-leo
unus-sed-leo

$9.130164 USD

0.27%

chainlink
chainlink

$8.534407 USD

2.01%

cardano
cardano

$0.141421 USD

1.43%

Cryptocurrency News Articles

Safe Wallet Modules Under Scrutiny After $7.7 Million Exploit Involving Signature-less Transactions

Sep 16, 2026 at 11:25 am

A recent exploit highlights the risks of Safe Wallet Modules and signature-less transactions, resulting in a $7.7 million loss and renewed focus on security.

Safe Wallet Modules Under Scrutiny After $7.7 Million Exploit Involving Signature-less Transactions

NEW YORK, NY - The digital asset space is buzzing with a critical security alert following a significant exploit that saw approximately $7.7 million drained from a Safe multisig wallet. The incident, which occurred on September 15, 2026, underscores the evolving risks associated with smart contract wallets, particularly concerning the use of Safe Wallet Modules and the implications of signature-less transactions.

Exploit Reveals Vulnerabilities in Enabled Modules

The attack targeted a Safe multisig wallet, a system typically lauded for its robust security due to its multi-signature requirement. However, the exploit bypassed these safeguards through a pre-enabled module within the wallet. This module, designed to automate certain functions without requiring individual owner signatures for every action, became the entry point for the attacker. The wallet owners had previously activated this module, likely for a specific liquidity strategy, unknowingly creating a potential backdoor.

This event is not an isolated incident. A similar exploit on May 25, 2026, involving the SquidRouterModule, affected numerous Safe wallets, leading to losses estimated between $3.2 million and $4 million. These occurrences suggest a pattern where the true vulnerability in advanced multisig setups lies not in the signature threshold itself, but in the extensibility granted through modules.

Understanding Safe Wallet Modules

Safe modules are essentially separate smart contracts granted permission to execute transactions on behalf of the wallet. Their intended purpose is to streamline complex operations like automated payroll, recurring rebalancing, or sophisticated liquidity strategies, which would otherwise be cumbersome with constant multi-signature approvals. Technically, this is facilitated through functions like execTransactionFromModule. While not a flaw in the core design, the Safe documentation explicitly warns that enabled modules can execute arbitrary transactions, emphasizing the need to only integrate audited and trusted modules. Once activated, modules remain permanently enabled until explicitly deactivated, and they operate largely unseen in day-to-day wallet activity.

The $7.7 Million Heist: A Closer Look

The September 15 exploit saw the draining of 2,882.37 rsETH, a liquid restaking token from Kelp DAO, from a wallet managing a leveraged position. The outflow, valued at approximately $7.7 to $7.8 million, was facilitated by a bespoke module integrated with a Uniswap v4 liquidity strategy. The critical vulnerability lay in the module's entry point, which lacked sufficient access control and passed data directly to the wallet's execTransactionFromModuleReturnData function with a DELEGATECALL operation flag. This DELEGATECALL allowed the attacker to execute code with the wallet's own identity and storage, effectively acting as the wallet itself without needing any owner signatures.

The attacker leveraged a publicly accessible keeper multicall function, guiding the wallet's module towards a controlled Uniswap v4 pool. A hook within this pool, also controlled by the attacker, then unwrapped the aEthrsETH (rsETH within an Aave interest-bearing wrapper) into freely transferable rsETH, enabling the theft. Notably, an MEV bot named "yoink" intercepted this transaction from the mempool and executed it first, securing the funds.

Implications for Users and the Path Forward

The incident serves as a stark reminder for smart contract wallet users to meticulously review their enabled modules. The advice is simple yet crucial: check which modules are active and remove any that are no longer needed or whose purpose cannot be clearly recalled. This can be done through the Safe interface's settings or directly by querying the wallet contract using functions like getModules and isModuleEnabled. While inspecting modules is free, disabling them requires a standard transaction with the necessary owner signatures.

It's vital to distinguish between token approvals and module permissions. While token approvals allow specific token debits, modules grant broader operational control within the wallet. Both require separate, diligent management. Furthermore, the increasing use of layered wrappers, such as aEthrsETH in this case, adds complexity, requiring users to understand each contract layer involved in their holdings.

A New Era of Digital Asset Security?

While the exploit is concerning, it is not a reason to abandon smart contract wallets altogether. Instead, it's an urgent call to action for users to be more proactive in managing their wallet's security configurations. The recent implementation of the EU Cyber Resilience Act, requiring prompt reporting of actively exploited vulnerabilities, offers a layer of protection for users interacting with EU-based providers. However, for bespoke or individually commissioned contracts, the responsibility for vigilance remains squarely with the user.

So, take a moment, peek under the hood of your digital vault, and ensure only the most trusted and necessary tools are at play. After all, a little diligence now can save a lot of heartache (and a lot of ETH) later!

Original source:coinmarketcap

Disclaimer:info@kdj.com

The information provided is not trading advice. kdj.com does not assume any responsibility for any investments made based on the information provided in this article. Cryptocurrencies are highly volatile and it is highly recommended that you invest with caution after thorough research!

If you believe that the content used on this website infringes your copyright, please contact us immediately (info@kdj.com) and we will delete it promptly.

Other articles published on Nov 23, 2026