Fake LAYER Hack

TOTAL LOST $465K
Low Rugpull

Summarize with AI

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

Incident Overview

On January 21, 2025, a fake SOLAYER token crashed to nearly zero within three hours after a community alert was raised. Scammer's profit could be estimated as 1,938 WSOL (~$465,000).

The attacker leveraged a fake SOLAYER contract  (LAYERruDbdbxZTT4cfFZPRLEoG4cGwn8HpwpgTToWDg) to mislead investors into purchasing worthless tokens. After artificially inflating the token’s perceived value, the attacker made a single significant “rug transaction,” liquidating 17 trillion of these fake tokens in exchange for nearly 2,000 WSOL. Once the attacker’s large sell order cleared, the token’s price plummeted by almost 100% in a matter of hours.

Malicious Address:

FU2cbiQea7mRX72BhPG716b1Q8eWu62pR2Ue5S9DC8jm

Fake Contract:

LAYERruDbdbxZTT4cfFZPRLEoG4cGwn8HpwpgTToWDg

Rug Transaction: https://solscan.io/tx/4Bio6okCE3qnLk5tEFnP9DQruihadB66vo51DkMBT9MRH6MCSwKSc88TiFJorxXkabb49oLSkgPTjvaHNyb7GRhW

Incident Report

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

Protocol Information

Protocol Type Exit Scam/Rugpull
Official Website stakelayer.io/
Protocol Twitter/X @StakeLayerIO
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
DeFi BNB Chain Ecosystem Restaking

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 Fake LAYER'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 Fake LAYER, these are the critical security checks that could have prevented this incident (January 2025).

  • 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 Fake LAYER

The Fake LAYER 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