A critical security vulnerability in older Coldcard firmware versions has weakened the seed generation process for several hardware wallet models. According to recent analyses, more than 1,000 Bitcoin were moved from numerous wallets around the time of the incident. The exact attribution and forensic investigation are ongoing.
The crucial takeaway is this: Self-custody was not the problem here. A specific implementation of the random number generator failed. While those who self-custody their private keys remain independent of a custodian, they must be able to trust that their wallet, firmware, and security processes are functioning correctly.
What happened in the Coldcard incident?
When setting up a Bitcoin wallet, it generates a seed from which private keys are derived. To ensure this seed cannot be guessed, it must be based on sufficiently random data. According to the manufacturer, Coinkite, this is exactly where the vulnerability lay.
In affected Coldcard firmware versions, the seed generation process did not access the hardware random number generator as intended. Instead, a weaker software-based random number generator was used. Under certain assumptions, its results were significantly easier to narrow down than a seed with the expected 128-bit security level.
In a preliminary analysis, Coinkite estimates the effective search space for affected Mk2 and Mk3 seeds to be around 40 bits. For the Mk4, Mk5, and Q models, additional entropy from secure elements was incorporated; the manufacturer estimates this to be approximately 72 bits. While better, this still falls short of the intended security level.
This created a scenario for attackers that should be virtually impossible with correctly generated seeds: the ability to automate the process of testing potential seeds, deriving Bitcoin addresses from them, and matching these against publicly visible blockchain data. This required neither the theft of the device nor the acquisition of the seed phrase through phishing.
In late July, approximately 594 Bitcoin were moved from about 500 wallets in a short period. Subsequent analyses by blockchain researchers reported a total of approximately 1,082.65 Bitcoin from 1,196 addresses. Coinkite has confirmed the wallet vulnerability; the full attribution of the transactions and the investigation into the attack were not yet complete at the time of writing.
Which Coldcard models and firmware versions are affected?
According to the security advisory from Coinkite updated on August 1, 2026, seeds generated on the following devices and firmware versions are affected:
- Coldcard Mk2 and Mk3: Firmware 4.0.1 up to and including 4.1.9
- Coldcard Mk4 and Mk5, standard version: before firmware 5.6.0
- Coldcard Q, standard version: before firmware 1.5.0Q
- Coldcard Mk4 and Mk5, Edge version: before firmware 6.6.0X
- Coldcard Q, Edge version: before firmware 6.6.0QX
The timing of the seed generation is critical. If a seed was created on an affected firmware version, a subsequent firmware update will not fix that seed. The update only corrects the generation of new seeds.
Coinkite notes an exception for users who added at least 50 fair, independent, and secret dice rolls during the initial creation. A strong, unique BIP39 passphrase can also provide an additional layer of security. However, it does not repair the weak seed and does not replace the recommended migration.
Why self-custody was not the problem
Self-custody means that users control their own private keys. It describes who has the ability to spend the bitcoin – not whether every piece of hardware or software used is automatically error-free.
The Coldcard incident therefore does not disprove the principle of self-custody. Rather, it shows that self-custody is only as robust as the technical and organizational implementation behind it. A faulty random number generator, a compromised seed phrase, an insecure backup, or an incorrectly verified receiving address can become a risk even when in self-custody.
Self-custody is a model, not a security guarantee
"Not your keys, not your coins" describes a key advantage of Bitcoin: those who hold the keys are not dependent on the payment authorization or solvency of a custodian. However, this advantage does not automatically provide protection against all other risks.
With self-custody, responsibility shifts to the user and the chosen wallet solution. This includes:
- secure and verifiable seed generation,
- authentic firmware from an official source,
- a protected, offline-stored backup,
- verification of receiving addresses on the device,
- regular security updates,
- a tested recovery process.
This incident is therefore not an argument against self-custody. It is an argument against the assumption that a single brand or device automatically makes a setup secure.
What affected Coldcard users should do now
Anyone who generated a seed on an affected Coldcard firmware version should check the official security advisory from Coinkite and migrate carefully. Remember: staying calm and in control is more important than rushing without verification.
Coinkite essentially recommends the following steps:
- Check if you are affected: Determine the model, firmware track, and firmware version used during the initial seed generation.
- Install the corrected firmware: Use only the official download page and select the appropriate standard or edge version.
- Generate a completely new seed: Do not re-import or continue using the old seed.
- Verify backup and wallet fingerprint: Document the new seed phrase securely offline and verify the new wallet uniquely.
- Check the receive address on the device: Do not rely solely on the display on your computer or smartphone.
- Send a small test transaction: Only transfer the remaining balance after successful confirmation.
- Migrate remaining Bitcoin: Keep the old backup until all transactions have been confirmed and verified.
A firmware update alone is not enough. Resetting the device and then importing the same seed will not eliminate the vulnerability. If you are unsure, do not take improvised steps and never disclose your seed phrase on a website, in a chat, or to anyone claiming to be support.
What does the Coldcard incident mean for 21bitcoin users?
The vulnerability affects seed generation in certain Coldcard firmware versions—not the Bitcoin network or the 21bitcoin app. This incident is only relevant to 21bitcoin users if they send Bitcoin to an external wallet whose seed was generated on an affected Coldcard.
Combining self-custody and professional custody
Users don't have to commit to just one custody model permanently. With 21bitcoin, purchased Bitcoin can remain in your account or be transferred to your own wallet. For recurring purchases, you can use the Auto-Wallet-Transfer to set a custom threshold at which Bitcoin is automatically sent to an external wallet.
If you are currently in the middle of a security migration, you can pause transfers until your new wallet setup has been verified. If you are still learning about self-custody, you can start with small amounts and test transactions. If Bitcoin remains in your 21bitcoin account, technical custody is handled via the cold storage infrastructure of BitGo Custody.
Both approaches carry different risks: self-custody reduces counterparty risk but requires a robust security process of your own. Professional custody reduces the technical burden but requires trust in the provider and their infrastructure. The deciding factor is not which model seems ideologically "more correct," but rather which risks users understand and can reliably control.
What users can learn from this incident
The Coldcard incident provides five key takeaways for using hardware wallets:
- The manufacturer and model are not the entire security concept. Even established devices can contain critical flaws.
- Firmware versions are critical to security. Updates should come from official sources and be installed before generating a seed.
- A weak seed remains weak. Software updates do not change existing private keys.
- Redundant entropy sources can mitigate individual errors. However, the key is how these are technically combined and verified.
- A clean migration process prevents follow-up errors. Verify your new wallet, send a test transaction, and only then move the full amount.
Self-custody does not require perfect technical knowledge. It does, however, require questioning security assumptions and designing processes so that individual errors do not immediately lead to a total loss.
Conclusion: Control requires verifiable security
The Coldcard incident was not a failure of self-custody. It was the failure of a central security component within a specific wallet implementation. While users controlled their keys, those keys were based on insufficient randomness in the affected cases.
The correct conclusion is therefore neither blind trust in every hardware wallet nor a blanket rejection of self-custody. A risk-based approach makes sense: keep wallet software up to date, take seed generation and backups seriously, test larger transfers, and only scale up self-custody once your own process is robust.
At 21bitcoin, this transition can be managed flexibly: Bitcoin can be held professionally or transferred to your own custody via an external wallet and the auto-wallet transfer feature. The decision remains with the user—as does the responsibility to carefully select and vet an external wallet.
FAQ
Was Bitcoin itself hacked?
No. According to Coinkite, the vulnerability lay in the firmware of certain Coldcard models during seed generation. The Bitcoin network and its cryptography were not compromised.
Is a Coldcard firmware update sufficient?
No, if the seed was already generated on an affected firmware version. The update corrects the generation of new seeds but does not retroactively make an existing weak seed secure. Affected users must create a new seed and transfer their Bitcoin to the new wallet.
Are all Coldcard wallets affected?
No. The model, the firmware version used during seed generation, and the release track used are the deciding factors. Coinkite also notes exceptions for seeds supplemented with at least 50 independent and secret dice rolls. When in doubt, the manufacturer recommends migration.
Does a BIP39 passphrase provide protection?
A strong, unique, and separately stored passphrase can create an additional barrier. Short, reused, or easily guessable passphrases do not reliably provide this protection. Even a strong passphrase does not fix an affected seed; Coinkite continues to recommend switching to a newly generated seed.
Is self-custody still secure after this incident?
Yes, if implemented carefully. Self-custody protects against the counterparty risk of a custodian, but not automatically against faulty wallet software, insecure backups, or user error. Security depends on the entire setup.
Do I need to do anything as a 21bitcoin user?
Only if you use a potentially affected Coldcard wallet or transfer Bitcoin to one. In that case, check the original firmware version before making further transfers, follow the manufacturer's instructions, and only register a verified new wallet after a successful migration.
Note: Marketing communication from FIOR Digital GmbH (21bitcoin). Investments in Bitcoin involve risks and opportunities. Past performance is not an indicator of future results. This article does not constitute legal or investment advice.
