How to tell if a token was rugged or just failed naturally

19 October 2026

A token that stops trading was either deliberately drained by its creators (a rug pull) or simply ran out of buyers and liquidity through normal market failure. The difference matters for reporting losses, understanding tax implications, and deciding whether to bother with a project's recovery attempts. You can usually tell which happened by checking the transaction that removed the liquidity, the pattern of the price chart, and the behavior of the token's contract.

What a rug pull looks like in practice

A rug pull is an intentional act. The creator or someone with contract control removes the liquidity pool funds, making it impossible to sell the token back. The signature sign is a single transaction that drains the liquidity pool, often labeled "remove liquidity" on a block explorer like Etherscan or BscScan. After that transaction, the token's price on a DEX drops to near zero, and the swap quote shows "insufficient liquidity" or "price impact too high."

Rug pulls often follow a pattern:

• Ownership renounced after the pull. Some creators renounce ownership of the contract after draining liquidity, to make it look like the project was abandoned rather than stolen. Check the contract's owner history. If renunciation happened minutes after the liquidity removal, it was a rug.
• Liquidity was never locked. Many rug pulls have a "dead-token-postmortems/liquidity-locked-zero-percent/">liquidity locked 0 percent" status from the start. The creator could withdraw the funds at any moment. If the liquidity was locked for a period but the unlock transaction removed it early, that is also a rug.
• Honeypot mechanics. Some rug pulls never let anyone sell from the beginning. The contract blocks sell transactions or charges a 100% fee. This is a honeypot, not a natural failure. You can test this by trying to sell a tiny amount on a DEX with a high slippage setting; if the transaction fails consistently, the token may be a honeypot.

What natural failure looks like

A token that fails naturally never had its liquidity removed by a single malicious transaction. Instead, the liquidity pool dries up gradually as sellers outweigh buyers. The price chart shows a slow decline over days or weeks, with many small sell transactions, rather than one sharp drop.

Signs of natural failure:

• Liquidity remains in the pool. You can still see a balance in the DEX's liquidity pool, even if it is tiny (a few dollars worth). The token can still be swapped, but the price impact is extremely high because the pool is shallow.
• The contract is still active. The contract's functions still work. You can transfer tokens, and the contract has not been paused or frozen. The token just has no demand.
• No single drain transaction. Looking at the token's transaction history on a block explorer, you will see many small sells over time, not one large removal of liquidity. The last few transactions are usually tiny sell attempts by holders trying to exit.
• Social media went quiet gradually. The project's Twitter or Telegram stopped posting weeks before the token died, with no final announcement or excuse. Rug pulls often have a sudden silence or a dramatic "we got hacked" message right before the liquidity disappears.

How to check the critical transaction

1. Find the token's contract address on a block explorer like Etherscan, BscScan, or Solscan.
2. Go to the "Holders" or "Token Transfers" tab. Sort by transaction time from newest to oldest.
3. Look for a transaction labeled "remove liquidity" or "burn" that involves the token's liquidity pool (the LP token contract). A rug pull will have this as one of the last major transactions.
4. Check the sender of that transaction. If the sender is the same wallet that deployed the token contract or a wallet that received tokens from the deployer, it was likely a rug.
5. Compare the total value removed. If the transaction removed more than 90% of the pool's value in one go, it was a rug. Natural failure shows many small removals or no removal at all.

When the difference is blurry

Some tokens sit in a gray area. A project might have abandoned development, then a later exploit or a sudden sell-off by a large holder drains the liquidity. That is not a planned rug, but the result for you is the same. The key question is whether the token's creators were directly responsible for the loss. If you cannot find a single transaction that removed liquidity, and the contract is still functional, it is safer to treat it as a natural failure for tax and reporting purposes.

What to do with the information

For tax reporting in most jurisdictions, a rug pull is a theft loss, while a natural failure is a capital loss. Check your local tax authority's guidance. If the token was rugged, you may be able to report the loss in the year the rug happened. If it failed naturally, the loss is realized when you sell the token for zero value or when the token is formally delisted.

For security, treat both types the same: revoke any token approvals you gave to the dead token's contract. A rug-pulled contract might still have functions that let the creator take other tokens from your wallet if you left approvals open. The page on revoking token approvals covers how to do that.

The honest answer is that most dead tokens that you cannot sell were rugged, because natural failure usually leaves at least a tiny ability to trade. But checking the single drain transaction is the most reliable way to know for sure.

Back to dead tokens