SQUID GAME Hack

TOTAL LOST $56K
Low Rugpull

Summarize with AI

Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #1695 By amount stolen
Protocol Type Exit Scam/Rugpull Target category

Incident Overview

SQUIDGAME token was rugpulled on PancakeSwap, with 55,539 USD worth of liquidity removed by the scammer.

SQUIDGAME, a BEP20 token trading on PancakeSwap, experienced an exit scam when the scammer removed 237.31 WBNB worth 55,539 USD from the liquidity pool. The stolen funds were transferred to another EOA and then distributed between multiple addresses. Notably, the scammer sent 21,274 USD to the developer's address 11 hours and 19 minutes before the sale of a large number of tokens.

Deployer Address:

https://bscscan.com/address/0x6dA430E6…91CDbd

Scammer Address:

https://bscscan.com/address/0x2cFe2D07…577e61

Liquidity Removal Transaction:

https://bscscan.com/tx/0x11ad1095…5cf7a0

Funds Sent Transaction between Deployer's and Scammer's addresses:

https://bscscan.com/tx/0x53ea5e3c…dea000

Incident Report

Protocol / Project SQUID GAME
Date of Incident
Attack Technique Rugpull
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token SQUIDGAME
Official Website squid.land/
Protocol Twitter/X @SquidCto
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
BNB Chain Ecosystem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of rugpull and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in SQUID GAME's contract logic - root cause: token
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Hard to catch — private key / OpSec failures are outside smart contract audit scope

If you're auditing a protocol with similar architecture to SQUID GAME, these are the critical security checks that could have prevented this incident (November 2023).

  • Verify all logic paths related to Rugpull are guarded by proper access controls and input validation
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Sources & References

Learn to Prevent the Next SQUID GAME

The SQUID GAME hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial