
If you’ve ever copied a crypto address from your recent transactions and hit send, this scam is aimed at you. Address poisoning is a simple trick: scammers clutter your wallet history with lookalike addresses so you copy the wrong one. It’s been flagged by blockchain security firms and researchers as a growing on-chain scam across crypto wallets. A university study revealed over 270 million attack attempts on Ethereum and BSC, resulting in 6,600 incidents that caused at least $83.8 million in losses, making it one of the largest phishing schemes in crypto.
In this article, we’ll explain how the scam works, what to do if you’ve been targeted, and steps to strengthen everyday practices.
Address poisoning is a social-engineering scam that plays out on-chain. The attacker doesn’t hack your wallet. They don’t need your private key. Instead, they pollute your activity feed with a wallet address that looks like the one you usually send to. When you make your next transfer, you copy the spoofed address from your history, and your cryptocurrencies go to the attacker.
This works because many people copy recent “to” addresses from their wallet UI. Wallets often shorten addresses, for example, 0x12ab…89cd. Attackers exploit that. They create vanity addresses that share the same starting and ending characters as your real recipient. At a glance, they look right.
Most incidents occur on EVM-compatible chains, such as Ethereum, BNB Chain, and Polygon. However, the idea can be applied anywhere, as addresses are long and UIs tend to shorten or sort them in predictable ways. Even chains with different address formats can be targeted as long as the wallet interface encourages copying from history.
Checksums can help, but they don’t fix human habits.
A checksum catches typos. It doesn’t protect against copying a valid, lookalike address. And if you only check the first four and last four characters, you can still be fooled. Some attackers even tune their vanity addresses to pass casual checksum cues that users think “feel” right.
Address poisoning variations exist.
Various scams use token approvals with deceptive contracts, hoping you’ll sign permissions that give them spending rights.
Attackers use several tricks to make poisoned addresses blend in:
Each tactic turns shortcuts in how we scan addresses into an opening for crypto losses.
Spotting address poisoning often comes down to noticing what feels slightly off in your wallet activity. Scammers count on quick glances and familiar patterns, so the warning signs usually hide in plain sight. A closer look at your transaction feed, token list, and saved contacts can reveal subtle red flags before a mis-send happens.
Protecting your wallet from address poisoning means building habits that make copy-paste traps ineffective. Small checks and structured workflows reduce risk across personal and team use. Key practices include:
If you spot signs of address poisoning, act quickly and methodically:
People make the final click when sending funds, but the design of tools strongly shapes that decision. Wallets can lower risks by flagging zero-value spam, highlighting verified contacts, and avoiding truncation patterns that hide key details. Simple prompts such as “This address is not in your contacts” or “This address is unverified” can slow a rushed transfer.
Explorers can add warnings for known poisoning clusters and adjust how addresses are copied, making the action more deliberate. Standards groups can support safer practices through richer checksums, consistent truncation rules, and auditable signed address books. Even small design changes, applied widely, can improve protection across millions of transactions.
Recovering funds after an address poisoning scam is difficult. While transactions can be traced on-chain, attackers usually move assets quickly through mixers, bridges, and exchanges. The outcome often depends on jurisdiction, since some exchanges can freeze funds if they are contacted in time and local laws allow it.
For larger losses, it helps to bring in legal counsel and trusted investigators. Analytics providers can identify linked addresses and transaction patterns, though their labeling has limits and may raise privacy questions. The best step is to collect evidence early, keep records well organized, and preserve a clear trail of how data was handled.
Clear policies on address changes, approvals, and incident response add another layer of protection. They also demonstrate to auditors, insurers, and clients that safeguards were in place and that the team acted responsibly.
Address poisoning works because it takes advantage of habits, not code. People often move quickly, reuse the last transaction, and trust what looks familiar. Scammers count on this.
The defenses are simple, but they need to be applied every time. Avoid copying from history. Save and reuse verified contacts. Double-check major transfers through a separate channel. Where possible, use hardware wallets, transaction simulations, filters, and clearer wallet interfaces.
Teams should treat this as a standard process, not a personal choice. Write it down, train on it, and review it after any incident. Attackers will continue to test habits and interfaces, but consistent checks make the scam far less effective. Slow is steady. Steady is safe.