Rug Pull

Security Updated Apr 2026

What is a Rug Pull?

A rug pull is a type of exit scam in crypto where the creators of a project suddenly drain its liquidity, abandon it, or manipulate its token to zero — leaving investors with worthless tokens. The term comes from “pulling the rug out from under” the community.

Rug pulls are one of the most common forms of crypto fraud. In 2021 alone, rug pulls accounted for 37% of all crypto scam revenue — over $2.8 billion stolen. Unlike smart contract hacks (which exploit code vulnerabilities), rug pulls are intentional fraud by insiders.

Types of Rug Pulls

1. Liquidity Pull (Most Common)

Developers create a token, list it on a DEX (usually Uniswap or PancakeSwap), and provide initial liquidity. Once enough buyers purchase the token, the devs withdraw all liquidity from the pool — leaving holders with tokens that can’t be sold.

Day 1: Dev creates TOKEN, adds $50K liquidity
Days 2-30: Marketing drives price up 10x, market cap hits $5M
Day 31: Dev removes all $500K liquidity
Result: TOKEN price drops to $0. Holders can't sell.

2. Mint-and-Dump

Developers retain the ability to mint unlimited new tokens (hidden in the contract code). After building hype and attracting buyers, they mint a massive supply and dump it on the market:

1. Dev deploys TOKEN with hidden mint function
2. Token pumps 50x through marketing
3. Dev mints 1 billion new tokens (invisible to buyers)
4. Dev dumps tokens into the liquidity pool
5. Price crashes 99%+ instantly

3. Honey Pot

A malicious smart contract where buying works normally, but selling is disabled or restricted. Users see the price going up, buy in, but when they try to sell… the transaction fails.

These are harder to detect because the contract appears to function correctly. The sell restriction is hidden in complex code or triggered by a specific condition.

4. Gradual Exit (“Slow Rug”)

Instead of a sudden exit, developers slowly sell their allocation over weeks/months while maintaining the appearance of active development. Price gradually bleeds 90%+ while the team claims “market conditions.”

5. DAO Governance Attack

As seen with Beanstalk Protocol ($182M loss), an attacker acquires enough governance tokens (via flash loan) to pass a proposal that drains the treasury.

Famous Rug Pulls

ProjectYearAmount LostHow
Squid Game Token2021$3.4MHoney pot — buying worked, selling didn’t
OneCoin2016-2018$4B+Fake blockchain, classic Ponzi (not DeFi)
AnubisDAO2021$60MLiquidity pull — devs drained LP pool
Meerkat Finance2021$31MCode exploit disguised as hack (rug)
Uranium Finance2021$50MHidden mint function exploited by team
Wonderland/Daniele Sesta2022$1B+“Slow rug” — inflated treasury through connected tokens
Balancer hack (feigned)2023VariousSome “hacks” were actually insider rugs

Red Flags: How to Spot a Rug Pull

Contract-Level Red Flags

Warning SignWhat to Check
Hidden mint functionVerify on Etherscan/BSCScan — can the team mint more tokens?
No timelock on liquidityIs LP locked? Check Team Finance or Unicrypt
Hidden transfer restrictionsCan all holders sell, or only whitelisted addresses?
Proxy contractCan devs upgrade the contract? What can they change?
Owner can pause tradingCan the team freeze all transfers?
High dev allocationTeam holds >20% with no vesting? Huge risk.

Project-Level Red Flags

  • Anonymous team: No real names, LinkedIn profiles, or track record
  • No audit: Contract hasn’t been reviewed by reputable firms
  • Guaranteed returns: “Can’t lose” or “Risk-free” promises
  • Pressure to buy fast: “Price doubles in 24 hours” urgency
  • Copy-paste whitepaper: Plagiarized or AI-generated with no technical substance
  • No product: Only a token and a Telegram group — no working dApp
  • “Dev wallet holds 30%+”: Developer controls too much supply

Tokenomics Red Flags

  • Low initial liquidity: <$100K in the LP pool
  • No vesting schedule: Team tokens are all unlocked immediately
  • Tax on sells: High sell tax (10-20%) that the team can modify
  • Blacklist function: Team can blacklist specific addresses from selling

How to Protect Yourself

Before Investing

  1. Check the contract on Etherscan: Read the source code (or use tools like Token Sniffer, RugDoc, or Honeypot.is)
  2. Verify liquidity is locked: Use Unicrypt or Team Finance to confirm LP tokens are locked for a reasonable period (6+ months)
  3. Check token distribution: Use Etherscan to see top holders. If one address holds >20%, that’s risky.
  4. Look for audits: Reputable firms (OpenZeppelin, CertiK, Trail of Bits) audit the contract
  5. Research the team: Real identities, past projects, community reputation
  6. Read the whitepaper: Does it explain real utility, or is it all hype?

Tools for Detecting Rugs

ToolWhat It DoesURL
Token SnifferAutomated contract analysis, scoringtokensniffer.com
Honeypot.isDetects honey pot contractshoneypot.is
RugDocCommunity-driven risk ratingsrugdoc.io
De.Fi RektDatabase of hacks and rugsrekt.news
GoPlus Security APIOn-chain security datagopluslabs.io

What to Do If You’ve Been Rugged

  1. Don’t try to buy more hoping for a “recovery” — the price isn’t coming back
  2. Report to authorities: FBI’s IC3 (ic3.gov) for US victims, local cybercrime units
  3. Document everything: Transaction hashes, developer communications, marketing materials
  4. Alert the community: Post on Twitter, Reddit, and the project’s channels to warn others
  5. Check for recovery: Some centralized exchanges freeze funds if scammers cash out there
  6. Tax write-off: In some jurisdictions, stolen crypto can be claimed as a capital loss

Frequently Asked Questions

Q: Are meme coins always rugs? A: Not always, but many are. Legitimate meme coins (like Dogecoin or PEPE) have fair launches with no team allocation. But 95%+ of new meme coins are either rugs or will trend to zero.

Q: If liquidity is locked, is it safe? A: Locked liquidity prevents the most common rug (LP drain), but doesn’t protect against hidden mints, sell taxes, or upgrade exploits. It’s necessary but not sufficient.

Q: Can DeFi protocols be rugged? A: Yes, through governance attacks (Beanstalk), hidden admin keys, or oracle manipulation. Always check if the protocol has a timelock on governance actions and a multi-sig for admin functions.