Electrum says version 4.8.3 fixes a flaw that allowed malicious servers to misrepresent some pending Bitcoin transactions. Developers disclosed two incidents, one involving lost funds, but have not said how much was lost or how many users were affected.
- Electrum says versions before 4.8.3 are affected.
- The flaw involved unconfirmed outgoing transactions.
- Users had to approve the fraudulent payment for funds to be spent.
- The scale of the attacks is unknown.
How the reported attack worked
In its security disclosure, Electrum’s developers said malicious servers could interfere with a pending outgoing transaction and show the wallet a different payment. A user trying to raise the transaction fee could then be tricked into signing a payment to an attacker-controlled address.
Replace-by-Fee (RBF) allows a wallet to replace an unconfirmed transaction with one that offers a higher fee, depending on the wallet’s behavior and Bitcoin network policy. The replacement does not have to preserve the original payment’s outputs. It can send Bitcoin to different destinations. Anyone trying to raise a fee should check the destination and amount before approving the replacement.
A server could not spend the user’s Bitcoin on its own. The reported attack relied on showing the user misleading transaction details, then getting them to approve the fraudulent payment. Electrum said the attacker-controlled addresses shared the final four characters of the intended addresses. That short suffix is not enough to verify a Bitcoin destination.
Two disclosed incidents
Electrum’s developers described two incidents reported privately. In one, a user said a transaction shown in the wallet’s history did not match the payment they had submitted. The case involved a two-of-three multisignature wallet with two Trezor devices. The intended transaction had 31 inputs and one output.
According to the developers, investigators found that all 62 signatures were valid for the original payment but invalid for the substituted transaction. The substitute sent nearly all the Bitcoin to a lookalike address and returned a small amount to the wallet. The original transaction had not reached the public Bitcoin network.
The disclosure does not say the first user lost funds. It describes a mismatch and a substituted transaction. The original payment had not been broadcast to the network.
In the second incident, a user said they lost funds while trying to increase a transaction fee. The fraudulent transaction had a zero fee. Developers suspected the fee was set that way to prompt the user to raise it, but they presented this as a possible motive, not a proven one.
Electrum’s disclosure did not specify the year of the incident dates, so they are omitted here. Developers said some servers were carrying out the attack but did not say how many were involved, how much was lost or whether there were other victims.
What Electrum 4.8.3 changes
Electrum says version 4.8.3 adds signature checks for unconfirmed transactions that spend coins controlled by the wallet. The checks are designed to stop the wallet from accepting a substituted outgoing transaction if its signatures are not valid for that transaction.
This is a targeted safeguard. It does not turn Electrum into a full node or make the wallet independently verify every piece of information servers provide. The new checks cover the specified unconfirmed outgoing transactions, not incoming ones. An unconfirmed transaction is still pending, not settled on the Bitcoin network.
Electrum uses Simplified Payment Verification (SPV) to check confirmed transactions without downloading and independently validating the entire blockchain. Pending transactions have not been confirmed, so seeing one in a wallet does not prove that the payment has settled.
What users should do
Electrum says every version before 4.8.3 is affected. Users with older versions should upgrade through Electrum’s official channels and verify that the software is authentic. Check Electrum’s official release information for the current supported version. Don’t assume 4.8.3 is still the latest.
Before approving a payment, check the full destination address and amount on the device that will sign the transaction, if it displays those details. Be especially careful when replacing a transaction to increase its fee. A hardware wallet protects private keys, but it cannot stop you from approving a payment to the wrong address.
If you cannot upgrade right away, Electrum advised users to check the full address and amount before signing. Developers also said that connecting only to trusted servers, including a server you operate yourself, avoids this particular malicious-server attack. It does not remove other wallet, device or operational risks.
Why the server relationship matters
Electrum is a lightweight wallet. It relies on external servers for some network information rather than independently validating blocks and transactions like a full Bitcoin node. That can make the wallet more convenient, but users should know which checks the wallet performs itself and which information comes from a server.
The flaw does not mean lightweight wallets are inherently unsafe, or that running a full node is practical for everyone. It does show why software updates and careful transaction checks matter. A pending payment is not final, and no wallet should be a reason to approve transaction details blindly. Bitcoin network
Key questions and answers
-
Which Electrum versions were affected?
Electrum’s disclosure identifies versions before 4.8.3. Check the official release information for the current supported version.
-
Does RBF itself redirect Bitcoin payments?
RBF allows an unconfirmed transaction to be replaced, and the replacement can have different outputs. The reported attack involved misleading a user during that process. It was not an automatic feature of RBF.
-
Could a malicious server spend Bitcoin without the user’s approval?
Not in the attack Electrum described. The reported theft required the user to approve the fraudulent transaction.
-
How much Bitcoin was lost?
Electrum did not disclose the total, the number of affected users or the number of malicious servers. Developers described two reports, one involving lost funds. Bitcoin rebounds
