By Hamza Faisal

Electrum has released version 4.8.3 to close a high-severity flaw that let rogue servers quietly swap a Bitcoin payment for a thief's transaction, then turn the victim's own attempt to speed it up into the moment the theft became final. The wallet's developers urged all users to upgrade immediately, warning that every version before 4.8.3 is affected.

The flaw, documented in advisory GHSA-6jp4-8v48-cc5v, sat in how the lightweight wallet handles unconfirmed transactions. Electrum does not run its own node for most users; instead it talks to a network of ElectrumX servers, and anyone can run one. While the wallet independently verifies confirmed transactions, older versions accepted certain unconfirmed transactions without checking their signatures, and attackers turned that gap into a trap.

How a fee bump became the theft

According to the advisory and reporting from Bitcoin.com and Cryptopolitan, a malicious server could withhold a user's broadcast transaction from the real Bitcoin network, then substitute a conflicting transaction that sent the funds to an attacker-controlled address. Because the wallet did not verify the signature, the fake appeared in the user's history as an ordinary pending payment, while the real payment stayed hidden.

The trap closed when the user did the natural thing. Seeing the payment stuck, the user bumped the fee using Replace-by-Fee, the mechanism for speeding up an unconfirmed transaction. But the wallet built the replacement from the substituted transaction the server had displayed, so the fee bump signed the attacker's payment instead of the user's own.

The attackers added a second layer of deception to make the swap hard to catch at a glance. The replacement addresses were crafted to match the final four characters of the real destination, the part of an address most people eyeball when double-checking. Some of the fraudulent entries were even set with a zero fee, a detail designed to nudge the victim into starting exactly the fee increase that triggers the theft.

One user lost funds, another spotted it in time

The advisory documents two reports. One user spotted the substitution before losing funds. Another, who privately reported the incident on October 18, bumped the fee on the fake transaction and lost money. The amount lost has not been disclosed, and the maintainers say some servers are running the attack in the wild.

Version 4.8.3 fixes the hole by checking signatures on wallet-owned inputs before adding a mempool transaction to local history. Users who connect only to servers they run themselves were never affected, and the fix does not change how confirmed transactions are handled.

What users should do now

Electrum's guidance is blunt: update to 4.8.3 before signing anything, and download only from electrum.org, verifying the installer's signature against the published checksums. Until every install is updated, users should verify output addresses and amounts before signing anything, including fee bumps, and avoid fee-bumping any unconfirmed transaction they cannot fully verify.

The incident is a reminder of the trade-off at the heart of lightweight wallets. Outsourcing blockchain data to outside servers keeps the software fast and light, but it means the wallet must trust what those servers report about transactions that have not yet confirmed. Electrum has shipped emergency fixes before: in January 2018 it closed a JSON RPC interface that had been left open for about two years after a researcher showed a website could exploit it to drain funds. This time the lesson is narrower and more practical — a fee bump is a signature, and a signature should never go to a transaction the wallet has not verified.

By Hamza Faisal