Address Poisoning: Verify the Destination Before Sending Crypto
A familiar-looking address can still be wrong
You open a wallet's recent activity, recognize the beginning and end of an address, and copy it for another transfer. Attackers exploit that shortcut. A misleading history entry can make their destination look familiar.
The danger is especially relevant when moving assets between an exchange account and a personal wallet. Recognizing a shortened address is not the same as verifying the recipient. The destination, network and asset each need an independent check.
How transaction history becomes misleading
MetaMask's address-poisoning guide describes attackers using lookalike addresses and tiny or zero-value transfers to contaminate activity history. The attacker hopes a later copy-and-paste sends valuable assets to the wrong destination.
Receiving an unsolicited history entry does not, by itself, prove that someone has your private key. The main trap in this scenario is the address you choose for a subsequent transfer. Do not respond by connecting to a recovery website or signing an unfamiliar transaction.
Start from a trusted receiving source
For an exchange deposit, obtain the current receiving details from the authenticated deposit page for the exact asset and supported network. For a personal wallet, use its receiving screen and independently verify any address supplied by another person.
Treat a block explorer or activity list as evidence about past transactions, not an address book. An entry appearing near a genuine transfer does not authenticate its counterparty. A remembered label is useful only when the underlying destination was checked before it was saved.
Verify beyond the visible prefix and suffix
Ledger's technical explanation discusses multiple poisoning techniques, including misleading token-transfer records. A short history preview can therefore hide differences or create a false impression about who initiated an entry.
Compare the complete destination against the trusted source, including the middle characters. Where a hardware wallet provides a trusted display, verify the details there as well. Keep the asset, network and any required memo or tag in the same checking routine; matching an address alone does not resolve every transfer risk.
Build a repeatable transfer routine
Prepare the recipient details before opening recent activity. Paste from the trusted source, compare the full destination, check the network and review the final confirmation screen. If anything changes or a warning appears, stop and resolve the discrepancy.
A small test transfer may help verify the receiving process when the destination supports the amount and network. It is not a guarantee: confirm receipt at the intended account and repeat the destination check before sending more. Never copy the address for the second transfer from an unverified new history entry.
If you suspect an incorrect transfer
Stop additional transfers and preserve the transaction hash, network, destination and time. Use the platform's official support entry, such as OrangeX.com support, rather than a contact from an unsolicited message.
Do not assume that a confirmed blockchain transfer can be reversed or that a recovery service can retrieve it. Do not share a seed phrase, private key or authentication code to investigate a history entry. The most effective checkpoint is before approval: use a trusted destination source and verify the full details each time.
