Skip to main content

Search...

Popular searches

Coldcard accepted hidden change paths that could hold funds to ransom

CoinkiteHigh

Who is affected

Coldcard users on firmware before 3.0.2 who signed transactions prepared by a compromised computer could have their change sent to a path they cannot spend from, opening the way to ransom. Coinkite considers the attack limited because it needs the victim's xpub and control of the PSBT files.

What happened

On 1 November 2019 Coinkite released Coldcard firmware 3.0.2 and a post crediting @TheCharlatan for reporting that a valid PSBT could send a transaction’s change to a location the user does not know. The researcher, writing as sedited together with Kaspar Etter of Shift Cryptosecurity, published the full details on 13 November 2019.

According to the researchers, the Coldcard neither displayed nor restricted the derivation path of change outputs. A malicious or modified wallet app on the computer could set a change path with extremely large indexes, so the change would be practically unspendable without knowing the exact path, and the attacker could demand a ransom for it. A second finding concerned receive addresses: the path parser accepted whitespace such as newlines, so the path shown on screen could differ from the one actually used, with the real end of the path pushed off-screen.

Coinkite states the attack requires knowing the victim’s xpub and a man-in-the-middle position on the PSBT files, and that keeping the original PSBT makes tampering easy to detect. Firmware 3.0.2 checks derivation paths against a conservative set of rules and shows a “Troublesome Change Outs” warning; Coinkite says these are warnings for now and may become fatal errors later. The researchers write that the release notes did not clearly flag a security fix and that they received two Coldcards and a mug rather than a bounty. They also report that the BitBox01 had been affected by similar attacks, fixed in March 2019.

What Coinkite advises:

  • Do not include xpub values in PSBT files and treat your xpubs as confidential.
HardwareColdcard

Coldcard is an air-gapped hardware wallet for Bitcoin, made by Coinkite, that stores private keys offline and signs transactions without internet exposure.

HardwareFirmware

Firmware is the software that runs on a hardware wallet itself: it generates keys, shows transaction details on the screen and signs.

Read full definition
TransactionPSBT

PSBT (Partially Signed Bitcoin Transaction) is a Bitcoin transaction format that allows multiple parties to sign a transaction incrementally before finalizing it.

Read full definition
BlockchainDerivation Path

A derivation path is a string of indices (e.g., m/44'/0'/0'/0) that specifies how to derive specific keys and addresses from a hierarchical deterministic (HD) wallet's master seed.

Read full definition
TransactionChange Address

A change address is a new address where leftover cryptocurrency is sent after a transaction, ensuring any unspent funds are returned to the sender in blockchain transactions.

Read full definition
WalletWallet Address

A wallet address is the public identifier others use to send you crypto. It is derived from a public key and is safe to share.

Read full definition
BlockchainXPUB

XPUB is an extended public key (xpub) in hierarchical deterministic (HD) wallets. It derives child public keys and addresses from a master public key without exposing private keys.

Read full definition

Sources

Independent reporting and research this entry was checked against.

  1. sedited (TheCharlatan) — Ransom attack on Coldcard (13 Nov 2019)
  2. Coinkite — Troublesome change (1 Nov 2019)

Learn more

Guides on protecting yourself against this type of incident (Firmware vulnerability) and the glossary terms that describe it.

Cite this entry

WalletInsights. “Coldcard accepted hidden change paths that could hold funds to ransom”. Hardware wallet security incident tracker. Last verified November 4, 2026. https://walletinsights.io/en/security-incidents/coldcard-change-path-ransom-attack-2019/

Corrections and right of reply

Vendors, researchers and readers can send corrections or statements to security@walletinsights.io. We check them against the sources, update the entry and record the change in its log.