Electrum Patches Server-Side Bitcoin Theft Flaw After Confirmed Loss

Bitcoin wallet Electrum shipped version 4.8.3 on October 24, patching a high-severity flaw that let malicious servers replace pending transactions with fakes and redirect user funds to attacker-controlled addresses. At least one user has confirmed a loss, reported on October 18, after fee-bumping a server-manipulated transaction. The vulnerability affects every version prior to 4.8.3.

The attack exploits how Electrum, one of the oldest Bitcoin software wallets in operation, handles unconfirmed transactions. When a user broadcasts a payment through a compromised server, that server can suppress the genuine transaction and inject a conflicting fake one. The spoofed entry displays an attacker's output address with a zero fee, so the payment appears stuck. The wallet does not verify signatures on unconfirmed transactions received from servers, so the fake appears in the history as legitimate.

How did the theft work?

The scam completes when the user tries to rescue a seemingly stalled payment. Fee-bumping what looks like a stuck transaction means signing and broadcasting an entirely new, valid transaction — one whose output address belongs to the attacker. The original payment never reached the network; the fee-bump is the first transaction that actually propagates, and it pays the attacker.

Electrum developer SomberNight, who published the advisory, added a detail that makes visual checks unreliable. Attackers can grind the fake transaction's output address so its last four characters match the user's intended destination. A user who spot-checks only the tail of a long Bitcoin address would see an apparent match and sign anyway. The takeaway: a partial address check is no defense against an adversary who controls the server.

Who was hit?

The advisory states plainly that "some servers are performing this attack in the wild," and it cites two user reports. A user identified as dannydeezy flagged the suspicious server behavior on October 11; the manipulated transaction never propagated beyond the local server, so no funds were lost in that case. A second user, Raju-K12, reported a confirmed loss on October 18 after fee-bumping a manipulated transaction. Two reports establish that the attack is live; they do not establish how widespread it is, and the advisory offers no aggregate loss figure.

What does the patch actually fix?

The fix in 4.8.3 verifies cryptographic signatures on wallet-owned inputs before any unconfirmed transaction enters local history. A server can no longer inject a fake transaction touching the user's own addresses without valid signatures — which the attacker cannot forge. Developers tagged the fix in the repository on October 23 and published binaries the following day.

The patch leaves a gap, and SomberNight acknowledged it in the advisory. Incoming transactions from external senders — where none of the inputs belong to the user's wallet — are still accepted without signature verification. Closing that hole, he noted, requires additional work. In plain terms: the front door is now locked, but a side entrance remains open.

Is this new for Electrum?

No. A 2018 campaign used rogue servers to push fake update notifications, and by 2020 it had drained an estimated $25 million from Electrum users — roughly the annual budget of a mid-sized security firm, taken from wallet holders. The root cause is structural: Electrum's open server model lets anyone run a node, and that openness is what makes this class of attack possible. Users who connect exclusively to a server they run themselves are not affected.

For those who cannot update immediately, the advisory's guidance is manual: verify output addresses and full amounts before signing any transaction. Electrum 4.8.3 is available at electrum.org and on the project's GitHub. The residual gap on externally sourced transactions means server-trust questions will not be closed with this release alone.