Fake Token Contract Detector

WHAT IT DOES

Fake Token Contract Detector reads live on-chain data from any EVM token contract and uses AI to detect impersonation attempts, name-squatting, and fake tokens that mimic legitimate projects. It examines token metadata including name, symbol, decimals, and total supply for suspicious variations—extra spaces, Unicode lookalike characters, swapped letters, or unusual formatting that impersonates well-known tokens. It scans contract bytecode for proxy patterns, compares bytecode fingerprints against known token standards, and flags non-standard implementations. It analyzes holder distribution to identify extreme concentration that enables rug-pulls. It checks for liquidity, owner-controlled mint/burn functions, blacklist mappings, and trading pause status. The AI generates a plain-language verdict—REAL, FAKE, or SUSPICIOUS—along with specific discrepancies and risks before you interact with the token.

HOW TO USE

Paste any EVM token contract address into the input field. The tool reads the token's bytecode and metadata including name, symbol, decimals, total supply, and owner address. It scans transfer event logs to build a holder distribution map and calculate concentration risk. It detects proxy patterns and bytecode anomalies. The AI receives all this data and compares the token against known legitimate token standards to detect impersonation. It returns a verdict with risk level—REAL (low risk), SUSPICIOUS (medium risk), or FAKE (high risk)—along with a detailed plain-language explanation of exactly why the token appears genuine or fraudulent, and what specific risks exist for anyone who buys, sells, or approves it.

CHUNKED LOG SCANNING WITH AUTOMATIC BACKOFF AND BYTECODE FINGERPRINTING

The tool fetches transfer event logs to build holder distribution maps. Public RPC endpoints enforce varying block range limits per request—some allow 10,000 blocks, others only 2,000, and some reject requests that span more than a few hundred blocks. This tool automatically detects the per-request range limit by probing and adjusts batch sizes accordingly. It walks backwards from the current block in chunks and, if a request fails due to a range limit, it halves the chunk size and retries. If a request fails due to rate limiting, it backs off exponentially and resumes from the last successfully scanned block. The scan is capped to the most recent 200,000 blocks to balance completeness against performance; older tokens may show partial holder data, but the most active holders are still captured. Additionally, the tool computes a bytecode fingerprint hash to compare against known token standards, enabling detection of tokens that copy legitimate bytecode but deploy under fake names.

WHAT IT CANNOT SEE

This tool cannot detect fake tokens that perfectly mimic legitimate token bytecode without any on-chain differences—if the bytecode, metadata, and deployment pattern are identical to a genuine token, it cannot distinguish them from the legitimate version. It cannot detect off-chain impersonation, fake websites, or social media scams. It cannot analyze bytecode that is obfuscated beyond EVM disassembly limits. It cannot verify that a token's name or symbol match the official project's off-chain branding; it can only compare on-chain strings against common patterns. It cannot detect fake tokens that use identical bytecode but differ only in deployment address. It cannot see pending transactions not yet in the mempool. It cannot determine if a token's website, Twitter, or Telegram presence is fraudulent. It cannot detect tokens that have not been deployed yet.

PLEASE NOTE

EVM chains only. This tool reads on-chain data and generates AI explanations—it does NOT sign transactions or execute any on-chain actions. The wallet's own signature prompt remains the final gate for every real action. Always review the exact transaction details in your wallet before approving any signature or token interaction. The AI assessment is informational only and does not constitute financial or security advice. Always verify token contract addresses against official project documentation before interacting with any token.