Skip to main content
₿SatSaver

How to Verify a Bitcoin Address Before You Send

Malware can swap a pasted address. Here's how to check the destination so your coins land where you mean.

6 min read · Reviewed September 12, 2026

A Bitcoin address is a long string of random-looking characters, and almost nobody reads the whole thing before hitting send. That habit is exactly what attackers count on. Because a confirmed Bitcoin transaction is irreversible — there is no bank to call and no chargeback — the thirty seconds you spend checking the destination is the cheapest insurance you will ever buy. Here is how to verify an address so your coins land where you actually mean them to.

The core rule

No one can undo a Bitcoin send. If the address is wrong — whether you fat-fingered it or malware swapped it — the coins are gone. Verify the destination before you broadcast, not after.

Why verifying matters

The biggest threat is not a typo you make yourself — it is clipboard-hijacking malware. This is a small, quiet program that watches your clipboard, notices when you copy something that looks like a Bitcoin address, and silently replaces it with an address the attacker controls. You copy the right address from your exchange or a friend's message, paste it into your wallet, and the pasted value is now the thief's. Nothing looks broken. The transaction sends normally. The money just goes to the wrong person.

This kind of malware is common precisely because it works: people trust copy-and-paste and rarely double-check the result. Combine that with irreversibility and a single unverified paste can cost you everything you sent.

How to actually check an address

Glancing at an address is not verifying it. A swapped address usually starts with the same prefix (like bc1) and is roughly the same length, so a quick look tells you nothing. Do this instead:

  • →Compare both ends, character by character. Read the first five or six characters and the last five or six, and match them against the source. Malware-swapped addresses often share a prefix but differ in the middle and end.
  • →Ideally, verify the whole string. For anything meaningful, check the entire address, not just the ends. Some wallets and block explorers let you paste an address to confirm it is valid and see its history, which is a useful sanity check.
  • →Confirm the address is even valid. Bitcoin addresses have a built-in checksum, so most wallets reject a mistyped one outright. That protects you from random typos — but not from a malware swap, because the attacker's address is itself valid.

Prefer scanning or a saved contact over pasting

The safest move is to avoid the clipboard entirely. Copy-paste is where the swap happens, so cut it out of the loop when you can:

  • →Scan a QR code.When you scan the recipient's QR directly with your wallet's camera, the address never touches your clipboard, so clipboard malware has nothing to hijack. Still glance at the decoded address before sending.
  • →Use an address book or saved contact. If you send to the same person or your own wallet repeatedly, save the address once — after verifying it carefully — and reuse the saved entry. A one-time careful check protects every future send.

On a hardware wallet, verify on the device

If you use a hardware wallet, its most important feature is the little screen on the device itself. When you send, the wallet displays the destination address on its own screen for you to confirm before it signs.

This matters because the hardware wallet's screen is trusted even if your computer is not. Malware can alter what you see in a browser or app, but it cannot change what the device shows. Always read the address on the device screen and match it against the true destination — do not just confirm because the app told you to. This single habit defeats clipboard swaps entirely.

Send a small test amount first

For a large transfer, do not send the whole thing at once. Send a small test amountfirst — enough to be worth confirming, small enough that a mistake would not hurt. Wait for it to confirm, have the recipient verify it arrived, and only then send the rest.

A test send costs you one extra transaction fee and a little time, but it catches a wrong address, an incompatible address type, or a misconfigured wallet before the full amount is on the line. Check a live rate first so the test itself is not overpriced — see how Bitcoin fees work if sat/vByte is new to you.

Watch for address poisoning

A newer trick is address poisoning. A scammer sends you a tiny amount of Bitcoin (“dust”) from an address deliberately crafted to look like one you use often — same first characters, same last characters. It shows up in your transaction history. Later, when you go to send and grab an address from that history, you copy the scammer's look-alike instead of the real one, and your coins go to them.

The defense is simple: never pull a send-to address from your transaction history.Always get the destination from the real source — the recipient's message, their QR code, your own verified address book, or the wallet you are sending to. Treat unexpected dust as a warning sign, not a convenience.

One habit that covers all of this

Get the address from the true source, remove copy-paste from the loop when you can, and confirm both ends of the string — on your hardware wallet's own screen if you have one. For anything large, test with a small amount first.

The bottom line

Verifying a Bitcoin address is not paranoia — it is the one check that cannot be undone later. Compare the whole string (or at least both ends) against the real source, prefer QR scans and saved contacts over pasting, confirm the address on your hardware wallet's screen, and send a small test before any large transfer. Do that and clipboard malware and address poisoning both come up empty.

Once you have confirmed the destination, make sure you are not overpaying to reach it. Check the live rate with the SatSaver tracker, and if you are weighing a cheaper, slower send, see whether it is safe to send Bitcoin with a low fee and what to do if a transaction gets stuck.

Recommended

Recommended gear & reading

Tools and books that pair well with this guide.

ⓘ As an Amazon Associate, SatSaver earns from qualifying purchases — at no extra cost to you. Commissions help keep the core tools free. Full disclosure

See the live answer right now

SatSaver reads the live mempool and helps you decide whether to send or wait — plus a recommended sat/vByte to pay. Free, no signup.

Open the fee calculator →

Keep reading