What Happened in the Safe Module Exploit?
A third-party Safe module carrying the Squid name was exploited across Ethereum and Base, draining approximately $3.2 million from 86 Safes in about two hours, according to blockchain security firms.
The vulnerable contract was verified on Basescan under the name “SquidRouterModule,” which initially created confusion over whether the incident involved the cross-chain protocol Squid. Squid said the exploited contract was not built, deployed, or operated by the project and that its core router was unaffected.
“The contract called SquidRouterModule is unrelated to Squid. We don’t know yet who wrote or deployed this,” pseudonymous Squid co-founder Fig wrote on X.
Squid’s official account also said the core router was architecturally separate and untouched. The project later said early public reporting that referred to “SquidRouter” was technically inaccurate because the affected contract shared the Squid name but was a third-party product that had integrated with Squid and other protocols without contact with the team.
How Did the Attacker Drain the Safes?
The exploit centered on a module that accepted a caller-supplied constant string as proof that a message was secure. Passing that string allowed the attacker to execute arbitrary calldata and spend tokens held in affected Safes without signatures, according to Squid’s explanation of the incident.
The attacker used Foundry-based exploit contracts to call the module’s DelegateBundler path, impersonating authorized delegates on each Safe and triggering unauthorized swaps through Uniswap V3 pools. The targeted assets were then routed through attacker-seeded Uniswap V3 pools into a worthless attacker-created token called “u.”
The attacker later removed liquidity from the pools and consolidated the proceeds into roughly 3.07 million DAI, now held in a wallet beginning “0xa447…54859,” according to blockchain tracing. The exploiter’s initial funding of 2.1 ETH came from Tornado Cash.
The mechanics show why Safe modules can create serious risk when granted broad execution permissions. Safe wallets are designed to require multiple approvals before transactions are executed, but optional modules can allow approved smart contracts to act on behalf of the wallet. If a module is flawed or malicious, it can become a direct path to wallet funds.
Investor Takeaway
The incident was not a compromise of Squid’s core protocol, but it shows how third-party modules can create hidden wallet-level risk. For DeFi users and institutions, module permissions now need the same scrutiny as bridges, smart contracts, and custody infrastructure.
Why Does Module Attribution Matter?
Attribution matters because the contract name created an immediate reputational risk for Squid even though the project denied any role in building or deploying the module. In DeFi, naming confusion can quickly affect market trust, especially when an exploit touches cross-chain infrastructure or wallet permissions.
Safe Labs CEO Rahul Rumalla said the affected accounts “do not seem to be operated on official Safe Wallet product,” adding that it remained unclear how and where they were created and managed. He said they were likely created through externally deployed integrations.
Rumalla also said Safe Wallet surfaces such risks through “Safe Shield,” a feature designed to flag potentially malicious or unverified modules and guards before they are used. The exploited module had already been flagged as malicious by Blockaid, which is included in Safe Shield’s risk detection ruleset, he added.
That distinction is important for wallet providers, DeFi protocols, and users. The exploit appears tied to a third-party integration rather than Safe’s core wallet system or Squid’s core router. Even so, the loss shows that externally deployed modules can still put assets at risk if users or integrations grant them execution rights.
What Does This Mean for DeFi Security?
The exploit adds to a difficult year for DeFi security, with losses exceeding $770 million in 2026 and April alone seeing roughly 30 incidents and more than $630 million drained. The pattern keeps pressure on protocols to prove not only that their own contracts are audited, but also that the external modules, routers, and integrations around them do not create indirect exposure.
Squid recently announced a $6 million strategic funding round led by North Island Ventures, with Ripple, Dialectic, and Borderless also participating. The project has said it has completed 9 independent security audits, recorded no exploits, and maintained 99.99% uptime.
The timing makes the reputational angle sharper. Cross-chain interoperability remains one of crypto’s highest-risk infrastructure categories after repeated bridge exploits and messaging failures across the sector. Even when a core protocol is not affected, any contract carrying its name can create confusion for users, counterparties, and liquidity partners.
For exchanges, funds, and DeFi protocols using Safe-based infrastructure, the main lesson is operational. Wallet security cannot stop at multisig thresholds. Teams must review every enabled module, verify who deployed it, understand its permissions, and remove unnecessary execution paths. In smart-account systems, a weak module can bypass the protection users believe they have.
