Binance Warns Lookalike Wallet Addresses Can Turn Transaction History Into a Scam Trap

Summary

• Binance warns that scammers can plant lookalike wallet addresses in transaction histories without accessing private keys or compromising user wallets directly.
• Attackers imitate familiar addresses and send small transfers, hoping users copy fraudulent entries when making larger payments to trusted recipients.
• Checking complete addresses, using verified contacts, and making small test transfers can help prevent costly mistakes during irreversible cryptocurrency payments.

Binance has warned crypto users that scammers can plant lookalike wallet addresses in transaction histories to misdirect future payments. According to the exchange, this address poisoning scheme depends on users copying the wrong destination during a transfer.

An attacker begins by finding a wallet that has sent funds to the same address before. Public blockchain records allow the attacker to see those transactions and identify a recipient the wallet owner may use again. The attacker then generates another address with similar opening and closing characters.

Next, the scammer sends a zero-value or small transaction from the lookalike address to the target wallet. That transaction puts the fraudulent address in the wallet’s history, where it may appear alongside genuine activity. Binance warns that the attacker needs neither the user’s private keys nor access to the wallet.

Long addresses make the deception harder to spot, particularly when a wallet displays only their first and final characters. Two addresses can look alike in that shortened view while containing different characters throughout the middle. Consequently, checking only the visible ends may give a sender false confidence.

Also Read: SEC Says Crypto Buybacks and Network Upgrades Do Not Automatically Make Tokens Securities

Why Copying an Address From Wallet History Creates Risk

The scam reaches its decisive point when the wallet owner prepares another payment to a familiar recipient. Rather than retrieving a verified address, the user may copy a similar one from the transaction history. If the copied entry belongs to the attacker, the funds go to the attacker’s wallet.

A small incoming transaction does not prove that its sender owns an address the user trusts. Nevertheless, its appearance in recent activity can make the entry seem relevant during a hurried transfer. The scam exploits that assumption, so even a secure wallet cannot prevent every mistake its owner makes when choosing a destination.

Binance advises users to verify the entire address before sending funds and to save trusted recipients in an address book. For larger payments, the exchange also recommends a small test transfer before sending the remaining amount. These steps give the sender another chance to identify an incorrect destination before committing more funds.

The warning applies wherever users rely on shortened addresses or copy destinations from recent wallet activity. Ethereum and BNB Smart Chain are among the networks where attackers have used this approach. Although the scam starts with a minor transaction, an incorrect outgoing transfer can cause a much larger loss.

A transaction history shows where activity occurred, but it does not verify which addresses deserve a user’s trust. Checking the complete destination remains the critical step before approving a crypto payment.

Also Read: Nik Bougalis Returns to XRP Ledger Code With Proposal to Rework Core Data Types