Bitcoin Wallet Fixes Critical Flaw That Redirected Funds to Attackers

Bitcoin wallet Electrum patched a high-severity vulnerability this weekend that allowed rogue servers to manipulate pending Bitcoin transactions and redirect funds to attacker-controlled addresses. The flaw affects all versions before 4.8.3, which is now available.

At least one user has confirmed losing money to the exploit.

Electrum is one of the oldest Bitcoin software wallets around. The attack exploits the wallet’s trust model for unconfirmed transactions. When a user broadcasts a payment through a compromised server, the server can suppress the real transaction and inject a fake conflicting one—showing an attacker’s output address and zero fee, making the payment look stuck.

Because Electrum doesn’t verify signatures on unconfirmed transactions from the server, the spoofed transaction appears in the wallet’s history as legitimate.

When the user fee-bumps what looks like a stalled payment, they sign and broadcast a completely new valid transaction—one whose output address belongs to the attacker. The real payment was never sent; the fee-bump is the first transaction that actually hits the network, and it pays the attacker.

Electrum developer SomberNight, who published the advisory, noted that attackers can grind the fake transaction’s output address to match the last four characters of the user’s intended destination. Anyone spot-checking only the tail of a long Bitcoin address would see an apparent match.

The advisory states that “some servers are performing this attack in the wild,” backed by two user reports. A user identified as dannydeezy first flagged the suspicious server behavior on October 11; the manipulated transaction never propagated past the local server, so no funds were lost. A second user, Raju-K12, reported a confirmed loss on October 18 after fee-bumping a manipulated transaction.

The patch in 4.8.3 closes the main attack surface by verifying cryptographic signatures on wallet-owned inputs before adding any unconfirmed transaction to local history. A server can no longer inject a fake transaction touching the user’s own addresses without providing valid signatures—which the attacker cannot forge. The fix was tagged in the repository on October 23 and binaries were published the following day.

Incoming transactions from external senders—where none of the inputs belong to the user’s wallet—are still accepted without signature verification. SomberNight acknowledged this gap in the advisory, noting it would require additional work to close.

This isn’t Electrum’s first rodeo and it has dealt with malicious attacks in the past. A 2018 campaign used rogue servers to push fake update notifications, and by 2020 it had drained an estimated $25 million from Electrum users. Electrum’s open server model—anyone can run a node—is what makes this class of attack possible.

Users who connect exclusively to a server they run themselves are not affected. Anyone who cannot update immediately should manually verify output addresses and amounts before signing any transaction; Electrum 4.8.3 is available at electrum.org alongside the project’s Github.