Morning Edition · Monday, October 26, 2026Published at 1:45 AM EDT · New York
Attackers were exploiting the bug before disclosure, with at least one confirmed theft, and older versions of the wallet remain exposed when they connect to a hostile server.

Electrum, one of Bitcoin's oldest software wallets, released version 4.8.3 on Oct. 24 to close a high-severity flaw that let a malicious server steal funds from users who tried to speed up a slow payment. The developers disclosed the bug on Saturday and said some servers were already exploiting it. CoinDesk reports that at least one person lost bitcoin before the patch shipped.
The attack used a weakness in how Electrum trusts its data sources. Electrum is a light client. It does not download the full blockchain. It asks third-party Electrum servers, which anyone can run, for the wallet's transaction history. Before the patch, the wallet accepted pending (unconfirmed) transactions from those servers without verifying their signatures. According to Startup Fortune and Bitcoin.com News, an attacker who controlled a server could intercept a user's payment before it reached the network. The attacker then placed a fake pending transaction in the wallet's history. When the user used Replace-by-Fee (RBF), the standard Bitcoin method for raising the fee on an unconfirmed payment, the wallet built the replacement from the fake transaction. The user signed what looked like a routine fee increase, and the signed transaction sent the funds to the attacker.
The root cause is an input-validation failure at a trust boundary: the wallet treated unauthenticated server data as true. Bitcoin's consensus rules were not affected, and the signed thefts are valid transactions that cannot be reversed. The developers received two reports in October, including one from a user who lost funds after approving the fee bump. No total loss figure, recovery, or attribution has been published. Users connected only to servers they trust, including their own, were not exposed. Version 4.8.3 verifies signatures on the relevant unconfirmed transactions, but earlier versions remain vulnerable when connected to a malicious server.
The incident illustrates a distinction between self-custody and self-verification. An Electrum user holds the private keys, but by default the wallet learns the state of the blockchain from servers run by strangers. The developers advise users to check payment addresses and amounts before signing, which means the user, not the software, has to catch fraud the wallet failed to block on its own. Several other long-standing defects have turned up in widely used open-source crypto code this autumn.
What this means
Part of a tracked trend
Unaudited Open-Source Crypto Code Surfaces at Scale
Coordinated volunteer and AI-assisted review keeps exposing large backlogs of undiscovered defects in the open-source libraries that wallets, nodes and protocols depend on, so disclosure waves — not novel attacker research — become a recurring driver of emergency patches and incident risk across the ecosystem.
Start a discussion in Townsquare.
More from this edition
The exposed group is self-custody bitcoin holders who run Electrum, or wallets built on its code, against public servers. The attack needs no break in cryptography, only a hostile server and a user who wants a payment confirmed faster. Fee spikes create that demand. The market has treated this as a patched bug, but the patch protects only users who upgrade. Light-wallet installs often stay on old versions for months, and the attackers' servers do not disappear when a fix ships. The precedent is December 2018, when attackers ran malicious Electrum servers that pushed fake update prompts and stole bitcoin from users who installed the bogus software. Electrum then spent months responding to further server-side abuse. The desk's read is that more small thefts from unpatched clients are likely over the coming weeks, especially during periods of high fees. Developers of light wallets will move toward verifying server data rather than trusting it. The read would be wrong if Electrum reports quick upgrade adoption and no further victims surface within about a month.
What to watch
Observations to monitor, not financial advice.
Synthesized from: CoinDesk · crypto.news · Bitcoin.com News · Startup Fortune
Comments
1Oct 26, 5:45 AM
Since the exploit depends on a hostile server, users who cannot upgrade immediately can reduce exposure by connecting only to an Electrum server they operate or trust.