Bitcoin wallet bug let rogue servers steal funds when users tried to speed up payments

Electrum’s Replace‑by‑Fee Vulnerability: How Rogue Servers Stole Bitcoin

A recent security issue in the popular Electrum Bitcoin wallet exposed users to a subtle but dangerous attack. By exploiting how the wallet handled unconfirmed transactions, malicious servers could swap a legitimate pending payment with a fake one. When users later tried to accelerate the transaction using Replace‑by‑Fee (RBF), they unknowingly signed a replacement that sent their coins to an attacker‑controlled address. At least one theft has been confirmed, prompting an urgent patch.

---

What the bug allowed

Electrum, unlike a full Bitcoin node, relies on external servers for transaction history and broadcasting. Prior to the fix, the wallet trusted these servers to report pending transactions without verifying the cryptographic signatures of those transactions. An attacker controlling a server could:

1. Intercept a user’s outgoing transaction before it reached the network.
2. Replace the pending transaction in the wallet’s UI with a counterfeit one that spent the user’s coins to an address they control.
3. Leave the fake transaction appearing "stuck" (often with a zero or very low fee) so the user would consider using RBF to raise the fee.
4. When the user selected RBF, Electrum would sign a new transaction that validated the attacker’s output, completing the theft.

The attack leveraged two Electrum features:

• RBF – a legitimate mechanism that lets users replace an unconfirmed transaction with a higher‑fee version.
• Lack of signature verification for unconfirmed, wallet‑originated spends.

Real‑world impact

Two reports surfaced in October 2026:

• First case (Oct 11) involved a two‑of‑three multisig wallet using Trezor hardware devices. The user saw a different outgoing transaction in the wallet history but did not lose funds in that instance.
• Second case (Oct 18) described a user who raised the fee on a substituted transaction and subsequently lost Bitcoin. The exact amount was not disclosed, but the incident confirmed that the vulnerability could be weaponized.

Developers have not identified the malicious servers or quantified the total loss, but the confirmed theft underscores the risk of trusting unauthenticated server data.

The fix and immediate steps

Electrum responded quickly, releasing version 4.8.3 on Oct 24, 2026. The update adds:

• Signature checks for any unconfirmed transaction that spends the user’s own coins.
• Stricter validation of transaction data received from servers.

Users on older versions remain vulnerable when connected to compromised servers. To protect yourself:

1. Upgrade to Electrum 4.8.3 or later immediately.
2. Verify addresses and amounts manually before signing, especially when using RBF.
3. Connect only to trusted servers – you can configure Electrum to use your own node or a vetted public server.
4. Consider hardware‑wallet signing for high‑value transactions, as the device will display the exact output addresses.

---

Lessons for the broader crypto ecosystem

The incident highlights a recurring theme in cryptocurrency security: reliance on third‑party infrastructure can introduce attack vectors that bypass the underlying blockchain’s guarantees. While Bitcoin’s consensus rules remain sound, wallet software must enforce strict validation of all data, even before a transaction reaches the network.

Developers of lightweight wallets should:

• Implement full signature verification for any transaction they construct or display.
• Offer transparent server selection and make it easy for users to run their own trusted nodes.
• Provide clear warnings when RBF is used, reminding users to double‑check destination addresses.

For users, the key takeaway is vigilance. Even well‑known wallets can have hidden flaws, and the convenience of remote servers comes with trade‑offs. Regularly updating software and limiting exposure to unknown servers are simple but effective defenses.

---

Bottom line

Electrum’s RBF bug demonstrates how a seemingly minor validation oversight can be turned into a lucrative theft vector. The swift patch mitigates the risk, but the episode serves as a reminder that crypto security is a shared responsibility between developers, service providers, and end‑users. Stay updated, verify transactions, and prefer trusted server connections to keep your Bitcoin safe.