SecurityDeveloping

Electrum Bitcoin wallet issues emergency patch after server-based theft exploit

Version 4.8.3 adds signature checks to block fake pending transactions; at least one user confirmed lost funds

By LineZotpaper AI staff

Published26 October 2026

Updated26 October 2026

Read Time2 min

Sources3 outlets

Follow this storyHear when it moves

Illustration: Electrum Bitcoin wallet issues emergency patch after server-based theft exploit

Electrum, one of Bitcoin's oldest software wallets, released an emergency patch on Oct 24 after a critical vulnerability allowed malicious servers to trick users into signing over funds when attempting to speed up payments, with developers confirming at least one theft.

The high-severity flaw, affecting Electrum versions prior to 4.8.3, exploits the wallet's reliance on external servers to track unconfirmed transactions. Unlike a full Bitcoin node, Electrum does not independently verify transaction data from these servers, opening the door for a substitution attack.

According to a security disclosure published by the developers on Oct 24, a malicious server can suppress a user's legitimate broadcast and inject a fake conflicting transaction that sends coins to an attacker-controlled address. The fake transaction initially carries invalid signatures, but Electrum does not check them before displaying it as pending. The trap is sprung when the user employs Bitcoin's Replace-by-Fee feature to increase the fee on what appears to be a stalled payment. Electrum then signs a valid replacement that directs the funds to the attacker.

The developers received two reports in October. A user on Oct 11 noticed a suspicious transaction after broadcasting a legitimate payment but did not lose funds. A second user on Oct 18 reported losing money after fee-bumping a manipulated transaction. The amount stolen has not been disclosed. The advisory states that "some servers are performing this attack in the wild."

Electrum 4.8.3, tagged on Oct 23 and distributed the following day, closes the main attack vector 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 valid signatures. The patch does not extend signature verification to incoming transactions from external senders, a gap developers said would require additional work.

Electrum developer SomberNight noted that attackers could grind the fake transaction's output address to match the last four characters of the intended destination, making the substitution harder to spot during a quick check.

Users are urged to upgrade to Electrum 4.8.3 from the official website and to verify complete recipient addresses and payment amounts before signing any transaction. Those connected exclusively to trusted servers, including their own, were not exposed to this attack.

RSS

The Daily Edition

The front page in your inbox each weekday morning: the lead, the picks, and why each one earned its place.

Analysis

Why This Matters

Electrum users who rely on public servers are vulnerable to having their funds silently redirected when they attempt to speed up a pending transaction
The attack highlights the risk of trusting third-party infrastructure in Bitcoin wallets and the dangers of features like Replace-by-Fee when combined with insufficient validation
While patched, earlier versions remain exploitable; users who delay upgrading risk losing funds if they connect to malicious servers

Background

Electrum is a lightweight Bitcoin wallet that delegates transaction history and broadcasting to external servers, unlike full-node clients that independently verify all data. This trust model has been exploited before: a 2018 campaign used rogue servers to push fake update notifications, and by 2020 attackers had stolen significant sums through similar phishing attacks. The current flaw is the first documented case of a server injecting a fake replacement transaction to redirect fee-bump attempts.

Key Perspectives

Electrum developers: Confirm at least one confirmed theft and have released version 4.8.3 adding signature checks for wallet-owned unconfirmed transactions; recommend upgrading and manually verifying addresses Affected users (dannydeezy, Raju-K12): Two reports filed; the first noted a suspicious transaction without loss, the second reported a confirmed loss after fee-bumping a manipulated payment

What to Watch

Whether additional thefts are reported as the disclosure becomes public and attackers may accelerate activity before users upgrade
Whether the remaining gap on unverified incoming transactions is addressed in a future release
Potential for similar vulnerabilities in other lightweight wallets that rely on untrusted third-party servers

Sources

Bitcoin Wallet Fixes Critical Flaw That Redirected Funds to Attackers · Decrypt
Bitcoin wallet bug let rogue servers steal funds when users tried to speed up payments · CoinDesk
Hackers found a way to steal Bitcoin without private keys · CryptoSlate

Checked

12 claims in this story checked against 3 sources: 10 supported.

Show each claim

Partly supportedElectrum issued an emergency patch after a server-based theft exploit.Decrypt: “Bitcoin wallet Electrum released version 4.8.3 on October 24 with a patch for a high-severity exploit”
Partly supportedThe vulnerability was critical.Decrypt: “a patch for a high-severity exploit”
SupportedAt least one user confirmed losing funds in the attack.Decrypt: “At least one user confirmed losing funds on October 18 after fee-bumping a server-manipulated transaction.”
SupportedThe developers disclosed the vulnerability on Oct. 24.CryptoSlate: “The developers disclosed the vulnerability on Oct. 24, confirming that malicious servers had exploited the weakness”
SupportedA malicious server can suppress a legitimate broadcast and supply a conflicting transaction directing funds to an attacker-controlled address.CryptoSlate: “a malicious server can withhold the transaction from the network and instead supply a conflicting version that redirects the funds to an attacker-controlled address.”
SupportedThe substituted transaction initially has invalid signatures, which Electrum fails to check before showing it as pending.CryptoSlate: “The fraudulent transaction initially contains invalid signatures, meaning it cannot be processed as a legitimate payment. However, affected Electrum clients failed to verify those signatures before displaying the substituted transaction in the wallet's unconfirmed history.”
SupportedUsing Replace-by-Fee on the substituted transaction causes Electrum to sign a valid replacement that sends funds to the attacker.CryptoSlate: “If the victim manually increases the fee on the substituted transaction, Electrum generates fresh signatures authorizing its altered payment details.”
SupportedThe Oct. 11 user noticed suspicious activity after broadcasting a payment and lost no funds.CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data: “The first report, submitted Oct. 11, involved a two-of-three multisignature wallet using two Trezor hardware devices. The user had checked the legitimate payment on both devices but later noticed a different outgoing transaction in the wallet's history (that user did not report losing funds).”
SupportedA second user reported losing money on Oct. 18 after fee-bumping a manipulated transaction.Decrypt: “A second user, Raju-K12, reported a confirmed loss on October 18 after fee-bumping a manipulated transaction.”
SupportedThe advisory states that “some servers are performing this attack in the wild.”Decrypt: “The advisory states that “some servers are performing this attack in the wild,” backed by two user reports.”
SupportedElectrum 4.8.3 was tagged on Oct. 23 and distributed on Oct. 24; it checks signatures on wallet-owned inputs before adding unconfirmed transactions to local history.Decrypt: “The fix was tagged in the repository on October 23 and binaries were published the following day.”
SupportedThe patch does not verify signatures on incoming transactions from external senders, and developers said closing that gap requires additional work.Decrypt: “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.”