Independent guide · Crypto

Spot and stop address‑poisoning, clipboard‑replacement and wallet phishing before you send crypto

How address‑poisoning, clipboard clippers and approval/phishing scams work, why they succeed, and simple, evidence‑backed checks to use before sending funds.

Editorial illustration for: Spot and stop address‑poisoning, clipboard‑replacement and wallet phishing before you send crypto

Attackers manipulate address lists, the clipboard, or transaction approvals to redirect funds. Verifying full addresses, using hardware‑wallet device checks, sending a small test transfer and maintaining endpoint hygiene are the most reliable user defenses.

What these attacks do and why they work

Address‑poisoning: attackers insert a malicious address into a victim’s contact list, transaction history or token list so the wallet UI shows the attacker’s address where the user expects a known recipient. Wallets often truncate addresses (e.g., first 4 + last 4 characters), so visually similar malicious addresses can deceive users.

Clipboard replacement (clippers): malware watches the system clipboard and automatically replaces any detected crypto address with an attacker‑controlled address. ESET and Chainalysis document many clipper families distributed via trojanized apps, malicious downloads or browser extensions.

Approval and wallet phishing: phishing pages and malicious dApps can trick users into signing transactions that grant spending permissions or trigger transfers. Chainalysis calls approval‑phishing a major loss vector because signed approvals persist and allow repeated theft.

  • Truncation in wallet UIs increases the risk of confusing addresses.
  • Clippers operate on the endpoint and are often delivered by compromised apps or unsafe extensions.
  • Approval phishing abuses user signatures instead of immediate transfer prompts.

What the evidence shows

Law enforcement advisories (FBI) and on‑chain analysis (Chainalysis) report real cases of address‑poisoning and impersonation scams. These sources document growth in incidents and financial losses without relying on anecdote alone.

Vendor telemetry (ESET) captures clipboard‑interfering malware families and distribution channels, demonstrating that clipper behavior is active and broadly observed across platforms.

Academic work such as the EthClipper paper shows technical paths attackers can use to evade verification flows, reinforcing the need for on‑device checks and multi‑channel verification.

  • FBI: public advisories on token impersonation and address‑poisoning tactics.
  • Chainalysis: on‑chain case studies and crime‑report findings on address manipulation and approval phishing.
  • ESET: telemetry and technical descriptions of clipper malware families.

Practical, evidence‑backed checks to do before sending

Never trust only a pasted address. Paste the address into a plain text editor and compare the full string character‑for‑character to the source. When using a hardware wallet, always verify the full destination address shown on the device screen before approving.

Send a small test transaction for new recipients or large transfers (e.g., $1–$5 worth of the asset). Confirm on‑chain and via an out‑of‑band channel (phone, authenticated chat) that the intended recipient received it. Only then send the remainder.

  • Verify full address on a trusted device (hardware wallet display) — not just the host UI.
  • Use test transactions for new or large addresses to catch clipboard or list poisoning.
  • Prefer QR scans from secure sources to reduce copy‑paste errors, but still verify the address string.

Endpoint hygiene and approval management

Keep operating systems, browsers and anti‑malware up to date. Remove unused browser extensions and avoid installing apps from untrusted sources; ESET links many clippers to trojanized apps and malicious downloads.

For smart‑contract approvals, inspect approval scopes and limit them when possible. Use read‑only explorers and reputable revocation tools to check and revoke unnecessary allowances. If in doubt, revoke or set allowances to minimal amounts rather than blanket approvals.

  • Run reputable anti‑malware and update regularly.
  • Avoid untrusted browser extensions and APKs; prefer official app stores and signed packages.
  • Audit and revoke unnecessary token approvals; use on‑chain explorers for verification.

Practical checklist

  • Don’t rely solely on pasted addresses — compare the full string in a plain text editor.
  • If using a hardware wallet, confirm the entire recipient address on the device display before approving.
  • Send a small test transaction ($1–$5 equivalent) to new or large recipients and confirm receipt via an independent channel.
  • Keep OS, browser and anti‑malware updated and remove untrusted apps/extensions.
  • Inspect approval scopes for smart‑contract interactions and revoke unnecessary permissions.

Sources and further reading

Fact-checked: . External sources open in a new tab.

  1. FBI Warns of Cryptocurrency Token Impersonation ScamFBI
  2. Anatomy of an Address Poisoning ScamChainalysis
  3. H1 2023 Threat Report (clippers and cryptostealers)ESET
  4. EthClipper: Attacking Clipboard VerificationarXiv (academic paper)
← More guides