# Bitcoin Address Poisoning: Look-Alike Addresses

Source: https://www.btcvanity.io/blog/bitcoin-address-poisoning

Published: 2026-11-06

Updated: 2026-11-09

![A familiar fragment can mislead. Imitation: A look-alike can share visible characters; Truncation: Short displays hide most of the destination; Confirmation: Verify every character against a trusted record.](https://www.btcvanity.io/images/blog/bitcoin-address-poisoning-diagram-v2.webp)

A familiar fragment can mislead. Imitation: A look-alike can share visible characters; Truncation: Short displays hide most of the destination; Confirmation: Verify every character against a trusted record.

[Full-size diagram (SVG)](https://www.btcvanity.io/images/blog/bitcoin-address-poisoning-diagram-v2.svg)

[Diagram download (PNG)](https://www.btcvanity.io/images/blog/bitcoin-address-poisoning-diagram-v2.png)

An attacker can create a different address sharing a familiar prefix or suffix. Those matching characters are not evidence of ownership.

## Why checking only the ends can fail

Vanity search demonstrates that a recognizable fragment is not unique evidence of a person or organization. A look-alike destination can share the characters your wallet happens to display while differing in the hidden middle.

A checksum checks the integrity of an encoded string. It does not know which recipient you intended. A malicious destination can be fully valid.


## Compare against an independent reference

When preparing a payment, use receiving instructions obtained through a channel you already trust. Expand shortened addresses and compare the complete destination. If a copied value changes, or an invoice unexpectedly changes networks, resolve that discrepancy before proceeding.

- Do not choose a recipient solely from a recent-activity list.
- Inspect the address actually shown in the final wallet confirmation.
- Treat an unexpected change to established payment instructions as a reason to reconfirm them.

## Publish enough information to avoid ambiguity

Display the network and complete address alongside a QR code. A memorable prefix can aid recognition, but your payment instructions should not tell users to validate only that fragment.

Read [how names and vanity addresses differ](https://www.btcvanity.io/blog/bitcoin-vanity-address-vs-payment-name) if you are designing a receiving page. If an explorer result is confusing, use [the address and transaction ID guide](https://www.btcvanity.io/blog/bitcoin-address-vs-transaction-id) to identify the type of record you are viewing.


## Explore the related mechanism

- [Bitcoin Vanity Address vs Payment Name](https://www.btcvanity.io/blog/bitcoin-vanity-address-vs-payment-name) — A vanity pattern changes the address you receive; a payment name resolves or points to a destination. They are separate layers.
- [Bitcoin Address or Transaction ID: How to Tell Them Apart](https://www.btcvanity.io/blog/bitcoin-address-vs-transaction-id) — A receiving address and a transaction identifier describe different things. The result of this generator is an address and its private key, not a transaction.
- [Open the complete workflow guide](https://www.btcvanity.io/guide) to place these checks in order.
- [Open the address generator](https://www.btcvanity.io/) when you have chosen a compatible format and pattern.

## Sources

- [Bitcoin developer transactions guide](https://developer.bitcoin.org/devguide/transactions.html)



Editorial method: https://www.btcvanity.io/about#publication-method