Gnosis Safe exploit for Base/ETH commot $3.2M through SquidRouterModule
Report say one Base/ETH exploit comot about $3.2M from 86 Gnosis Safe wallets for less than two hours, dem use third-party module wey dem dey call “SquidRouterModule.” PeckShield and Blockaid talk say wetin make am happen na because victims whitelist the module and give am extended permissions, so the contract fit run transfers without extra user signatures.
PeckShield yarn say the attacker fund the operation with 2.1 ETH through TornadoCash, then swap the stolen funds into about 3M DAI using Uniswap V3 pools wey the attacker control. Blockaid also note the quick take-over of 86 Gnosis Safe wallets, attribute am to overly broad approvals tied to the Safe module.
Later reports add technical detail: “SquidRouterModule” allow an immutable caller-provided string as a “security proof,” and victims accept am when dem add am as trusted Safe module. Important be say Squid clarify say the exploited module no be build, deploy, or maintain by Squid core protocol, and not all integrators/users kena affected.
For traders, this na short-term risk-off signal for Base/ETH multisig use. Make una review Gnosis Safe module approvals and whitelist settings, because similar “router/module” naming fit hide real contract risk wey connect to SquidRouterModule.
Neutral
Di tin happen clear say e be bearish for multisig/Safe users for short term, but e dey mostly limit to third-party module permissions (no be Squid core protocol). If traders tighten Safe module whitelists and dey monitor contract approvals, direct market impact on ETH/Base ecosystem pricing fit remain small. But ongoing scrutiny and possible follow-on investigation fit keep people cautious, stop any strong bullish or bearish move just from this news.