Local comparison · no wallet connection

Crypto address poisoning checker

Compare a trusted crypto wallet address with one copied from transaction history. Highlight look-alike prefixes, suffixes and changed middle characters locally without connecting a wallet.

Important: A similarity warning does not prove an address is malicious. Always verify the complete destination through a trusted source or saved address book.

✓ The comparison stays in this browser. Nothing is submitted to the server.

How the scam works

The attacker wants you to copy from history without checking the middle

01

Observe a real transfer

An attacker watches public stablecoin transfers and learns an address you use.

02

Create a look-alike

A new address is generated with a similar beginning and ending but a different middle.

03

Poison transaction history

A tiny or zero-value transaction puts the look-alike in your recent activity.

04

Wait for a copy mistake

The attacker hopes you later copy the shortened address without checking every character.

A safer address routine

  • Do not copy a destination from recent transaction history.
  • Use a saved address book or a fresh verified deposit page.
  • Check several characters in the middle, not only the beginning and end.
  • For a new destination, send a small test and independently confirm receipt.
  • For high-value transfers, verify the address on a hardware-wallet screen when available.

Security reference: MetaMask · Address poisoning scams

Frequently asked questions

What is address poisoning?

An attacker sends a tiny or zero-value transfer from a look-alike address so that a victim may later copy the wrong address from transaction history.

Does a similar address prove it belongs to a scammer?

No. Similarity is a warning signal, not proof of malicious ownership. Verify the full destination through a trusted source.

Does this tool upload wallet addresses?

No. The comparison runs in the browser and the form does not send the entered addresses to the server.

Are Ethereum addresses case-sensitive?

Normal 0x address identity is compared without case here, because checksum capitalization can differ. TRON and many other address formats remain case-sensitive.