> ## Content Index
> Fetch the complete content index at: https://www.cryptowithblock.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Address Poisoning and Clipboard Attacks
- URL: https://www.cryptowithblock.com/address-poisoning-and-clipboard-attacks/
- Published: 2026-11-01T10:03:15.000Z
- Updated: 2026-11-15T15:03:22.000Z
- Description: Address poisoning and clipboard attacks can send crypto to a thief even when the address looks right. Learn the four-rule checking routine that works against both.
- Author: Crypto With Block
- Tags: Protect Your Crypto, #lesson

## When the address isn't yours

Hi, I'm Block. You copy an address. You paste it. You check the first few characters and the last few, and they match. You hit send, and the money goes straight to a thief. Nobody hacked your wallet. In this lesson: how that happens, why a test transaction won't save you, and a checking routine that will.

## No undo button

Last time we cleaned up old permissions. This lesson is about something even simpler: the address itself. With a bank, a wrong transfer can sometimes be stopped or reversed. With crypto, once a transaction is confirmed, there's no bank to call and no undo button. So the address is the last line of defense.

> The address is your last line of defense.

Here's the weak spot. Crypto addresses are long strings of letters and numbers, often dozens of characters long. Nobody reads all of that, so wallets and apps usually shorten it, showing just the first few and last few characters. And that's exactly what most people check.

> Most people only check the ends.

Attackers take advantage of that. They use computers to generate huge numbers of new wallets until they find one whose address starts and ends with the same characters as an address you use. Researchers found most attack groups matching around fourteen characters, and one matching twenty. The ends match. Only the middle is different.

> The ends match. Only the middle is different.

Then they plant it. Attackers watch the blockchain. Right after you send to someone you pay often, they send you a tiny amount, a zero-value transfer, or a fake token, from their look-alike address. Now their address is sitting in your transaction history, right next to the real one.

> Their address now sits in your history.

Here's what your history might look like. Your real payment to your exchange deposit address. Then a strange zero-value transfer a few minutes later. Look closely. The start and end are the same. The middle is not.

Next time you need that address, you open your history and copy it from there, like you've done a dozen times. Except this time you copy the newest entry. Theirs. Your transaction history is a record, not an address book. Anyone can write to it.

> Anyone can write to your history.

How common is this? Researchers who studied two years of activity on two big networks counted about two hundred seventy million poisoning attempts aimed at about seventeen million people. Only a few thousand worked, but those cost victims at least eighty-three million dollars.

> A few thousand worked. They cost $83M+.

You might think this only targets whales. It doesn't. The whole thing is automated, so it costs attackers very little to aim at everyone who makes a transfer. That's how the targets add up to millions of ordinary people. If you've ever sent tokens on one of these networks, assume you're on the list.

> Sent tokens before? Assume you're on the list.

And some single mistakes are huge. In one case, a holder sent eleven hundred fifty-five wrapped bitcoin, about sixty-eight million dollars at the time, to a look-alike that matched the first six and last six characters. In a rare twist, the attacker sent it back after negotiations. Almost nobody gets that ending.

> Getting it back is rare. Don't plan on it.

Another case shows why the usual safety advice isn't enough. A holder did the careful thing and sent a small test transaction to the right address first. Minutes later, they copied the address from their history and sent the rest. Nearly fifty million dollars went to the look-alike. The test worked. The second copy didn't.

> The test worked. The second copy didn't.

## A test can be a signal

Here's the uncomfortable part. A test transaction is public. It tells attackers exactly who you're about to pay, and roughly when. That's their cue to plant a look-alike. A test only protects you if you copy the address from the original source again, never from your history.

> After a test, copy from the source again.

## The clipboard swap

Now the second attack, and it's sneakier. With address poisoning, you copy the wrong address. With a clipboard attack, you copy the right address, and something on your computer swaps it before you paste. You did everything right, and it still goes wrong.

> Right copy, wrong paste.

The malware is called a clipper. It sits quietly in the background and watches everything you copy. When it sees something shaped like a crypto address, it replaces it with the attacker's address. You paste, glance at it, and send. It's an old trick. Banking malware did the same thing with account numbers years ago.

> An old banking trick, aimed at crypto.

How does it get on your computer? One campaign hid a clipper inside fake installers for a popular privacy browser, posted on unofficial download sites. Security researchers counted more than fifteen thousand attacks in over fifty countries, and at least four hundred thousand dollars stolen. The real browser was free. The fake one was expensive.

> Download from the official site, only.

Another clipper that Microsoft analyzed spreads through USB drives, and checks what you've copied about twice every second. Besides swapping addresses, it also looks for recovery phrases. That's one more reason for the clean money device from two lessons ago, with no random downloads and no shared drives.

> A clean device keeps clippers out.

## A routine, not a better eye

So how do you protect yourself from both? Not with a better eye. With a routine that doesn't depend on spotting a fake. Here are the rules I'd want every holder to follow.

Rule one: never copy an address from your transaction history. Get it from the source every time. If you're sending to your own exchange account, open the exchange and copy its deposit address. If you're paying someone, get it from them directly, through a channel you trust. History is for reading, not copying.

> History is for reading, not copying.

Rule two: save trusted addresses once. When you've verified an address carefully, add it to your wallet's address book with a clear name, like My exchange or Savings. Many exchanges also let you lock withdrawals to a list of approved addresses. Verify once, carefully. Then pick from the saved list every time.

> Verify once. Pick from the saved list.

## Rule 3: check the middle

Rule three: check the middle. Attackers spend their computing power matching the start and the end, because that's what people look at. The middle is the hardest part to fake. Compare the whole address in chunks of four or five characters, and pay the most attention to the middle.

