Wallet bug lets rogue servers steal BTC

TLDR

A critical bug in the Electrum Bitcoin (BTC) wallet let malicious servers redirect users' coins when they tried to speed up pending payments, but a fix is now live.

1. Electrum versions before 4.8.3 had a vulnerability that at least one attacker exploited to steal BTC via rogue Electrum servers.
2. The bug let a malicious server replace a real unconfirmed transaction with a fake one, then trick users into signing it when using Replace-by-Fee (RBF) to raise fees.
3. Updating to Electrum 4.8.3, using trusted servers, and carefully checking destination addresses and amounts before every signature significantly reduce this specific risk.

Deep Dive

1. What Happened And How Bad It Was

Several reports describe a flaw in Electrum, a popular lightweight Bitcoin wallet, that allowed rogue servers to steal BTC during fee bumps. Electrum confirmed two incidents, including at least one case where a user lost funds after increasing a transaction fee using RBF, and released version 4.8.3 to fix the issue Electrum advisory summary.

Coverage from multiple outlets notes that the bug affected all Electrum releases before 4.8.3 and was actively exploited by malicious servers connected to the public Electrum network Bitcoin.com report and CoinDesk coverage. Exact total losses have not been disclosed.

2. How Rogue Servers Stole BTC

Electrum is a "light" wallet that relies on external servers for transaction history and unconfirmed transaction data instead of fully validating every transaction like a full node. Before 4.8.3, it trusted those servers for unconfirmed outgoing transactions without verifying their signatures.

Attackers exploited this by:

1. Blocking the user's genuine outgoing transaction from reaching the Bitcoin network.
2. Inserting a fake pending transaction in the wallet history that sent BTC to an attacker-controlled address, often with a zero fee and with similar ending characters to the real recipient address TokenPost description.
3. Waiting for the user to use RBF to "speed up" the stuck payment; Electrum would then sign and broadcast a valid replacement transaction that actually paid the attacker TradingView summary.

Version 4.8.3 adds signature checks for unconfirmed transactions spending the wallet's own coins and rejects invalid ones before they appear in history detailed breakdown.

3. How Users Can Reduce Risk

Reports emphasize three main mitigations:

1. Upgrade Electrum to at least 4.8.3 using the official site and verify downloads where possible Electrum-focused coverage.
2. Prefer trusted or self-hosted Electrum servers, as users connected only to such servers were not exposed to this particular attack.
3. Treat every signing request, including fee bumps, as a fresh transaction: confirm the full recipient address and amount rather than relying on earlier checks TokenPost follow-up.

More broadly, this episode highlights a general trade-off with light wallets that delegate some trust to remote servers, compared with running a full node that validates all data locally.

Conclusion

The Electrum bug did not compromise Bitcoin itself, but it exposed a serious weakness in how one widely used wallet trusted remote servers for unconfirmed transactions. The fix in version 4.8.3, plus better server hygiene and careful transaction review, substantially closes this specific theft vector while underscoring that convenience-focused light wallets always carry some additional trust risk compared with fully validating setups.