Electrum has released version 4.8.3 to address an actively exploited attack in which malicious servers substituted fake pending Bitcoin transactions, then relied on users to authorize them while increasing transaction fees. The wallet's developers disclosed the issue on October 24 and confirmed one user reported losing funds.

How the substitution worked

Electrum relies on servers for transaction history. According to its security advisory, a malicious server could withhold a newly broadcast payment and replace it in the wallet's history with a conflicting transaction directing funds to an attacker. The replacement had invalid signatures, but the wallet did not check them before displaying it as unconfirmed.

If the user manually increased that transaction's fee using Replace-by-Fee, the wallet would sign a valid replacement paying the attacker. Both reporting users said the attacker's address matched the last four characters of the intended destination. In the loss report, the substituted transaction had a zero fee, potentially encouraging a fee increase.

What the update changes

Version 4.8.3 checks signatures on unconfirmed transaction inputs belonging to the wallet before adding those transactions to local history. Binaries were released October 24, six days after the report of stolen funds.

The protection is scoped: Electrum does not validate every incoming unconfirmed transaction as a full Bitcoin node would. Developers recommend upgrading and checking destination addresses and amounts whenever signing, including fee increases. They say clients connected only to trusted servers, such as their own, are not affected by this attack.