Crypto
03 Aug 2026
Read 13 min
Coldcard seed vulnerability 2026: How to Protect Funds *
Coldcard seed vulnerability 2026 exposes predictable keys; move funds and rotate seeds to secure assets
The Coldcard seed vulnerability 2026 is driving a fast, automated sweep of weak wallets. On-chain data flagged three attack waves, draining roughly 1,367 BTC from 4,585 addresses. If you made a seed on older firmware, act now: move funds to a new, strong wallet, add your own entropy, and update all devices.
A major wallet attack is still active. Analysts at Galaxy Research observed three waves of coordinated Bitcoin sweeps that target keys created on a flawed Coldcard firmware from March 2021. The attacker first hit large balances, then shifted to smaller wallets, often a few thousand dollars each. Across all waves, about 1,367 BTC has moved, which is nearly $89 million at recent prices, from 4,585 addresses. The attacker also changed tactics to hide their tracks, sending each victim’s coins to different destinations and using advanced script types.
This is a teachable moment. Bad randomness can break even “cold” storage. You must assume seeds from the affected period are unsafe. The rest of this guide explains what happened, who is at risk, and the exact steps to protect your coins today.
Bundled about six victims per sweep instead of one at a time.
Sent each victim’s coins to a unique destination instead of shared collectors.
Used pay-to-witness-script-hash (P2WSH) outputs, which can hide multisig or timelock conditions.
Scanned only the default derivation path (the standard branch most wallets check first), not multiple branches per seed.
These changes hide links between victims and speed up scanning. They also suggest the operator adjusted after public analysis, or that a new operator is grinding the same weak key space. Galaxy Research believes each wave is internally consistent but will not link waves together.
You created a new seed on a Coldcard around March 2021, before a firmware fix was installed.
You relied only on the device’s software randomness and did not add your own entropy (like dice rolls).
You used the default derivation path and typical address types (for example, native SegWit addresses).
You imported that seed into other wallets. The seed is the problem, not the app you use.
If you are not sure when your seed was created, treat it as suspect if it might date to that window. If you only ever used seeds generated on fully patched firmware, your risk is much lower, but you should still review your setup.
Unexpected outgoing transactions that you did not sign.
Small, fast sweeps that move your whole balance to a new address you do not control.
Movements that cluster with other victims around the same time window.
Set alerts on your addresses using a reputable block explorer or wallet monitoring tool. If you see a surprise transaction, act at once on any remaining funds.
Do not create new addresses from it.
Do not export or share its extended public keys (xpubs) again.
Use a device with the latest firmware from a trusted vendor.
Confirm the device uses hardware randomness.
Add your own entropy. Roll physical dice many times and enter the results on the device if supported. This helps ensure the seed cannot be guessed.
Write the seed backup by hand on paper or steel. Verify each word carefully. Store backups in separate safe places.
Use a new wallet file and a fresh derivation path created by the new seed.
Use PSBT (partially signed Bitcoin transactions) if your device supports it. Keep private keys offline at all times.
Test the setup with a small amount first, then move the rest.
Send coins from the old wallet to the new wallet in as few transactions as practical.
Use a fee high enough for fast confirmation. Add replace-by-fee (RBF) if supported, so you can bump the fee if needed.
Avoid reusing addresses. Receive to a fresh address for each transaction.
Use 2-of-3 or 3-of-5 multisig with keys on devices from different vendors. This reduces single-point failure risk.
Keep each device and backup in separate places. Practice recovery with a small test spend so you know the process works.
Update firmware on all hardware wallets to the latest stable release.
Remove old xpubs from watch-only apps or services tied to the weak seed.
Enable passphrases only if you understand and can safely back them up. A lost passphrase means lost coins.
Always add your own entropy during seed creation when supported (for example, dice).
Never reuse old seeds for new savings. Treat each long-term stash as a fresh setup.
Install firmware updates from official channels only.
Read release notes for security fixes. If a note mentions randomness or seed generation, take it seriously.
Buy devices from trusted sources. Beware of tampered or second-hand gear.
Multisig with vendor diversity helps protect against one-device flaws.
Split backups across safe locations. Consider Shamir backups only if you fully understand them.
Limit what you expose online. Watch-only wallets are useful, but treat xpubs as sensitive data.
Start with small test sends for any new wallet or firmware.
Use coin control to avoid linking all your funds in one transaction when privacy matters.
Label addresses and keep simple records so you can spot odd activity fast.
If your seed is weak and you use the default path, you may be hit sooner.
Even small balances are now in scope. Do not wait to act.
Unique destinations make blacklist checks harder. Focus on securing your keys, not on tracking the thief.
Set up address alerts for your current wallets. If a surprise outgoing transaction appears, immediately sweep any remaining UTXOs to your new wallet with a higher fee. Then retire the old seed forever.
Wallet makers should publish clear guidance on secure seed creation, entropy options, and firmware fixes.
Exchanges and services can message users who deposited from known-at-risk address patterns and suggest urgent wallet rotation.
Educators and communities should promote simple checklists for seed safety and recovery drills.
The lesson is simple: security starts with strong randomness and tested recovery. A cold wallet is only as safe as its seed.
In closing, treat the Coldcard seed vulnerability 2026 as a prompt to review your setup, rotate any seeds that might be weak, and harden your process. Create a new seed with true randomness, move funds now, and adopt habits that keep your Bitcoin safe for the long run.
(Source: https://www.coindesk.com/tech/2026/08/02/bitcoin-cold-wallet-attack-spreads-to-4-500-addresses-as-losses-near-usd89-million)
For more news: Click Here
What happened: understanding the Coldcard seed vulnerability 2026
The flaw in simple terms
In March 2021, a firmware build on some Coldcard devices used software to create seed words, not the chip’s hardware random number generator. That made the pool of possible seeds smaller and more predictable. With the right disclosure and enough compute, an attacker can recreate those weak seeds offline. They do not need your device. They just need to test the limited key space and scan standard wallet paths for balances.How the attack evolved on-chain
– Wave one hit on July 30 and drained 1,083 BTC from 1,196 addresses in 41 minutes. Each address went to a small set of “collector” addresses, which made mapping easy. – Wave two continued the same basic approach. – Wave three changed tactics. The attacker:Who is at risk and how to check
High-risk users
You face higher risk if any of the following apply:Warning signs
Move now: a clear action plan to secure funds
Time matters. The attacker is actively scanning predictable keys. If your seed is weak, assume compromise and move coins today.1) Stop using the old seed
2) Create a brand-new seed with strong randomness
3) Build safer transaction habits
4) Sweep funds quickly and cleanly
5) Consider diversified multisig
6) Update and harden everything
Best practices that help prevent the next crisis
Make randomness your first priority
Keep devices current and verified
Use defense in depth
Transact with caution
How the on-chain pattern helps you react
The third wave targets smaller balances and sends coins to unique destinations, often as P2WSH outputs. The attacker also seems to scan only the default derivation path. This means:What companies and communities can do now
FAQ
Q: What is the Coldcard seed vulnerability 2026 and how did it enable the recent wallet sweeps?
A: The Coldcard seed vulnerability 2026 refers to a flaw in some Coldcard firmware (March 2021) that used a predictable software randomiser instead of the device’s hardware RNG, creating a bounded, reproducible set of seeds. That weakness let attackers recreate weak seeds offline and automate sweeps of affected wallets without touching the device.
Q: How much Bitcoin was stolen and how many addresses were affected by the attack?
A: Analysts observed three waves that moved roughly 1,367 BTC — nearly $89 million — from about 4,585 addresses. Wave one alone drained about 1,083 BTC from 1,196 addresses in 41 minutes, and later waves shifted to smaller balances including a roughly 208 BTC third wave from 1,912 addresses.
Q: Who is at risk from this vulnerability and how can I check if my seed is affected?
A: You face higher risk if you created a seed on a Coldcard around March 2021 before the firmware fix, relied only on the device’s software randomness, used default derivation paths, or imported that seed into other wallets. If you are unsure when the seed was created, treat it as suspect, set address alerts, and watch for unexpected outgoing transactions.
Q: If my seed was created on affected firmware, what immediate actions should I take?
A: Assume compromise and move coins immediately by creating a new seed on a device with the latest firmware, adding your own entropy (for example, dice rolls), and sweeping funds to the new wallet in as few transactions as practical with a sufficient fee. After sweeping, retire the old seed, remove old xpubs from watch-only apps, and update firmware on all hardware wallets.
Q: How did the attacker change tactics in the third wave and what does that mean for victims?
A: In wave three the attacker batched roughly six victims per sweep, sent each victim’s coins to unique destinations instead of shared collector addresses, and parked funds in P2WSH outputs that can hide multisig or timelock conditions. They also scanned only the default derivation path, which speeds scanning and makes blacklist-based defenses less effective, so even small balances on standard paths are vulnerable.
Q: How should I create a new seed to avoid the same vulnerability?
A: Create a new seed on a device with the latest firmware that uses hardware randomness and add your own entropy during setup, for example by entering many physical dice rolls. Write the backup by hand and store copies in separate secure locations, then test the setup with a small transaction before moving larger balances.
Q: Is multisig recommended after this incident and how does it help?
A: Yes; the guidance recommends diversified multisig (for example 2-of-3 or 3-of-5) with keys on devices from different vendors to reduce single‑device or single‑seed failures. Keep each device and backup in separate places and practice recovery with a small test spend so you can restore funds if needed.
Q: How can I monitor my addresses and what should I do if I see suspicious movement related to the Coldcard seed vulnerability 2026?
A: Set address alerts using a reputable block explorer or wallet monitoring tool and monitor for unexpected outgoing transactions. If you see activity consistent with the Coldcard seed vulnerability 2026, immediately sweep any remaining UTXOs to a newly created secure seed with a higher fee and retire the compromised seed forever.
* The information provided on this website is based solely on my personal experience, research and technical knowledge. This content should not be construed as investment advice or a recommendation. Any investment decision must be made on the basis of your own independent judgement.
Contents
