Rug Pull Detector
See who can still drain, mint or freeze a token before you buy it.
Free to start: scanning is included in a free tier with a monthly usage allowance. Higher volumes and API access are on paid plans.
A rug pull is not one mechanism but several: the team withdraws the liquidity, an owner mints an unlimited supply and sells into the pool, or a privileged function freezes everyone else's ability to sell. This rug pull detector scans an ERC-20 contract for all of them. It reports the token's live DEX liquidity, what the owner can still do, and whether the contract can be changed after you buy. It covers Ethereum, BNB Smart Chain, Base, Arbitrum, Avalanche and Robinhood Chain.
The three ways a token gets rugged
Liquidity removal is the classic version: the pool is drained and there is nothing left to sell into. Supply inflation is quieter: a mint function the deployer kept lets them create tokens and sell them into your liquidity. Permission-based rugs are quietest of all: a blacklist, a trading pause or a tax the owner can raise to 100% stops you selling while the price still shows on a chart.
What this scanner checks
Tok{In} decompiles the contract's deployed bytecode with Gigahorse (Dedaub's own decompiler) and simulates a real buy and sell against live DEX liquidity. On top of the trade simulation it maps privileged functions: who owns the contract, whether ownership is genuinely renounced, whether a mint or burn path still exists, whether transfers are gated by mutable storage, and whether the contract sits behind an upgradeable proxy that can be repointed later.
Why "ownership renounced" is not the whole answer
Renouncing ownership sets the owner to the zero address, and a lot of checklists stop there. It does not help if the risky function was never gated by ownership in the first place, if a second privileged role remains, or if the contract is a proxy whose admin is a different address entirely. The scan reports the privileged paths that actually exist in the bytecode rather than the single owner field.
Read liquidity alongside the flags
A contract with no dangerous permissions and no meaningful liquidity is still a bad trade: there may be nothing to sell into. The scan lists the token's pools, their liquidity, and the tax observed on each, so you can see whether the market is real before you weigh the contract risk.
Frequently asked questions
- How can I tell if a crypto token will rug pull?
- You cannot know a future intention, but you can measure the capability. Check whether liquidity is meaningful, whether an owner can mint new supply, whether taxes are modifiable, whether wallets can be blacklisted, and whether the contract is upgradeable. If none of those powers exist, a rug becomes much harder. The scanner above reports each one.
- Does a locked liquidity pool mean a token is safe?
- No. An LP lock stops the deployer withdrawing liquidity for the lock period, which removes one rug mechanism. It does nothing about hidden mints, modifiable sell taxes, blacklists or an upgradeable proxy, and the lock expires. Treat it as one input, not a verdict.
- How much does the rug pull detector cost?
- There is a free tier that covers occasional checks, within a monthly usage allowance. Heavier use and programmatic access through the Tok{In} API are on paid plans. Current allowances and pricing are shown on the plans page.