SimpleSwap

Honeypot Tokens & Rug Pulls: When You Can Buy but Cannot Sell

A honeypot blocks your sell from the moment the contract is deployed. A rug pull lets you trade normally – until whoever holds the liquidity walks away with it. Both end the same way: you can't get out.

Two failures that look identical from outside

Honeypot

A trap written into the code before you ever arrive. You buy, the transaction succeeds, then your sell reverts.

Rug pull

A timing trap. You can buy and sell normally at first – until whoever holds the liquidity removes it, or dumps supply into your bids.

A honeypot is a locked door – you were never getting out. A rug pull is a room that gets emptied while you're still standing in it.

Deploying a token costs almost nothing and needs no permission – which is the point of the technology, and the reason this category exists at all.

25,000+

tokens launched per day on Solana alone, five straight days in January 2026 (Dune data) – roughly 70% via Pump.fun

67,000

suspicious tokens flagged by GoPlus across Ethereum, BNB Chain and Base in Q4 2024

6.08M

of the 47.9M tokens Token Sniffer has indexed across 15 chains are flagged as suspicious

Take the total loss figures you'll see elsewhere with a grain of salt. Annual estimates for rug pulls range from a few hundred million to several billion dollars, depending on whether the count is limited to funds provably stolen or includes every token whose liquidity ever collapsed – which sweeps in ordinary failed projects along with deliberate fraud. The scale isn't in question. The precision is.

How the trap looks in the code

Honeypot contracts don't need clever cryptography. They need one conditional in the transfer function.

Sell-blocking transfers

The contract checks whether you're selling, not buying, and reverts only that transaction. Sells fail with a generic error most people mistake for a slippage problem.

Blacklists and whitelists

Instead of blocking everyone, the contract keeps a list. Ordinary buyers get added after purchase; a handful of addresses never do – which is why the chart can still show real-looking sells.

Modifiable tax

An owner-only function can change the sell tax at will – low while people buy, then near 100% the moment the owner decides. You can technically still sell. You'll receive almost nothing.

Mint rights

If the owner can mint new supply, the token count isn't fixed no matter what the tokenomics chart promised. Your share can be diluted to nothing without a single sell.

Pause functions

A single address can hold a switch that halts all transfers for everyone, at any time.

Proxy contracts

An upgradeable proxy routes calls to separate logic the deployer can swap out. The contract you checked on Monday isn't necessarily the one running on Friday.

Why the chart can lie

The standard reassurance is to check the chart: price rising, volume real, sells visible. In a whitelist honeypot, all of that can be true, and none of it protects you – the wallets exiting are simply the ones the contract permits to exit.

Visible sells on a chart tell you someone could sell – not that you can.

The one-minute check

None of this requires reading Solidity. Four steps, in order, using free tools.

  1. 1

    Run two scanners against the contract

    GoPlus flags honeypot logic, modifiable tax, hidden owner and mint functions. Token Sniffer matches the bytecode against known scam templates. Run both – when they disagree, that disagreement is information.

  2. 2

    Simulate a sell

    Honeypot.is executes a real simulated buy and sell against the contract and reports what actually happens, including the real tax rather than the advertised one. It's the most direct test there is.

  3. 3

    Check whether liquidity is locked

    Look for a lock with a reputable locker like Unicrypt or Team Finance, verify the lock transaction itself rather than a claim on a website, and check the expiry date. A lock that expires next week isn't a lock.

  4. 4

    Check holder concentration

    Bubblemaps or the block explorer's holder tab show whether supply is spread out or clustered in a few connected wallets – the ones who can trigger the exit you'll absorb.

If all four check out, do a small test buy immediately followed by a test sell. The purchase proves nothing – only the exit does.

What a clean scan doesn't mean

A green scanner result means no known trap was detected – not that the token is safe. New patterns show up before detection rules catch them; automated scans match known patterns, they don't understand code.

A red flag isn't automatically fraud either – some legitimate teams keep ownership early to fix bugs, or run temporarily higher taxes. What matters is whether the team is identifiable and those powers are time-locked. Unrenounced ownership, an anonymous team and unlocked liquidity together aren't three separate yellow flags – it's the same red flag, three times.

A swap can get you into a token. It can't get you out of one that won't let you leave.

If a token's contract blocks the sell, no exchange, aggregator or DEX can execute it. The failure looks like a routing problem – it isn't. The token itself is refusing the transaction, and SimpleSwap can't override a sell restriction written into someone else's contract.

An asset that's traded across many venues for a long time has already been through some filter, however imperfect. A contract deployed yesterday hasn't – the check above is the only filter you get. Our only official domain is simpleswap.io.

Want the full breakdown?

Read the full guide for the exact one-minute check, real loss estimates, and why unrenounced ownership plus an anonymous team plus unlocked liquidity is one red flag, not three.

Key takeaways

  • A honeypot blocks your sell from day one; a rug pull lets you trade normally until the liquidity disappears.
  • Visible sells on a chart prove someone could sell – not that you can.
  • Run two scanners, simulate a sell, and check locked liquidity before you buy, not after.
  • A clean scan means no known trap was detected, not that the token is safe.

Honeypot Tokens & Rug Pulls FAQ

A rug pull is when whoever controls a token's liquidity or supply exits suddenly – draining the pool, dumping their holdings, or minting new tokens to dilute everyone else's share. Trading can look completely normal right up until the moment it isn't.

A honeypot blocks your sell from the moment the contract is deployed – the trap is written into the code before you ever buy. A rug pull lets you trade normally at first; the token only becomes unsellable once the people holding the liquidity remove it or dump their supply.

Not on its own. A whitelist-style honeypot can show real, rising sells on the chart – they're just coming from the handful of wallets the contract lets exit. Trading activity doesn't prove a token is sellable for everyone.

Run it through two scanners (GoPlus and Token Sniffer), simulate a sell with a tool like Honeypot.is, check whether liquidity is locked and for how long, and look at how concentrated the holders are. If all four check out, do a small test buy followed immediately by a test sell.

No swap service can be, and that's worth saying plainly. A honeypot or a drained pool blocks the sell at the contract level – nothing on our side, or any exchange's, can override that. The only real protection is checking a token before you buy it, not after.