Quick Answer
Honeypot detection · LP lock · Mint authority · Sell tax
| Signal | Risk | Description | Example |
|---|---|---|---|
| BSC Honeypot (PancakeSwap) | Critical | BSC honeypots follow the same pattern as Ethereum but are more common due to near-zero deployment costs. The contract allows buys through PancakeSwap but reverts or charges 100% tax on sells. BSC's low gas means thousands of new honeypots deploy daily. | A BSC memecoin that processes buy transactions normally but includes `require(tx.origin == _devWallet)` in the sell path — only the dev wallet can sell, all other sell attempts revert. |
| PancakeSwap LP Not Locked | Critical | LP tokens from PancakeSwap's liquidity pool are held by the deployer. PancakeSwap V2 and V3 LP tokens are standard ERC-20 tokens on BSC — the holder can call removeLiquidity() at any time. BSC's lower gas costs make the LP removal faster and cheaper than on Ethereum. | The BALD rug on Base (Aug 2023, $23M) followed the same LP removal pattern. BSC equivalent: any unlocked LP token held by deployer can be removed in a single transaction. |
| Fork Clone Backdoor | Critical | The most common BSC rug pattern: copy Uniswap or PancakeSwap contract code, add a hidden migrator() or setMinter() function that allows moving all LP tokens or minting tokens. The original Sushi Swap migrator controversy spawned hundreds of BSC clone backdoors. | A BSC yield farm forked from SushiSwap adds a `migrate(address newAddress)` function callable by the deployer — this function moves all staked LP tokens to an attacker-controlled address. |
| Migrator Function | High | A migrator() function in a staking or yield farm contract allows the contract owner to move all deposited LP tokens to an arbitrary address in a single call. This is the standard SushiSwap-era clone rug mechanism and is still deployed on BSC frequently. | MasterChef fork on BSC with setMigrator(address _migrator) — deployer deploys a malicious migrator contract, calls setMigrator(), then calls migrate() on each pool, draining all staked LP tokens to their wallet. |
| Anti-Bot Mechanism Rug | High | Many BSC tokens launch with 'anti-bot' features — max transaction limits, trading cooldowns, blacklists — marketed as security features. These same features can be used as rug mechanisms: block all sells while team dumps, or blacklist all holders before draining liquidity. | BSC token launches with 'anti-bot' blacklist. Team adds 5,000 buyer addresses to the blacklist post-launch, freezing all their tokens. Team removes liquidity from the now-one-sided pool. |
| No Source Code Verification | Medium | BSC contracts that are not verified on BSCScan cannot be audited. Given that BSC deploys hundreds of scam tokens per day, unverified contracts should be treated as high-risk by default. BSCScan verification is free and instant — there is no legitimate reason for a project contract to remain unverified. | A BSC token with 10,000 holders but no verified source code on BSCScan. Without source, you cannot check for honeypot patterns, mint functions, blacklist capabilities, or migrator functions. |