- Trending
- Comments
- Latest
Electrum has patched a Bitcoin wallet flaw that let malicious servers trick users into signing away their own funds. At least one user lost bitcoin after trying to raise the fee on a stuck transaction. Electrum 4.8.3, released October 24, adds the missing signature checks, and older versions remain vulnerable.
Electrum is a Bitcoin wallet that relies on external servers to retrieve transaction information and broadcast payments. Unlike users operating a full Bitcoin node, Electrum users depend on these servers to communicate with the Bitcoin network.
That reliance created an opportunity for attackers operating malicious servers. According to the vulnerability disclosure, the wallet previously accepted information about unconfirmed transactions without adequately verifying their signatures.
By exploiting this weakness, an attacker could manipulate the transaction information displayed in the wallet. A fraudulent transaction could appear to spend the user’s Bitcoin to an attacker-controlled address, even though its signatures were invalid.
Because the wallet failed to identify the invalid signatures at the relevant stage, the substituted transaction could appear to be a legitimate outgoing payment awaiting confirmation.
This created a potentially dangerous situation for users who trusted the transaction details displayed by their wallet. A payment that appeared merely delayed could, in reality, have been manipulated before reaching the Bitcoin network.
The Bitcoin Wallet Bug did not mean that Bitcoin’s underlying blockchain had been compromised. Instead, the vulnerability involved Electrum’s handling and verification of transaction information supplied by external servers.
The distinction is important because the attack exploited the wallet’s software and its interaction with servers rather than a flaw in Bitcoin’s consensus mechanism.
The vulnerability became more serious because of its interaction with Replace-by-Fee, a Bitcoin feature that allows eligible unconfirmed transactions to be replaced with versions carrying higher transaction fees.
Users commonly rely on RBF when a payment remains unconfirmed because its original fee is too low to attract timely processing. By increasing the fee, a user can encourage the network to prioritize the replacement transaction.
However, attackers could exploit this routine process when a fraudulent transaction had aglready been inserted into an affected Electrum wallet.
When a user attempted to increase the fee on what appeared to be a stalled payment, the wallet could use the substituted bw
04b44transaction to create and sign a valid replacement. That action could authorize a payment directing the user’s Bitcoin to an address controlled by the attacker.
In one reported incident, the malicious transaction carried no transaction fee, making it appear stalled and increasing the likelihood that the user would attempt to accelerate it.
Attackers also reportedly generated destination addresses whose final four characters matched those of the intended addresses. This technique could make the fraudulent destination harder to detect when users performed a quick visual check.
The combination of misleading transaction information, a familiar fee-increase procedure and similar-looking addresses made the vulnerability particularly concerning.
The Bitcoin Wallet Bug therefore demonstrated how a routine wallet operation could become a security risk when software failed to validate transaction information correctly.
Users who assumed that a transaction displayed in their wallet had already passed the necessary security checks could unknowingly approve a payment that sent funds to the wrong destination.
The first report concerning the vulnerability was submitted on October 11 by a user operating a two-of-three multisignature Bitcoin wallet secured with two Trezor hardware devices.
The user noticed a suspicious outgoing transaction, although no financial loss was reported in that initial incident.
A second report followed on October 18. In that case, a user increased the fee on a substituted Bitcoin transaction and subsequently lost funds.
Developers have not disclosed the amount stolen or identified the malicious servers involved in the reported incidents. The available information also does not establish how many additional users, if any, were exposed to the attack.
Electrum released version 4.8.3 on October 24 to address the vulnerability. The update introduced signature verification checks for unconfirmed transactions that spend coins from the user’s wallet.
The fix is intended to prevent the wallet from accepting improperly verified transaction information in the manner that enabled the attack.
Users operating older versions remain at risk when connecting to malicious servers. Electrum’s developers recommend upgrading to the patched release and checking transaction addresses and payment amounts carefully before signing any Bitcoin transaction.
The disclosure also indicates that users connected exclusively to trusted servers, including servers they operate themselves, were not affected by the reported attack.
Nevertheless, users should not assume that a transaction is safe simply because it appears in their wallet’s history. Verifying the recipient address and the amount before approving a payment remains an important security precaution.
Copyright © 2025 - The Bit Gazette.
