Solid Protocol Hack

TOTAL LOST $72K
Low Rugpull ethereum

Summarize with AI

Affected Chain ethereum Incident surface
Recovered - No recovery reported
All-Time Rank #1628 By amount stolen
Protocol Type Yield Target category

Incident Overview

On LinkedIn, the project team created accounts with fictitious images and identities.

The contract deployer distributed tokens in big amounts between external wallets at:

https://etherscan.io/tx/0x83dfa98a…0dd868

https://etherscan.io/tx/0x64797cdc…e548a4

https://etherscan.io/tx/0xb8fa1eff…1212b0

https://etherscan.io/tx/0xa20c511b…e7eb52

https://etherscan.io/tx/0xaf70f4b3…edafe2

One from the recipients added initial liquidity at:

https://etherscan.io/tx/0xb875065e…7e2452

The other addresses started selling tokens in multiple transactions, for example:

https://etherscan.io/tx/0xc5e5f42d…6db17d

https://etherscan.io/tx/0x923bb84b…6ed103

https://etherscan.io/tx/0x494cf90d…2d263e

https://etherscan.io/tx/0x040b78ab…18a1cf

The liquidity was removed by the external address at:

https://etherscan.io/tx/0x25c58351…4094b7

https://etherscan.io/tx/0xeb822c02…7daccb

Incident Report

Protocol / Project Solid Protocol
Date of Incident
Affected Chain(s) ethereum
Attack Technique Rugpull
Classification Exchange (DEX)
Primary Source View Post-Mortem

Protocol Information

Protocol Type Yield
Affected Token SOLID
Official Website Solv.finance/?chl=CMC
Protocol Twitter/X @solidprotocol

Market Context at Time of Hack

Token Categories
Spartan Group BNB Chain Ecosystem Bitcoin Ecosystem BTCfi Binance Megadrop Binance Ecosystem Binance Listing Made in China

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 ethereum smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Solid Protocol's contract logic - root cause: exchange (dex)
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 Solid Protocol, these are the critical security checks that could have prevented this incident (December 2020).

  • 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 Solid Protocol

The Solid Protocol 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