Address Poisoning and Clipboard Malware: Limit the Damage

How address poisoning, clipboard malware and phishing trick people into sending bitcoin to attackers, how to check addresses, and how a daily limit caps losses.

Many bitcoin losses involve no stolen keys at all. The owner signs the payment themselves, to an address that looks right and is not. Clipboard malware swaps the address you copied, address poisoning plants a lookalike in your history, and phishing gets you to hand over your seed or approve something you did not mean to. Bitcoin payments cannot be reversed, so the defence has two layers: check addresses in ways these tricks cannot fake, and set up your wallet so that when a check fails anyway, the damage has a ceiling. This article covers both.

Three ways to pay the wrong person

Clipboard malware ("clippers")

Malware on a computer or phone watches the clipboard. When you copy something that looks like a bitcoin address, it replaces it with the attacker's address. You paste, the wallet shows a valid address, and you send. Clippers often arrive with pirated software, fake apps and unofficial downloads.

Address poisoning

An attacker creates an address whose first and last few characters match one you use, which is cheap to generate, and gets it into your transaction history, usually with a tiny transaction. Later you copy "the usual address" from your history and pick theirs. Poisoning is most common on networks where people reuse one address for years, but it works anywhere people copy addresses from history or check only the ends.

Phishing

Fake support accounts, fake wallet websites, fake apps in app stores, emails about "wallet validation" or an urgent firmware update: the goal is either your seed words or a payment you did not intend. A variant targets wallets with security alerts: a fake "suspicious activity, click here to cancel" message.

How to check an address properly

  • Check the whole address, or a long stretch in the middle. Attackers match the beginning and the end because that is what people check. Read the full address, or compare a chunk of eight or more characters from the middle as well.
  • Check it on a screen malware cannot change. A hardware wallet shows the destination on its own display when you sign. Compare that with the address the recipient gave you through another channel, not with your computer's screen.
  • Do not copy addresses from your transaction history. Get a fresh address from the recipient each time, or use a saved contact you verified once.
  • Prefer QR codes and payment links (BIP 21 bitcoin: URIs) scanned from the recipient's own screen, which skip the clipboard.
  • Use a new receive address for every payment you receive. It keeps your history harder to poison and is better for privacy (see address reuse).
  • Send a small test payment first for large or first-time transfers, and confirm with the recipient that it arrived.

How to recognise phishing

  • No legitimate person or company ever needs your seed words. Not support, not a wallet maker, not a "recovery" service. Anyone who asks is stealing.
  • Install wallets only from the official source and check signatures where the project publishes them.
  • Firmware updates come through the vendor's own app or device, never through a link in a message.
  • Treat urgency as a warning sign. "Act within 24 hours" is how phishing gets past careful people.
  • Know what your wallet's real alerts look like. If its genuine alerts never contain links, a message with a link is fake.

Why verification is not enough on its own

Everyone fails a check eventually: a tired evening, a convincing message, a device that was already compromised. A good setup assumes that and limits what one mistake, or one compromised device, can cost:

  • A daily limit on the convenient path. Payments from your phone alone (or with an automatic co-signer) are capped per day. A clipper, a phisher or a thief who controls the phone can take at most the limit.
  • A stronger device above the limit. Larger payments need a hardware wallet, whose screen shows the real destination and amount. Malware on the phone cannot change what the device displays.
  • Rules that only the stronger device can loosen. If the phone alone could raise the limit, malware would simply raise it first.
  • Alerts and delays for unusual actions, such as a recovery starting (see Delay & Notify).
  • A separate wallet for savings that the everyday keys cannot touch.

A limit does not help if you approve a large payment to the wrong address on your hardware wallet yourself. That is why the device's screen, read carefully, remains the last check.

How Trikey approaches it

Trikey is built around the second layer. It is a 2-of-3 multisig wallet with your hardware wallet (key 1), your phone (key 2) and the Trikey Guardian on your own home server (key 3). From the design document's rules and threat model:

  • A daily limit you set (the app suggests 200,000 sats). The guardian co-signs phone payments only while the total leaving the wallet over a rolling 24 hours, fees included, stays under it. A stolen or compromised phone can send at most that.
  • Over the limit, the hardware wallet signs instead of the guardian, and shows the payment on its own screen.
  • Raising the limit needs the hardware wallet. The phone alone can only tighten the rules. The approval is a short text the device displays, with the new values in clear.
  • Turning the limit off is possible but strictly opt-in: it needs its own hardware approval, and your alert contacts are told. With the limit off, a thief who gets into the phone can send everything at once, and the design says so.
  • Alerts never carry a link or a button and never ask anyone to sign in, in any channel. The guardian breaks up anything link-like before it sends a message, so a message with a link is not from it.
  • The phone backup's recovery code and the Recovery Kit's words are never put on the clipboard, and on Android they are hidden from screenshots and the app switcher.
  • An optional Savings wallet that the phone and the guardian cannot move even together.

Status: Trikey is pre-alpha and has not been audited. Use it on test networks (signet, testnet4 or regtest); if you try mainnet, use only an amount you can afford to lose. The testers guide includes a payment inside the limit and one over it, so you can see both paths.

FAQ

Can I get bitcoin back if I sent it to a poisoned address?

Almost never. Bitcoin payments cannot be reversed. Report it to the police if the amount matters, and beware of "recovery" services that contact you afterwards: they are a common second scam.

Does a hardware wallet protect against clipboard malware?

Only if you read the address on the device's screen and compare it with the recipient's real address. The device shows what it signs; it cannot know who you meant to pay.

Is checking the first and last characters enough?

No. Lookalike addresses are generated to match exactly those. Check the whole address, or a long section in the middle as well.

What is a good daily limit?

Enough for what you spend from your phone in a normal day, and small enough that losing it would hurt but not matter. You can lower it at any time; raising it should need a stronger key.

How do I know an alert from my wallet is real?

Learn what your wallet's real alerts contain. If they never include links or ask you to sign in, any message that does is fake. When in doubt, open the wallet app yourself rather than following the message.