Self-custody after Coldcard and Electrum: a practical security guide for 2026
Two Bitcoin wallet failures this year had nothing to do with lost seed phrases. Here is what went wrong and which habits actually reduce the risk.
SECURITY & HACKSBITCOINANALYSIS
Lukas Brenner
10/28/20263 min read
For years, the standard advice on self-custody was simple: buy a hardware wallet, write down the seed phrase and keep it offline. Two incidents in 2026 show why that advice is no longer enough on its own. In the summer, attackers drained thousands of Coldcard wallets whose seeds had been generated with weak randomness. In October, Electrum users learned that malicious servers could trick older versions of the wallet into showing a forged transaction. In neither case did victims lose their seed phrase or click a phishing link.
Both cases point to the same idea. A wallet is a chain of components, from the chip that creates the seed to the server that reports the balance, and each link can fail. Below is how each failure worked and what a holder can do about it.
How weak randomness emptied Coldcard wallets
A seed phrase is only as strong as the randomness behind it. According to TRM Labs, a build configuration error in Coldcard firmware 4.0.1, released in March 2021, caused some devices to fall back to a weak software random number generator instead of the hardware entropy source. On older devices, effective key strength dropped from the intended 128 bits to as little as 40 bits, a range that modern computers can search.
That meant attackers did not need the device, the PIN or the paper backup. They could recreate the keys by brute force. Sweeping began on July 30, and within days Galaxy Research had counted about 1,816 BTC taken from more than 5,200 addresses, roughly $116 million at the time. Galaxy warned that the final total could keep rising as more victims come forward.
The most important detail for users is easy to miss: a firmware update stops the device from producing new weak seeds, but it does nothing for seeds that already exist. Anyone who generated a seed on affected firmware between March 2021 and the fix should treat it as compromised, create a fresh seed on updated hardware, confirm a receive address and move funds only after a small test transaction goes through.
How a malicious server fooled Electrum
The Electrum case targeted a different link. The popular desktop wallet relies on public servers to learn about transactions, and versions before 4.8.3, released on October 23, could be shown a forged transaction by a hostile server. The attack exploited the moment when a user raises the fee on a stuck payment. In reported cases from October 11 and October 18, the attackers used addresses that matched the last four characters of the real destination, counting on users who only check the ends of an address. The new version verifies the signatures on a user's own inputs before an unconfirmed transaction enters the wallet history. Users who ran their own server or connected only to a trusted one were not exposed, and those who checked the full address on a hardware wallet screen had a strong defense.
Habits that would have helped
A few practices address both failure modes. First, know where your keys came from: record the date and firmware version used to create every seed, and follow the vendor's security advisories. Second, split trust. A multisignature setup that combines devices from different manufacturers, each generating its own entropy, means a single firmware bug cannot empty the wallet. Third, verify on the device itself. Read the full recipient address and the amount on the hardware wallet's screen rather than the computer's, and compare every character.
Fourth, reduce your dependence on strangers' servers. Running your own Bitcoin node with an Electrum server, or connecting to a provider you trust, removes the exact attack Electrum just patched. Fifth, update only from the official source. Download from the project's own website and verify signatures, because fake update prompts are a common lure after any public advisory. Finally, rehearse migration. Moving funds to a new seed under pressure invites mistakes, while a calm test run done in advance turns an emergency move into a routine one.
None of this makes self-custody risk-free, but it does change the question a holder should ask. Instead of asking whether the seed phrase is safe, the better question in 2026 is which single component, if it failed, would cost everything. If the answer is one device, one vendor or one server, that is the place to start.