Squid clarifies security incident: the vulnerability originated from the third-party Safe module, and the core protocol was not affected

Golden Finance reports that the cross-chain liquidity protocol Squid issued a statement regarding the approximately $3.2 million security incident that occurred today, stating that this attack is unrelated to the Squid core protocol and contracts, and that all Squid users and integrators are unaffected and do not need to take any action. Squid stated that the exploited component is a third-party Gnosis Safe module, which is deployed on the Base and Ethereum networks and has been verified on BaseScan as “SquidRouterModule.”
However, this contract was not developed, deployed, or operated by Squid, nor is it an official Squid Router contract; it is a third-party smart wallet product integrated with protocols like Squid.
The attack originated from a serious validation flaw in this module: the contract uses a fixed string provided by the caller as the basis for “security message” verification, and this string can be directly obtained from the verified contract code, allowing attackers to execute arbitrary calldata arrays to steal funds.
ETH-0.32%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pinned