Community Trust ScoreVerified
Electrum developers released version 4.8.3 on Oct. 24 to patch a high-severity vulnerability that allowed hackers to redirect Bitcoin payments when users attempted to increase transaction fees. The update addresses a flaw in how the wallet software processes transaction data from external servers, preventing unauthorized substitutions of pending payments.
Exploit mechanism and active attacks
The vulnerability affects Electrum versions prior to 4.8.3 and exploits the wallet’s reliance on connected servers to track unconfirmed transactions. When a user broadcasts a payment, a malicious server can withhold the legitimate transaction and supply a conflicting version that redirects funds to an attacker-controlled address. Although the fraudulent transaction initially contains invalid signatures, affected clients failed to verify these signatures before displaying the substituted transaction in the unconfirmed history. Consequently, the legitimate payment disappears from the user’s view, replaced by the manipulated transaction.
Attackers leveraged Bitcoin’s Replace-by-Fee feature to complete the theft. If a victim manually increased the fee on the substituted transaction to accelerate confirmation, Electrum generated fresh signatures authorizing the altered payment details. This action made the attacker-directed transaction valid, allowing funds to transfer without compromising the user’s private keys. In the Oct. 18 incident, attackers reportedly set the fraudulent transaction fee to zero, a tactic potentially designed to encourage the victim to raise the fee.
To increase the likelihood of user deception, attackers generated Bitcoin addresses that matched the final four characters of the intended recipients’ addresses. This manipulation targeted users who relied on partial address checks rather than verifying the full string. Electrum maintainers confirmed that some servers were actively carrying out this attack, though the company did not disclose the total amount stolen or the number of compromised wallets.
Timeline and security patch details
The disclosure followed two user complaints received by the development team. The first complaint arrived on Oct. 11 from a user who noticed an unfamiliar transaction appearing in their wallet after broadcasting a payment. The second complaint was received on Oct. 18 from a user who lost funds after attempting to accelerate a pending transfer. Both incidents involved the same address-matching technique used to disguise the fraudulent payments.
Electrum developers tagged version 4.8.3 on Oct. 23 and distributed the updated software on Oct. 24 alongside the public security disclosure. The patch introduces signature checks for wallet-owned inputs before unconfirmed transactions enter the client’s local history. This change prevents the reported substitution technique from reaching the fee-adjustment stage, ensuring that invalid transactions are not presented to the user for approval.
The advisory notes that clients connected exclusively to trusted servers, including privately operated ones, are not exposed to this specific attack vector. However, the patch does not extend signature verification to every incoming transaction. Developers advised users to download the patch from Electrum’s official website and to verify complete recipient addresses and payment amounts whenever signing transactions. The maintainers have not provided further details on the scope of the active exploitation or the identity of the malicious servers involved.
Frequently Asked Questions
Which Electrum versions are affected by the vulnerability?
The high-severity vulnerability affects Electrum versions earlier than 4.8.3. Users running older versions are advised to update immediately to prevent potential payment redirection during fee adjustments.
How did the attackers redirect Bitcoin without private keys?
Attackers used malicious servers to substitute pending transactions with fraudulent versions. When victims manually increased fees on these substituted transactions, Electrum generated new signatures for the altered payment details, making the theft valid without accessing the user’s private keys.
