What this tutorial says in five lines
- Sending to a wrong address is irreversible — no support line can reverse it.
- Clipboard hijackers silently swap the address you copied.
- Address poisoning plants a lookalike address in your history to catch a lazy copy.
- Always verify the first 6 and last 6 characters, on the destination device.
- Send a small test amount first for any transfer you would regret losing.
Why this matters
This is the cheapest failure to prevent and the most expensive to make. A crypto transfer is final in seconds and no one — not the exchange, not the network, not law enforcement — can reverse it. Almost every "I sent it to the wrong address" story involves one of three mechanical failures, and all three are defeated by the same 60-second routine.
The three ways an address goes wrong
It is rarely a simple typo. The failure modes are mechanical, which is why a mechanical check prevents them.
- 01Clipboard hijacking: malware watching your clipboard and substituting a lookalike address between copy and paste.
- 02Address poisoning: an attacker sends you a dust transaction from an address that mimics one you use, hoping you copy theirs out of your history later.
- 03Manual truncation: you copy a shortened address from a message, or a chat app wraps it, and part of the string is silently lost.
A clipboard hijacker does not need to be clever. It only needs you to paste without comparing. That is the entire attack.
The 60-second verification protocol
Run all six steps for any transfer you would regret losing. Together they take about a minute.
| Step | Action | What it catches | Time |
|---|---|---|---|
| 1 | Get the address from the destination device or a signed message, not from a chat paste | Chat-app wrapping, truncated copies | 15s |
| 2 | Compare the first 6 and last 6 characters character-by-character | Clipboard hijackers, lookalike addresses | 15s |
| 3 | Check the total length is exact (42 for Ethereum, 32–44 for Solana) | Truncation, wrong-chain pastes | 5s |
| 4 | Confirm the chain matches — an ETH address sent to a Solana address is lost | Cross-chain mistakes | 5s |
| 5 | Send a small test amount first, confirm it arrives, then send the remainder | Everything above, before it is expensive | 2 min |
| 6 | Keep the transaction hash of the final send | Nothing — this is for your evidence if it goes wrong | 10s |
Address poisoning, visualised
Address poisoning is the technique most people have never heard of, and it is why "I copied it from my own history" is not a safe method. The attacker generates thousands of addresses whose leading and trailing characters match addresses you transact with, then sends you a zero-value transaction from each. They now appear in your history, looking familiar.
Because most wallets display shortened addresses, the poisoned address looks identical to your real one. The next time you copy from history rather than from a verified source, you send to the attacker.
How easy a lookalike address is to miss when you only glance
Similarity a casual glance perceives, by how many characters you compare
Reading: The drop between the second and fourth row is the whole lesson. Comparing the tail as well as the head is what collapses the similarity a hijacked address can achieve.
What a safe send looks like, end to end
A worked example, using an exchange withdrawal to a self-custody wallet.
- 01Open the receiving wallet on the receiving device and copy the address directly from it — never from a message, a note, or your history.
- 02In the sending app, paste it and then read the first six and last six characters back against the receiving screen. Do this out loud if you are tired.
- 03Check the network selection. A token sent on the wrong network is usually unrecoverable, and this is the most common self-inflicted loss.
- 04Send the minimum viable amount. Wait for confirmations. Verify the balance actually changed on the destination.
- 05Only then send the remainder, verifying the address again — because the clipboard is re-read on every paste.
The test transfer is not bureaucracy. It is the only check that tests the whole route rather than the address alone.
If you have already sent to the wrong address
The honest position first: a transfer to a wrong but valid address cannot be reversed. What changes the outcome is whether the destination belongs to a known party.
- 01If the destination is a known exchange deposit address, contact that exchange immediately with the transaction hash — sometimes internal recovery is possible before the funds are credited to a stranger.
- 02If the destination is self-custody and unknown, record the hash and treat it as evidence rather than as a recoverable mistake.
- 03If a clipboard hijacker was involved, assume your device is compromised: move remaining funds from a clean device before doing anything else.
- 04Check whether the destination address has been reported before. A reported address strengthens a complaint considerably.
The visual summary
Everything above, reduced to the four stages that matter for this topic. If you only look at one thing on this page, look at this.
Where this fits in the pattern
Before contact
Nothing has happened yet. This is when every tutorial here is most useful and costs you nothing but reading.
During the approach
The script is running. The verification tests in this tutorial are designed to be run here, neutrally, without confrontation.
At the money request
The decisive moment. Any request for funds, fees, taxes or unlock deposits is the end of the script, not a stage of it.
After a loss
Prevention is over; evidence work begins. Preserve, report, and never pay a second fee to recover the first.
Common questions
Vet an address before you trust it again
The tracer reads the public ledger for any address — balance, activity window, hop pattern and a transparent risk signal you can keep as evidence.
Primary sources and further reading
- FTC — Scams That Follow a Scam consumer.ftc.gov
- FBI — Common Scams and Crimes www.fbi.gov
- CISA — Cybersecurity Best Practices www.cisa.gov
External links open in a new tab so you can verify the underlying material yourself. TrueMoneyTalk is not affiliated with these organisations.
Prevention only works if it reaches people before the contact does.
Disclaimer: this tutorial is general information, not legal, financial or recovery advice, and is not a substitute for advice from a licensed professional in your jurisdiction. Individual outcomes vary and are never guaranteed.