wardcrest

Rug pulls and honeypot tokens

How liquidity pulls, mint powers, blacklists, sell taxes and honeypot code trap buyers, and what to check before you touch a token contract.

Updated 15 Sept 2026 · Intermediate · 3 min read

In short

  • A rug pull is not one single pattern. Teams can remove liquidity, mint more supply, blacklist holders, raise sell taxes or stop selling altogether.
  • A honeypot token lets you buy but makes selling fail, often while showing a rising chart that attracts more victims.
  • Before you buy, check the token contract, the holder concentration, the liquidity depth and the admin powers. A clean check lowers risk; it does not prove honesty.

The two broad failure modes

Some tokens collapse because the market turns on them. Others collapse because the contract or the liquidity setup was designed to let insiders win at everyone else’s expense. The second group is what people mean by a rug pull or a honeypot token. The important question is not whether the token is new, but whether someone can change the rules after you buy.

On decentralised exchanges, many buyers only see the chart and the pool balance. They do not see who controls minting, pausing, blacklisting, fees or trading exemptions. That hidden control is where most deliberate token scams live.

How rug pulls are done

  • Liquidity pull. The team controls the pool’s liquidity provider tokens and removes the paired asset, leaving buyers with an untradeable market.
  • Mint power. The contract owner mints a large new supply and sells it into the pool, crushing the price.
  • Blacklist or transfer controls. The contract lets the owner block chosen addresses, often sellers, while insiders remain exempt.
  • Sell tax abuse. A token starts with a low fee, then raises the sell tax so high that ordinary holders cannot exit without severe loss.

These controls may appear directly in the token contract or in upgradeable logic behind it. That is why the question “is ownership renounced?” is helpful but not enough on its own.

What makes a honeypot different

A honeypot is built to trap buyers. The contract may allow buys from the pool but block sells from most holders, or require conditions that only the owner’s addresses satisfy. Explorers and wallets then show purchases going through while ordinary sale attempts revert.

Because people can buy but not sell, the chart often moves in one direction for a while. That fake strength is the lure. Some honeypots also airdrop small amounts to many wallets so the token appears widely held.

Checks to do before you buy

  1. Run the contract through our token risk, which flags common powers and suspicious holder concentration.
  2. Check who owns or can upgrade the token with the contract admin inspector. A token that one key can pause, blacklist or rewrite carries that key’s risk.
  3. Look at liquidity depth and who controls the liquidity position. Thin liquidity means small sells move the price sharply even without a scam.
  4. Review the largest holders. If a few addresses hold most of the supply, they can dominate the market whatever the contract code says.
  5. Search for evidence of real selling, not only buying. A token you can buy but never see sold is a bad sign.

What a check cannot prove

A token can pass basic technical checks and still be a bad trade. Teams can abandon a project, market makers can disappear, and insiders can sell heavily without any blacklist function or explicit honeypot code. A risk tool is best at finding powers and concentrations, not intent.

  • Treat unknown tokens sent to your wallet as bait. Do not approve them or visit links in their name or symbol.
  • Use a separate small wallet for experiments, so one bad token cannot expose your main holdings.
  • If you already approved a suspicious token or router, review the allowance in token approvals.

Put it into practice