Why a pool-drain backdoor can exist while a token still trades

A token may have an active chart and successful trades while its contract contains a path that can remove tokens from its own liquidity pool. Those facts are not contradictory: the backdoor is a capability that may exist before anyone uses it.

What the finding establishes

Hawkeyescan simulates calls from privileged addresses discovered in the contract, including the owner, deployer or addresses the contract names. A pool-drain finding means one of those addresses can move the pool’s tokens without the approval an ordinary transfer would require. That can undermine the reserves traders expect to be available.

What it does not establish

The finding alone does not prove that a drain already happened, that every sell fails, or that a named team intended to exploit it. “The contract contains a path that can drain its pool” is supported by the simulation. “Nobody can exit” requires separate evidence, such as the simulated holder transfer or sell reverting.

Why liquidity can look normal

Until the capability is exercised, the pool can continue quoting and processing swaps. Volume and price movement describe activity; they do not remove a dangerous permission from the token contract. Burned liquidity tokens are also not sufficient protection if the token contract itself can move assets held by the pool.

How to read the page

• Blocked: a conclusive behavioural check failed, so Hawkeyescan does not offer a Buy button.
• Simulated sell or transfer: a separate result about whether an ordinary holder can move the token.
• Liquidity and activity: evidence that a market exists now, not evidence that the permission is harmless.
• Verdict time: the contract can change, so the time of the check matters.

The cautious statement is precise: the capability exists in the tested contract state. It is not necessary to invent a failed exit to explain why that matters.