How a Fee Bump Became a Trap: The Electrum Rogue-Server Flaw Explained

A reported Electrum flaw let rogue servers swap a payment for a fake one and exploit fee bumps. How it works, what changed and how to lower your risk.

Published: October 26, 2026

📌 Pinned Check a Wallet Address Before Sending Crypto – Free, No Sign-Up → or create a free account

In late October 2026, the developers of the Bitcoin wallet Electrum disclosed a flaw that had been used against at least one user. Reports describe a rogue server that swapped a legitimate payment for a fake one and then waited for the user to "speed up" the payment. This article explains how that kind of attack works, what the developers say they changed and what ordinary users can do to reduce their exposure. It is based on press reports of the developers' security advisory, so details may be updated.

What was reported

According to CoinDesk and other outlets, Electrum versions before 4.8.3 could be tricked by a malicious server. The developers released version 4.8.3 on 24 October 2026. Reports say they had received two private reports in October, on 11 and 18 October. In one of them, a user lost funds after raising the fee on a transaction. The amount was not disclosed, and the malicious servers have not been publicly identified. The developers reportedly said that some servers were already exploiting the flaw before the fix.

Why wallets depend on servers

Many popular wallets do not store the whole Bitcoin blockchain. Instead they ask outside servers for the history of the user's addresses and use them to send payments to the network. This design is convenient and fast, but it means the wallet must decide how much to trust what a server tells it. Wallets normally check what they can, such as proofs that a confirmed transaction is included in a block. Unconfirmed transactions, which are still waiting to be mined, have no such proof.

How the reported attack worked

Based on the reports, the attack went in these steps:

The user created a legitimate payment.
A malicious server held it back from the network instead of passing it on.
The server sent the wallet a different transaction that spent the same coins to an address controlled by the attacker. It carried invalid signatures, so the network would have rejected it, but vulnerable versions did not check the signatures before showing it in the history as a normal pending payment.
The payment stayed unconfirmed. In one reported case the fake transaction had a zero fee, which looked like an ordinary "stuck" payment. The developers reportedly suspected this was meant to push the user to raise the fee.
When the user used Replace-by-Fee (RBF) to increase the fee, the wallet signed a new, valid version of the transaction. In this case, the valid version paid the attacker.

Reports also say the attacker's receiving addresses ended with the same four characters as the real destination, which made the swap harder to notice if someone only compared the end of the address.

Why a fee bump is the sensitive moment

RBF is a legitimate feature. It lets a sender replace an unconfirmed transaction with a higher-fee version so it gets mined faster. For that to happen, the wallet has to sign a new transaction, and the user usually approves it quickly because the goal seems routine. If the transaction being replaced is not the one the user actually created, that routine approval becomes the point where funds are lost. A related explanation of the feature is in what Replace-by-Fee is and how it can be abused.

What the developers changed

According to the reports, Electrum 4.8.3 verifies the signatures of unconfirmed transactions that spend the wallet's own coins and rejects invalid ones before they enter the local history. One report notes that incoming unconfirmed transactions are not covered by this check. Reports also say users who connect only to trusted servers, including their own, were not exposed to this particular attack.

What you can do

This applies to any wallet, not only Electrum:

Update from the official source. If you use Electrum, update to the fixed version, download it only from the official site and check the signature of the download as the developers recommend.
Compare the whole address. Check the full destination address and the amount before signing, including when you are only changing the fee. Do not rely on the first and last characters alone. See look-alike addresses.
Be careful with a stuck payment you do not recognize. If your history shows a pending payment with a very low or zero fee that you did not expect, do not bump it. See what helps when a transaction is stuck.
Check outside your wallet. Look up the transaction ID on a public block explorer. A payment that the wallet shows as sent but the explorer cannot find deserves a second look. See how to verify a payment yourself.
Verify on a separate screen when you can. If you use a hardware wallet, check the address shown on the device itself. See verifying a receive address on a hardware wallet screen.
Consider your own server. Running or choosing a server you trust reduces what an unknown server can do, though it takes more effort.

These steps lower the risk. They do not remove it.

If something looks wrong

Stop approving anything and do not increase fees. Check the transaction on a block explorer, update the software from the official site and ask the wallet's official support channels, not strangers who offer help in comments or private messages. Recovery offers that follow a loss are a common second trap.

What is not known

The total amount stolen, the number of affected users and the identity of the servers have not been disclosed. Reports also differ on the severity label, and it is not clear whether other wallets with a similar design are affected. Check the developers' own advisory and release notes for the latest information.

Sources

This article is for general information only and is not financial advice.