How to avoid address poisoning scams where a scammer sends you 0 tokens?

Understanding Address Poisoning Mechanics

1. Scammers generate thousands of wallet addresses and send negligible token amounts—often 0.00000001 or exactly zero-value transactions—to them.

2. These transactions appear in blockchain explorers and wallet histories, creating a false impression of prior interaction with the sender’s address.

3. Victims who later copy-paste that address for legitimate transfers may unknowingly send funds to the scammer’s controlled wallet.

4. The poisoned address often mimics real project contracts or exchange deposit addresses, increasing deception through visual similarity.

5. Wallet interfaces rarely flag such micro-transactions as suspicious, allowing them to blend seamlessly into transaction logs.

Wallet-Level Defense Strategies

1. Disable auto-import of addresses from transaction history in MetaMask, Trust Wallet, and Phantom by toggling off “Suggest tokens” and “Auto-add tokens” features.

2. Manually verify every address before initiating a transfer—even if it appears in your recent history—by cross-checking checksums on Etherscan or Solscan.

3. Use wallet extensions that support address labeling; assign custom names only after confirming ownership via official project channels.

4. Avoid clicking “Send to this address” buttons embedded in explorer pages—always copy manually and paste into a clean send interface.

5. Enable hardware wallet confirmation for all outgoing transactions so each address must be visually verified on-device before signing.

Blockchain Explorer Verification Protocols

1. Paste any suspicious address into Etherscan, BscScan, or Solscan and examine its transaction tab—not just the token transfers but also internal transactions and contract creation details.

2. Check if the address has ever received ETH or native gas tokens; legitimate project addresses usually hold balances or have verified contracts.

3. Look for patterns like multiple identical zero-value transfers sent within seconds across different wallets—a hallmark of automated poisoning scripts.

4. Verify whether the address is verified: unverified contracts with no source code or audit links should trigger immediate caution.

5. Use the “Token Holders” tab to see if the address holds any meaningful balance—if it only contains dust or zero-value entries, treat it as compromised.

Transaction Signing Hygiene

1. Never sign a transaction without reading the full payload in your wallet extension—especially when interacting with unfamiliar dApps or bridges.

2. Reject any approval request asking for unlimited allowance to an unknown token contract, even if the token symbol looks familiar.

3. Use tools like Revoke.cash or Blockaid to scan active allowances and revoke permissions for contracts you no longer use.

4. When sending tokens, always double-check the recipient field after pasting—some malicious sites inject JavaScript that swaps the address upon paste event.

5. Avoid using mobile wallets for high-value transfers unless they offer on-screen address confirmation with full checksum visibility.

Frequently Asked Questions

Q: Can zero-value transactions be reversed or blocked on-chain? No. Once confirmed, even zero-value transfers are immutable and cannot be undone or filtered retroactively by nodes or wallets.

Q: Do hardware wallets protect against address poisoning? Hardware wallets prevent private key exposure but do not stop users from copying poisoned addresses—on-device address verification remains essential.

Q: Is there a way to detect poisoned addresses programmatically? Some open-source scripts analyze Etherscan API responses for clusters of zero-value inbound transfers, but no mainstream wallet integrates real-time detection natively.

Q: Why do scammers prefer zero-value over tiny-value transfers? Zero-value transactions cost less gas and avoid triggering spam filters in explorers or wallet notifications designed for non-zero token movements.