Most fake tokens copy a real project name and ticker, then trick you into buying on a Uniswap-style decentralized exchange before you realize the contract owner can drain liquidity or block your sale. A block explorer like Etherscan, BaseScan, or BscScan lets you disprove a scam in under a minute: check whether the source code is verified, count how many wallets actually hold the token, look at who owns the liquidity pool, and skim the comments for honeypot tells.
Key takeaways
- Search ads are the top fake-token delivery vehicle, so never trust the first link Google returns for a token name.
- A verified contract with public source code is safer than an unverified one, but verification alone does not guarantee the code is honest.
- Real projects have hundreds or thousands of distinct holders; a scam with the same ticker often shows fewer than fifty wallets.
- Reading the contract's "Read Contract" tab reveals hidden taxes, transfer cooldowns, or whitelists that scream honeypot.
- revoke.cash is the right tool to clean up old token allowances after a close call, even one that ended without a loss.
Why fake token contracts exist, and who actually falls for them
The phrase "fake token contract" covers a wide spectrum, from outright malware to contracts that technically function but route most of the value back to the creator. The common thread is that the deployer publishes a contract address that resembles a legitimate project, then waits for buyers to paste that address into a swap interface. Once liquidity appears on a decentralized exchange (a peer-to-peer trading app where users trade directly against a shared token pool), buying feels easy and exit feels normal, until it isn't.
The scale is significant. Chainalysis estimated that rug pulls and token impersonation schemes extracted more than 9 billion dollars from crypto users between 2021 and 2024, with the typical victim losing a few hundred dollars at a time. The victims are rarely beginners doing obvious things wrong. They tend to be people who clicked a polished link, recognized the right name and ticker, and skipped the few sanity checks that would have warned them.
The good news is that on a public blockchain every transaction is inspectable, so the scam leaves fingerprints. The bad news is that those fingerprints only help you if you know which buttons to click on a block explorer (a search engine for transactions, contracts, and wallet balances on a specific chain such as Ethereum, Base, or BNB Smart Chain). This article walks through the exact checks, in the exact order, so the safe path becomes muscle memory rather than a lesson you learn by losing money first.
The scam pattern you are most likely to face
The single most common delivery vehicle is a paid search ad. You type "PEPE coin" or "TURBO token" or any other trending name into Google. The top result, marked "Ad," leads to a clean-looking site with a polished logo and a "Buy now" button. That site gives you a contract address and tells you to paste it into Uniswap, PancakeSwap, or another decentralized exchange. Everything from the URL to the whitepaper is set dressing. The only thing that is real is the contract address, which is freshly minted by the scammer.
Several tells travel with this pattern. The "official site" often registered its domain in the past few weeks, which you can check on who.is. The listed social channels point to accounts with low follower counts or names that differ from the real project's handle by a single character. Sometimes the scammers impersonate the real project's admin on Telegram or Discord, sending DMs with the fake link. In every case the destination is the same: a token whose contract the deployer fully controls.
Once a victim swaps into the contract, the harm usually comes in one of three forms. The first is the classic "honeypot," a token whose smart contract code blocks sells while allowing buys, so the holder can watch the price rise and yet never exit. The second is a "tax token" that charges a 50 percent or 90 percent fee on every transfer, with most of that fee going to the deployer's wallet. The third is a slow rug pull, where a seemingly normal token trades for days and then the deployer removes the liquidity pool in one transaction. A block explorer reveals each of these patterns before you commit funds, if you know where to look.
What you actually need: an explorer that matches the chain
Every major chain has at least one mainstream block explorer. On Ethereum mainnet that is Etherscan. On Base, the layer-2 network built by Coinbase, it is BaseScan. On BNB Smart Chain, it is BscScan. On Arbitrum and Optimism it is Arbiscan and Optimistic Etherscan respectively. On Solana the equivalent tool is Solscan or the explorer built into Phantom wallet. Each one shows the same set of fields for a given contract: transactions, holders, contract code, and a "Read Contract" tab for the public functions baked into the code.
Always paste the token address into the explorer that matches the chain you intend to trade on. A real Ethereum contract and a fake copy on BNB Smart Chain can share the same ticker, and mixing those up is itself a way to get burned. If the explorer you load does not recognize the address, that is its own warning: the contract has had almost no organic activity, and the address you were given may not be the one the project actually uses.
A useful habit is to bookmark the three or four explorers you actually use rather than clicking through search results. Search engines happily show scam domains above the real Etherscan URL when someone has bought the keyword. Going directly avoids the entire class of "wrong site" mistakes.
Check one: is the source code verified?
The single most important button on any token contract page is the contract tab. Above the code area Etherscan and its sibling explorers show a small green checkmark labeled "Contract" when the deployed bytecode matches published source code. That checkmark is the gateway to reading what the token actually does. Without it the code area shows only opaque bytecode, which tells you the deployer chose not to publish what the contract really does.
An unverified contract is not automatically a scam. Many small projects simply never uploaded their source. But unverified source combined with any other red flag is decisive. Treat "unverified + low holder count + locked social channels" as the scam it almost always is. Conversely, a verified contract lets you read the actual Solidity code and verify that the functions behave the way the project claims.
Inside the source you should grep for a few specific patterns. A function named something like setTax, setFee, or updateTaxRate that the deployer alone can call means the sell tax can be raised overnight. A function that excludes addresses from fees, with the deployer hardcoded as the excluded wallet, means the contract is designed to favor the creator. A function with the word blacklist paired with a mapping named isBlacklisted means any wallet can be locked out of selling. None of these by themselves prove malice; many projects use one or two of them legitimately. The combination matters.
Check two: how many holders actually exist
Scroll to the "Holders" tab. A legitimate token with real trading volume usually shows hundreds, often thousands, of distinct wallets. A fake token that just launched will show a small number, sometimes dominated by a cluster of wallets the deployer controls, with names like "0x000...dead" or sequential addresses that funded each other from the same source. The exact threshold depends on the project's age, but as a rule of thumb, fewer than fifty holders on a token that claims to be a major established project is a hard stop.
The "Top holders" list is where this gets interesting. Etherscan and its peers show each holder's percentage of supply. If the top three or four wallets together own more than half the tokens, the "market cap" number shown on trackers is essentially fictional. Even worse, watch whether those top wallets are labeled with a public name tag such as "Uniswap V2: ROI," indicating that the tokens are sitting in the liquidity pool, or whether they are unlabeled addresses that funded each other minutes before the contract was deployed. Concentrated supply in unnamed wallets is the layout of a planned exit.
There is a subtle follow-up worth doing on the holders tab. Click a few of the wallets and look at their history. A wallet that received tokens directly from the deployer contract in a single batch, then routed them to the liquidity pool, is a setup wallet. A wallet that bought from the pool on Uniswap after the project already had buzz is a real buyer. When almost every holder is the first kind, you are looking at a contract that paid itself to create the illusion of a crowd.
Check three: who owns the liquidity pool
On Etherscan you navigate to the contract address of the liquidity pool itself, not just the token, and look at the "Contract" tab there. The Uniswap V2 and V3 pair contracts let the pool creator, known as the deployer, manage the liquidity position. Real projects either burn the deployer's ownership by sending the LP (liquidity provider) tokens to a dead address or hand the LP tokens to a time-locked contract that prevents withdrawal for weeks or years. Either move means the deployer cannot pull the pool in one click.
Look for an Etherscan comment or an audit note that mentions a lock. Platforms like Unicrypt, Team.Finance, and PinkSale have recognizable patterns: the LP tokens live in a contract named after the lock service, and the lock contract has a function called "unlock" whose release time is set in the future. Click through to that lock contract and read its unlock date. If the unlock is weeks or months out, the project has at least committed to a slow exit. If there is no lock and the deployer still owns the LP tokens, you are trusting a stranger to behave well, which is exactly what scammers do not do.
Even a locked LP is not a guarantee. Some projects lock with a 24-hour or 7-day window and then quietly drain the pool the moment it unlocks, calling the result a "natural market event." Look at how long the lock is and whether the unlock triggers any automatic migration. "Locked" only matters if the lock lasts longer than your expected holding period, which for most users should be measured in months, not hours.
Check four: read the public functions of the contract
The "Read Contract" tab on Etherscan shows every public function that does not require sending a transaction. For a token, the functions that matter are typically named something like name, symbol, decimals, totalSupply, balanceOf, allowance, and the various fee-related variables. Two patterns should get your attention immediately. The first is a function that sets a per-transfer fee to a value above a few percent. Anything north of 10 percent, especially when the fee can be changed by the deployer at will, is a tax token. Some apply a low buy fee and a punishing sell fee, which is why it is worth reading both directions if the contract exposes them separately.
The second pattern is a "max transaction" or "max wallet" limit combined with a whitelist of exempt addresses. Real projects use these limits to fight bots, but they leave the deployer's own wallet exempt. A 1 percent max transaction rule plus a 1 percent max wallet rule plus a deployer exemption means only the deployer can move meaningful size, which means the only exit is at the price the deployer chose. Read the contract, do not just skim the marketing site.
If you are not a Solidity developer, focus less on understanding every line of code and more on understanding which functions exist and whether the deployer alone can call them. The Explorer labels functions as read-only or write functions, and "onlyOwner" patterns show up in the source. When a single address controls most of the writable knobs, the token is in spirit a centralized database, no matter how decentralized the marketing says it is.
Practical implications: the 60-second pre-flight checklist
Before any swap on a token you have not used before, run the following sequence. Open the chain's explorer, paste the contract address, and stop at the first red flag. The checks, in order, are: contract is verified, holder count is in the hundreds at minimum, top holders are not dominated by a small cluster of freshly funded wallets, the liquidity pool's LP tokens are either burned or locked with a long unlock, and the Read Contract tab does not show a punishing tax or a transfer blacklist. Five checks, under a minute, no special tools required.
Layer a few habits on top of that checklist. Always get the contract address from the project's verified social media or a reputable listing such as CoinGecko's "Contracts" section rather than from search ads. Cross-check the address character by character: many scams rely on the first and last few characters matching, with a middle string of letters swapped out. When in doubt, ask in the project's official Discord channel using a regular message rather than answering a DM. Admin impersonators almost always slide in by direct message.
Keep separate wallets for trading. Your "hot" wallet, the one you connect to dApps (decentralized applications), should never hold more than you are prepared to lose in a single session. Your "cold" wallet, a hardware device whose keys never touch an internet-connected computer, should hold long-term positions, and you should not be connecting it to a new DEX to buy a meme token. The cost of this discipline is small. The cost of skipping it is the entire balance on that wallet.
If you already interacted: revoke.cash and what to do next
Approvals are the overlooked risk. When you swap on Uniswap or any similar venue, you grant the token contract permission to spend your tokens, and that permission (called an "allowance") persists on-chain until you revoke it. A malicious contract can drain the approved tokens later, even if you no longer intend to trade it. This is why a tool called revoke.cash exists. It shows every active allowance held by your wallet and lets you reset each one to zero with a small gas fee, cutting off the relationship.
The right time to visit revoke.cash is right now, not after a loss. Cleaning approvals once a month takes about ten minutes and closes the window through which most post-trade exploits operate. It is also the right call after a near-miss, when you approved a token contract, recognized the scam during the read-only checks above, and never actually swapped. The approval itself is still open, and revoking it is the responsible close-out.
Pair revocation with a rotation habit. After any wallet-draining incident, even an attempted one, move remaining assets to a fresh wallet and stop using the compromised address. Treat a wallet the way you would treat a credit card with a suspected skim: it is not safe to keep. Hardware wallets are inexpensive compared to the balances they protect, and migrating once every few years is a small price for peace of mind.
How to follow token launches the smart way
Token launches move fast and so do the scams around them. Tracking every new contract, holder count, and liquidity lock manually is a losing game, especially when the same fraud pattern recurs dozens of times per week on every major chain. Zippfeed surfaces token-launch and airdrop headlines with sentiment scoring (bullish, neutral, or bearish) and an importance rating, so you can tell genuine launches from recycled tickers and skip the ones where the red flags are already flashing.