> The middle is the hardest part to fake.

It's even harder on a phone. Small screens shorten addresses even more, so you often see just a handful of characters on each end. The researchers called out exactly this: the less of the address you can see, the easier a look-alike is to miss. If you must send from a phone, open the full address and read the middle.

> On a phone, open the full address.

Rule four: confirm on a second screen. If you use a hardware wallet, it shows the destination address on its own little screen before you approve. Malware on your computer can't change what that screen shows. Read the address there, slowly, in chunks, and compare it to the source.

> Trust the device screen, not the computer screen.

Test transactions are still worth doing for big amounts, as long as you do them the right way. Send the test, ask the recipient to confirm they got it, then copy the address again from the source, not from your history. And re-check the middle before the big send.

> After the test, go back to the source.

And treat unexpected tiny transfers as a warning sign. A zero-value transfer, a few cents of something, or a token you never bought, from an address that looks familiar. That's not a gift and it's not a glitch. Someone is setting a trap in your history, so be extra careful with your next send.

> Unexpected dust means a trap is set.

For large amounts, add one more step. Confirm the address through a second channel. If you're paying a person or a business, read the middle characters back to them over a call you started, using a number you already had. It takes a minute. Compared with a mistake you can't undo, that's nothing.

> One minute beats a mistake you can't undo.

And if it does happen, move fast but carefully. Write down the transaction details, report it to the police and, in the U.S., to the FBI's internet crime center. If funds went to an exchange, contact that exchange through its official app. Then ignore anyone who contacts you offering to get it back. We'll cover that in a later lesson.

> Anyone offering to get it back is a second threat.

## Two attacks, one routine

So keep the two attacks straight. Poisoning lives on the blockchain, in your history, and it waits for you to copy the wrong line. A clipper lives on your device, and it changes what you paste. One routine handles both: copy from the source, check the middle, confirm on a second screen.

> One routine handles both.

The good news is that both attacks rely on the same habit: trusting a quick glance. Once your routine stops depending on your eyes catching a fake, poisoning and clipboard swaps lose most of their power. Slow and boring wins again.

> Slow and boring wins again.

## Check the address

Here's the whole lesson in four lines. Never copy an address from your history. Save trusted addresses once and pick from the list. Check the middle, not just the ends. And confirm big sends on a hardware wallet screen or a second channel. Your eyes can be fooled. Your routine can't.

> Your eyes can be fooled. Your routine can't.

## Sources

- [Address poisoning research (Tsuchiya et al., USENIX Security 2025): about 270 million attack attempts against about 17 million victims over two years on Ethereum and BNB Smart Chain; 6,633 incidents caused losses of at least $83.8 million](https://arxiv.org/abs/2501.16681v1?ref=cryptowithblock.com)
- [Same paper: attack types are tiny transfers, zero-value transfers and counterfeit-token transfers; attackers brute-force keys to match an address's first and last characters (most groups about 14 matching digits, one group 20); poisoning transfers follow shortly after the victim's real transfer; wallets have shown only the first and last 3-5 characters](https://arxiv.org/html/2501.16681v1?ref=cryptowithblock.com)
- [May 2024: a victim sent 1,155 WBTC (about $68 million) to a look-alike address matching the first and last six characters of the intended address](https://www.coindesk.com/business/2024/05/03/exploiter-steals-68m-worth-of-crypto-through-address-poisoning?ref=cryptowithblock.com)
- [The attacker in the $68 million WBTC case returned the funds (about 22,960 ETH) after negotiations in May 2024](https://cointelegraph.com/news/wbtc-address-poisoner-all-funds-negotiations?ref=cryptowithblock.com)
- [December 2025: a victim sent a small test transaction to the correct address, then minutes later sent 49,999,950 USDT (nearly $50 million) to a poisoned look-alike copied from transaction history; first 3 and last 4 characters matched](https://cointelegraph.com/news/address-poisoning-copy-paste-mistake-50m-usdt-loss?rand=50490&ref=cryptowithblock.com)
- [Kaspersky: clipper malware monitors the clipboard and swaps copied crypto addresses for the attacker's; spread through trojanized Tor Browser installers; more than 15,000 attacks in at least 52 countries; at least $400,000 stolen; advice to download only from official sources](https://www.kaspersky.com/about/press-releases/2023%5Fnew-clipper-malware-steals-us400000-in-cryptocurrencies-via-fake-tor-browser?ref=cryptowithblock.com)
- [Microsoft described a crypto clipper spreading via USB drives that checks the clipboard about every 500 milliseconds, swaps wallet addresses and grabs recovery phrases](https://microsoft.com/en-us/security/blog/2026/06/17/crypto-clipper-uses-tor-worm-like-propagation-for-persistence-control?ref=cryptowithblock.com)
- [Secondary report of the Microsoft clipper analysis (500 ms clipboard checks, address replacement, seed phrase theft, USB spread)](https://thenextweb.com/news/microsoft-crypto-clipper-usb-malware-tor-cryptocurrency-theft?ref=cryptowithblock.com)
- [Example of an exchange withdrawal allowlist: when enabled, crypto can only be withdrawn to addresses saved in the address book](https://help.coinbase.com/en/international-exchange/manage-account/address-book-and-crypto-withdrawal-address-allowlisting?ref=cryptowithblock.com)
- [FBI: victims can report to the Internet Crime Complaint Center (IC3) at ic3.gov](https://www.ic3.gov/PSA/2022/PSA221221?ref=cryptowithblock.com)

*Education only. Not financial advice.*