scams addresses security

· Educational crypto

Address poisoning: why history is not a contact list

How lookalike addresses get planted in your transaction history, why copying from that list is risky, and a slow-down check before you send. Literacy only—not a recommendation to use any wallet, explorer, or asset.

Wallets and explorers often shorten addresses (first few characters, last few characters). Humans copy from “the last time I sent there.” Address poisoning exploits both habits. Public materials from MetaMask Help, Etherscan’s information center, and ethereum.org security pages describe the same pattern: a tiny or zero-value transfer from a lookalike address so it shows up in your history.

What the attacker does

  1. They watch a public transfer you already made (your address, or a counterparty you used).
  2. They generate a vanity address whose start and end match that real address, while the middle is different.
  3. They send you a dust, spoofed-token, or zero-value transfer from that lookalike. Receiving it does not, by itself, move your funds—but it poisons the history.

Later, if you tap the most recent similar-looking row and paste that address as the destination, the send goes to them. Confirmed chain transfers are generally not reversible (ethereum.org: sending to the wrong address is a common, often unrecoverable mistake).

Why the UI makes it easy to miss

A slow-down check before you send

TakeawayHistory is a log, not a contact list. Poisoning plants a lookalike row. Verify the full destination (especially the middle) from a source you already trust before you send.

Related free docs

Sources

Educational content only — not investment advice. This page explains a documented abuse pattern; it does not recommend any wallet vendor, token, or trade.

← All docs