Loading...
UpgradeSign in

Rug Pull Risk Detector

Analyze Token Security

Detect potential rug pull risks by analyzing token contract code, liquidity locks, ownership, and other security indicators.

Rug Pull Risk Analyzer

Understanding and Avoiding Rug Pulls

Learn how to identify red flags and protect yourself from rug pull scams in DeFi.

What is a Rug Pull?
A rug pull occurs when developers abandon a project and run away with investors' funds. Common tactics include draining liquidity pools, minting unlimited tokens, or using hidden backdoors in smart contracts.
Liquidity Analysis
Locked Liquidity: Legitimate projects lock their liquidity (LP tokens) for a set period. If liquidity is unlocked, developers can withdraw it at any time, instantly crashing the price to zero.
Red Flags to Watch For
Unlocked Liquidity: The biggest red flag.
Minting Function: Check if the contract allows minting new tokens.
High Sell Tax: Taxes above 15-20% are suspicious.
Security Checklist
Before investing:
1. Check if LP is locked.
2. Verify contract ownership is renounced or behind a multisig.
3. Search for the project on Twitter/Telegram for community activity.
4. Look for a professional audit report.

Frequently Asked Questions

Only invest in projects with locked liquidity, renounced ownership, audited contracts, and doxxed teams. Start with small amounts, verify contract code, and be skeptical of guaranteed returns.

No, but new tokens carry higher risk. Legitimate projects have transparent teams, clear roadmaps, audited code, and locked liquidity. Do your own research and never invest more than you can afford to lose.

A soft rug is when developers slowly dump their tokens or abandon the project without a sudden catastrophic event. They might stop communication or fail to deliver promised features while selling off their holdings.

It helps, as it means the developer can no longer change contract functions (like fees). However, they could still rug if they hold a large supply of tokens or if the liquidity isn't locked.

Longer is better. A lock for 1 month is risky. Look for locks of at least 6 months to 1 year, or vesting schedules that match the project's roadmap.

Yes. Audits check for code vulnerabilities, not intent. An audit can't stop a developer from dumping their own allocation or abandoning the project. Always read the audit report carefully.