Squid Clarifies Security Incident: Vulnerability Originated from Third-Party Safe Module, Core Protocol Unaffected

Cross-chain liquidity protocol Squid issued a statement regarding the approximately $3.2 million security incident that occurred today, stating that the attack was unrelated to the Squid core protocol and contracts. All Squid users and integrators were not affected and do not need to take any action. Squid indicated that the exploited vulnerability was in a third-party Gnosis Safe module, which is deployed on the Base and Ethereum networks and verified on Basescan as 'SquidRouterModule.' However, this contract was neither developed, deployed, nor operated by Squid, nor is it an official Squid Router contract, but rather a third-party smart wallet product that integrates protocols like Squid. The attack stemmed from a serious validation flaw in the module: the contract used a fixed string provided by the caller as the basis for validating a 'secure message,' and this string could be directly obtained from the verified contract code, allowing attackers to execute arbitrary calldata arrays and steal funds.
ETH1.29%
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