SLS Hack

TOTAL LOST $41K
Low Rugpull

Summarize with AI

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

Incident Overview

SLS project's token GSLS lost the price by more than 85% after the token deployer-related EOA address drained liquidity. The scammer made a profit of 41,122 $USD.

GSLS is the BEP20 token trading on PancakeSwap. On 3rd October, the token deployer sent 40,000 $GSLS to EOA address. The address received 25,000 $BUSD from another address and added liquidity with them and received $GSLS to the liquidity pool on PancakeSwap.

Consequently, the scammer made many trades with small amounts at the beginning. When the initial token holder sent 360,000 $GSLS to the scammer, the tokens were sold immediately, which leads to the token price dump and liquidity draining for the total amount of 41,122 $BUSD.

Scammer address:

https://bscscan.com/address/0x89cc4469…f421ab

Token deployer:

https://bscscan.com/address/0xf60910b4…bca05d

Initial token holder:

https://bscscan.com/address/0xaa06eec2…9f2f7a

Liquidity pool:

https://bscscan.com/address/0x84f9d526…3DDfF3

Incident Report

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

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token GSLS
Team Anonymous
Source Code Unverified

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 SLS'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 SLS, these are the critical security checks that could have prevented this incident (October 2022).

  • 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 SLS

The SLS 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