Electrum, one of Bitcoin’s longest-running lightweight wallets, released version 4.8.3 on October 24, 2026, after developers confirmed that a high-severity flaw was already being exploited by malicious servers.
The vulnerability allowed an attacker controlling an Electrum server to intercept a user’s freshly signed payment, suppress its broadcast to the Bitcoin network, and replace it in the wallet’s local history with a conflicting transaction that redirected the same coins to an address the attacker controlled.
Because older clients did not verify signatures on unconfirmed transactions spending the wallet’s own coins, the substituted payment appeared as an ordinary pending transfer.
The attack becomes complete only when the wallet owner takes an additional step.
If the user later raises the fee through Replace-By-Fee (RBF), the software signs and broadcasts the substituted transaction rather than the original one.
The result is a fully valid payment that moves funds exactly where the attacker intended.
Private keys themselves are never compromised; the theft occurs because the user unknowingly authorizes a different set of outputs.
Attackers added two practical refinements that made the switch harder to notice.
Destination addresses were generated so that their final four characters matched the legitimate recipient, the portion of an address most users glance at during a quick check.
In at least one reported case the fraudulent transaction carried a zero fee, creating the appearance of a stalled payment and giving the owner a clear reason to initiate the fee increase that completed the theft.Electrum received two private reports.
On October 11 a user noticed that a newly broadcast payment had been replaced in the wallet history by a different transaction; the fee-bump vector was not yet understood.
On October 18 a second user reported losing funds after raising the fee on what turned out to be the attacker’s substitute.
Developers confirmed that some public servers were already conducting the attack in the wild.
Clients that connect exclusively to servers the user trusts, including self-hosted Electrum servers, are not exposed to this particular technique.
The 4.8.3 update closes the gap by requiring the client to verify signatures on any unconfirmed transaction that spends coins belonging to the wallet before the transaction is added to local history.
Invalid substitutes are rejected and never displayed.
Until every installation is upgraded, the practical defense is manual verification: before signing any transaction, including a fee bump, users should confirm both the full destination address and the exact amount.
Downloads should be obtained only from the official Electrum website and their cryptographic signatures checked.
The episode illustrates a long-standing tension in lightweight Bitcoin clients. Electrum deliberately trusts its chosen server for mempool data and fee estimates, a design choice documented for years.
That trust is what made the substitution possible.
By adding client-side signature checks on outgoing unconfirmed transactions, version 4.8.3 reduces the surface without requiring every user to run a full node.
The broader lesson remains unchanged: a wallet that protects keys can still be induced to request a perfectly valid signature for a payment its owner never meant to send. Immediate upgrades, careful address review, and preference for trusted servers remain the most effective immediate protections.
