Handle an Unfamiliar Token Without Following Its Instructions
An unfamiliar token entry is a reason to check identity, not a reason to claim, sell or activate it. Treat names, links and instructions attached to that entry as untrusted content.
Record what appeared without interacting
Privately note the chain, full token contract and where the entry appeared. Distinguish a wallet row, an explorer transfer entry and an unsolicited message advertising a balance. Do not follow a URL embedded in the name or error text. Receiving an entry does not establish that you previously approved a spender, and the entry alone is insufficient to diagnose a compromised account.
Do not use a displayed price as verification
MetaMask documents scams involving unsolicited tokens that cannot be moved and error messages that direct users toward phishing sites. A quoted dollar value or recognizable symbol is not evidence of liquidity or a legitimate claim. There is no need to attempt a sale to prove whether a surprise token is real. Leave its value unresolved unless identity and the relevant facts can be established independently.
Verify claims through an independent path
If you expected an issuer distribution, reach the issuer’s established official documentation without using the token’s supplied link. Compare the stated network and contract. If no authoritative match exists, record that limit instead of selecting a similarly named asset. The RunixCoin mainnet native-coin rows are not a complete inventory of ERC-20 tokens, so their presence or absence cannot certify an unexpected token.
Separate hiding from changing permissions
Removing a row from a wallet view is a display choice, not proof that an on-chain allowance changed. If you already signed something after following a claim link, investigate the exact request, chain and permission through independently trusted information. Do not sign another unexplained request offered as a repair. Never provide recovery material to someone promising to unlock an airdrop. This guide does not offer a claim service, assess a particular token’s value or verify whether a specific account is safe.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.