How to Spot the Pattern of a Slow Rug Pull in Dead Tokens

11 November 2026

A slow rug pull isn't a single event. It’s a process, and the token usually looks alive while it’s happening. The pattern is visible if you know what to check: liquidity that drains gradually, social channels that shift tone, and a developer wallet that moves small amounts out over weeks. You can spot it after the fact, and often before it completes, by looking at the same three things: the liquidity pool, the token contract, and the team's behavior.

This page covers the common sequence of a slow rug pull and how to recognize the signs in tokens that have already stopped trading.

The difference between a quick exit and a slow drain

A classic rug pull is abrupt. The developer removes all liquidity in one transaction, the price goes to zero, and the trading pair dies the same day. A slow rug pull is the opposite. The developer wants to keep the appearance of a working project while extracting value. So the liquidity pool stays open, the price drifts down, and the exit happens in pieces. The token doesn’t die from a single kill transaction. It dies from a thousand small withdrawals.

The end result is the same: you hold a token you cannot sell for anything close to what you paid. But the timeline and the evidence differ. A quick rug leaves a single, obvious transaction. A slow rug leaves a trail of ordinary-looking transfers that only make sense in aggregate.

Step 1: Check the liquidity pool for a downward trend

The most reliable sign of a slow rug pull is the liquidity pool's total value over time. On a DEX, the liquidity pool is the sum of the two paired tokens (for example, the project token and WBNB or WETH). If the project is legitimate, the liquidity should stay roughly flat or grow with trading volume and fees. If the developer is slowly pulling out, the pool value will trend downward in a sawtooth pattern: small upswings from buy pressure, then larger withdrawals.

You can check this on a blockchain explorer. Find the pair address for the token (usually listed on the project's page or on DEX tools like Dexscreener or Geckoterminal). Look at the pair's transaction history. You are looking for a repeated pattern: a sell, then a withdrawal from the pool, then another sell, then another withdrawal. Each withdrawal might be small, often just above the threshold that would trigger a large price impact warning. But over a month, they add up to a significant portion of the total liquidity.

A key detail: the withdrawals should come from the same address or a small cluster of addresses. If you see the same wallet pulling out 0.5% of the pool every few days, that is not a random trader. That is the developer monetizing their position.

Step 2: Look at the token contract for hidden mechanisms

Slow rug pulls often rely on contract functions that let the owner mint new tokens or tax transfers in a way that hides the drain. You can check the contract source code if it is verified on a block explorer. Look for these specific functions:

• Mint function with an owner-only modifier. If the contract has a function that creates new tokens and only the owner can call it, the developer can sell those new tokens into the pool. This dilutes your holdings and lowers the price, but the sales are spread out so the chart doesn't show a single crash.
• A transfer fee that goes to a specific address. Some contracts take a small percentage on every trade and send it to a "marketing" or "development" wallet. In a slow rug, that wallet is controlled by the developer. The fee might be 2% or 3%, which seems normal. But if the wallet accumulates the token and then sells it in a single large transaction, that is the rug completing.
• A "cooldown" or "max wallet" function that is adjustable. This is trickier. The developer might set a high max wallet limit during the launch to look fair, then lower it after there is enough trading volume. When the limit drops, any wallet holding more than the new limit cannot sell. The developer can then sell their own holdings freely, knowing that the small holders are stuck.

You don't need to understand Solidity to check this. Use a block explorer's "Read Contract" section. Look at the owner address, the max transaction amount, and any function with a name like setFee, updateTax, or mint. If any of these can be changed by the owner and the owner is not a time-locked contract, the project has a slow rug capability even if it has not used it yet.

Step 3: Examine the social channel for the "pivot"

A slow rug pull is not just a technical process. It is a social one. The developer needs to keep people holding while the drain happens. The pattern here is a shift in communication style over several weeks.

At launch, the team is active. They answer questions, post updates, and talk about upcoming features. As the drain continues, the tone changes. Updates become vaguer. They start talking about "partnerships" without naming anyone. They post about "technical difficulties" when the chart looks bad. Then they go quiet for a few days. Then they post a single message about "rebranding" or "moving to a new chain."

This is the pivot. The rebranding announcement is usually the last step before the project dies completely. The developer wants to convince you that the token still has potential, so you hold while they finish selling. The quiet periods are not accidental. They are a choice to reduce the number of people watching the chain.

You can check the history of the project's official social accounts. Look at the dates of the posts and compare them with the liquidity pool withdrawals. You will often see that the most optimistic announcements come right after the largest withdrawals. That is the team talking the price up to create exit liquidity for themselves.

Step 4: Check the pair's age and the developer's history

A slow rug pull often uses a new pair contract. The developer creates a fresh liquidity pool for the token, which is normal. But the same developer wallet might have launched other tokens that also died slowly. You can check the wallet's transaction history on the block explorer. Look for prior token launches and whether those tokens also have a history of downward-drifting liquidity. If the same wallet launched three tokens that all followed the same pattern, you are looking at a serial slow rugger.

Also check the age of the liquidity pool itself. If the pool was created recently but the token has been trading for months, that means the developer migrated the liquidity. Migration is not inherently suspicious, but it is a common moment to hide a slow drain. The new pool might have a different token amount or a different paired asset, which changes the price calculation.

Why the pattern is hard to see in real time

The reason slow rugs work is that each individual step looks like normal market activity. A 1% drop in the pool every few days could be a large holder selling. A 2% transfer fee could be a marketing cost. A vague tweet could be a busy team. The pattern only becomes clear when you look at the whole sequence over a month or more.

If you are checking a token that has already stopped trading, you have the benefit of hindsight. The pool chart shows the full drain. The contract shows the owner functions. The social history shows the shift in tone. The only question is whether you take the time to connect those dots.

A dead token is dead. The slow rug pattern does not change that. But understanding the pattern helps you avoid the next one.

Back to dead tokens