Electrum Wallet Flaw: Click 'Speed Up Transaction' and a Rogue Server Steals Your Coins

An everyday move — "the network is slow, let me bump the fee" — became the trigger for this theft.

Three key facts

Electrum released version 4.8.3 on October 24, fixing a flaw that let malicious servers steal funds. According to CoinDesk, the vulnerability was disclosed in a GitHub security advisory and developers said some servers were already exploiting it. Two reports came in during October, including one user who lost funds after approving what looked like a routine fee increase.

The attack hinges on Electrum not running its own full node. Unlike a full Bitcoin node, Electrum relies on outside servers to retrieve transaction history and broadcast payments. Before the fix, the wallet trusted those servers' reports of unconfirmed transactions without verifying their signatures. A malicious server could intercept a payment before it reached the network and replace it in the wallet's history with a fake transaction — one that spends the user's coins to an attacker address, using invalid signatures the wallet failed to detect.

The trap's trigger is Replace-by-Fee (RBF). Bitcoin allows replacing an unconfirmed transaction with one carrying a higher fee. When a user chooses to "speed up," Electrum would take the fraudulent transaction and sign a valid replacement, sending coins to the attacker. In one reported case the malicious transaction carried zero fee, making it look stuck; attackers also generated receiving addresses whose last four characters matched the real destination, making substitution harder to spot in a quick check.

Wang Dou's Take

The sharpest part first: the first reporter used a 2-of-3 multisig wallet with two Trezor hardware devices — meaning he locked his money down fairly carefully and verified the legitimate payment on both devices. But the problem wasn't his money; it was his information source. The "pending transaction" the wallet showed him was itself a forgery.

That's the structural risk of light wallets. What you trust isn't cryptography — it's the server that checks the books for you. No matter how secure the private key or how expensive the hardware wallet, if the channel feeding you information is compromised, you're signing against an altered ledger. The cleverest part of this attack is exactly that: it didn't break encryption. It broke "what you think you're looking at."

Second detail everyone should remember: the attacker made the last four digits of the receiving address match. People are lazy — when checking an address, they habitually glance at the first and last few characters, and attackers know this. The most expensive lesson in security design is never the algorithm; it's human habit.

Finally, something practical. Electrum 4.8.3 fixes this, but older versions remain at risk whenever connected to a malicious server. If you use Electrum, what you should do now isn't "be careful" — it's upgrade, and connect to your own node if you can. This incident proves an old line again: "my keys, my coins" only holds when you can see the real ledger.

Source: CoinDesk · Electrum Security Advisory