Bitcoin address poisoning is one of the quietest ways to lose funds, and it needs no malware, no hacked exchange and no stolen seed phrase. The attacker only needs you to copy the wrong string of characters once, at the exact moment you are paying attention to the amount and not to the address. The trick works because most wallet apps shorten addresses to something like bc1q...7f2k, and a lookalike address that shares those same four characters looks identical at a glance. This guide explains how the attack is built, how to test an address before you send, and what a Bitcoin ATM purchase actually changes about your exposure.
Table of Contents
- What Is Bitcoin Address Poisoning?
- How to Check a Bitcoin Address Before You Send
- Bitcoin ATM Purchases: Where the Risk Actually Sits
- Dusting Attacks vs Address Poisoning
- What to Do If You Sent Bitcoin to a Poisoned Address
- Frequently Asked Questions
What Is Bitcoin Address Poisoning?
Address poisoning is a copy-paste attack. The attacker watches public blockchain activity, picks a wallet that transacts regularly, and generates a new address whose first and last few characters match one of the addresses that wallet already deals with. Then the attacker pushes a tiny transfer from that lookalike address into the victim’s wallet, so the fake address is written into the wallet’s transaction history.
Nothing about that transfer asks for permission. It arrives, it sits in the history list, and it waits. Weeks later, when the owner opens the wallet to send again and copies what looks like the same recipient from the last transaction, the clipboard picks up the attacker’s address instead. The send goes through, the confirmations pile up, and the funds are gone. Chainalysis published a walkthrough of the attack showing how little infrastructure it takes: one script, a watch list of addresses and a wallet that funds a few thousand cheap transfers.
Why the trick works on careful people
Almost every Bitcoin interface compresses addresses for display. A phone wallet shows perhaps eight characters, an exchange withdrawal screen often shows six, and a block explorer shows a shortened version until you click it. Matching those visible characters is exactly what the attacker optimises for, so the check most people perform, glancing at the beginning and end, returns the answer the attacker wants.
The attack also exploits trust in the history list itself. A wallet’s history feels like a record of things that really happened, and in a narrow sense it is. What it does not tell you is who authored each entry. A transfer into your wallet can be sent by anyone, including someone who wants you to copy their address later.
How it differs between Bitcoin and other chains
On Ethereum and Tron, an attacker can register a fake token, emit a transfer event to your address, and pay a trivial fee for the privilege, so poisoning attempts cost almost nothing and victims see fake tokens they never received. Bitcoin has no token contract layer to abuse that way. A poisoning transfer on Bitcoin is a real transaction that moves real sats and pays a real network fee, which makes it more expensive but no less effective: a few cents is enough to put an address into your history for good.
How to Check a Bitcoin Address Before You Send
The defence is boring and it works: stop trusting the shortened form. Every check below costs a few seconds, and together they close the gap the attacker is trying to exploit.
Compare the whole string, not the ends
Read the address in four-character groups from left to right, including the characters in the middle that no interface displays. On a desktop, paste the expected address and the address you are about to use into a plain text editor on separate lines and compare them line by line. On mobile, expand the address if the wallet allows it, or open the receiving wallet and read from its own screen instead of from history.
The prefix alone tells you the format, not the owner. The Bitcoin Wiki’s list of address prefixes documents the common ones: bc1 for native SegWit, 1 for the oldest P2PKH format and 3 for P2SH. A checksum protects against a mistyped character, so a corrupted address will normally be rejected outright. A lookalike address is perfectly valid, which is why the checksum never helps here.
Use an address book instead of the clipboard
A saved contact removes the moment where a mistake happens. Most wallets let you store a recipient once and reuse it, and most exchanges let you whitelist a withdrawal address. Scan a QR code directly from the receiving wallet’s screen rather than pasting text, and never scan a QR code that arrived in a message or a comment.
Verify on the device that signs
If you use a hardware wallet, the address shown on the device’s own screen is the one that matters, because it comes from the keys rather than from the computer. Confirm it against the screen of the wallet receiving the funds, character by character, and reject the transaction if the two disagree. If you are still deciding what to hold your keys in, this is the single most useful feature to compare when you look at the best Bitcoin wallet options in Canada.
Bitcoin ATM Purchases: Where the Risk Actually Sits
A cash purchase at a Bitcoin ATM is a push transaction: you insert cash, you enter a receiving address, and the machine sends bitcoin to that address. There is no account to log into and no stored balance to drain later, so the poisoning risk in an ATM purchase is concentrated in one narrow moment, the address you enter at the machine.
The practical habit is to open your wallet at the machine, tap receive, and scan the QR code from that screen. If you must type or paste, paste from a saved contact rather than from a list of past transactions, then read the middle characters on the ATM’s confirmation screen before you feed the cash in. Our step-by-step guide to using a Bitcoin ATM covers the rest of the flow, including what the machine asks for and how long the transfer usually takes.
One small note on screenshots: a photo of your receiving QR code sitting in a camera roll is not a security control, and it is easy to send the wrong one from a gallery that has accumulated months of images. Show the code on the screen, scan it live, and close the wallet when you are done.
Dusting Attacks vs Address Poisoning
These two get confused because both arrive as an unexpected tiny deposit, but the goals are different. A dusting attack sends minuscule amounts to thousands of addresses to map which ones belong to the same owner: if several dusted addresses later move together in one transaction, the analyst learns they share a wallet. Theft is not the immediate objective, and receiving dust does not put your coins at risk on its own.
Address poisoning is targeted and personal. The payoff is you copying the attacker’s address, so the transfer is engineered to look like it belongs to someone you already pay. Academic work on the technique, including a USENIX Security 2025 paper on blockchain address poisoning, measures how the lookalike matching is chosen and how often it converts. The common thread is that neither attack breaks cryptography. Both work on human attention, which is also why the broader catalogue of crypto scams in Canada keeps returning to the same advice about slowing down.
What to Do If You Sent Bitcoin to a Poisoned Address
Be clear-eyed about the mechanics: a confirmed Bitcoin transaction cannot be reversed by you, by a wallet vendor, by an exchange or by Bitcoiniacs. Only the holder of the destination’s private keys can move those coins, and in a poisoning attack that person is the attacker. What you do next is about documentation and about not making the loss larger.
- Stop sending. Do not send a “test” amount to the same address hoping to trace it.
- Save the evidence. Record the transaction ID, the destination address, the amount, the timestamp and screenshots of the wallet history. This is what investigators and any platform review will ask for.
- Report it. File a report with the Canadian Anti-Fraud Centre and with your local police service. Volume matters: patterns across reports are what trigger wider investigations.
- Tell the destination platform, if there is one. If the address belongs to a custodial exchange, its compliance team may be able to freeze the deposit before it is withdrawn, though there is no guarantee and no obligation to do so.
- Ignore recovery offers. Anyone who messages you promising to retrieve the funds for an upfront fee is running the second stage of the scam. No legitimate service can reverse a confirmed Bitcoin transaction.
If you are still working out where your transaction actually went, this breakdown of what happens when you send Bitcoin to the wrong address separates the recoverable cases from the permanent ones.
The prevention list is short enough to memorise: full-address comparison, saved contacts, QR scans from the receiving wallet, hardware-wallet screen checks, and a fresh receiving address for each payment so your history has less worth poisoning. None of it depends on being technical. All of it depends on refusing to trust a shortened string.
Frequently Asked Questions
Is checking the first and last characters of an address enough?
No, and that is the specific weakness address poisoning is designed around. The attacker generates addresses that match the visible start and end of the address you already use, so those characters will agree while everything in the middle does not. Compare the full string, or better, use a saved contact so there is nothing to compare in the moment.
How does an attacker get a transfer into my history if they never really sent me anything?
On Ethereum-style chains they emit a fake token transfer event, which costs almost nothing and puts their address in your history without any real value moving. On Bitcoin there is no such shortcut, so the attacker sends a genuinely small amount of bitcoin from the lookalike address. Either way the entry is real in your history and fake in its meaning: it was not sent by the person you think it was.
I received a random tiny Bitcoin deposit. Is that a dusting attack?
Possibly, and it may also be address poisoning, since the mechanics overlap. A surprise deposit worth a few cents from an address you do not recognise is a signal to be careful rather than a reason to panic. Do not interact with that address, do not copy it, and do not consolidate it with your main funds if you care about privacy. Your keys and coins remain yours.
Can I get bitcoin back after copying a poisoned address?
In practice, no. A confirmed Bitcoin transaction is final, and the only person who can return the coins is whoever controls the destination keys. Report the loss to the Canadian Anti-Fraud Centre and police, notify the destination platform if the address is custodial, and treat any paid recovery service as a scam. Recovery stories that circulate online almost always involve an exchange freeze that happened before the attacker withdrew, not a reversal of the transaction.
Address poisoning is a reminder that most bitcoin losses are not cryptographic failures. They are small procedural ones, repeated at scale. A five-second check of the full address, and a wallet that remembers recipients for you, is enough to make the entire technique pointless against you.
