Electrum 4.8.3 Patches High-Severity Flaw Allowing Malicious Servers to Redirect Funds via Fee-Bump Transaction Substitution

The vulnerability demonstrates how structural shortcuts in lightweight client architecture allow untrusted infrastructure to trick end users into signing irreversible balance transfers.

• The flaw enabled transaction replacement: Malicious public servers suppressed legitimate pending transfers and injected zero-fee substitute transactions sharing partial address characteristics with the intended recipient.
• The exploit triggered on fee-bumps: When users attempted to accelerate the stalled, forged entry by adjusting fees, the client generated and signed a valid transaction directing funds to an attacker-controlled address.
• Electrum deployed an emergency patch: Version 4.8.3, released on October 24, 2026, forces cryptographic signature verification on all unconfirmed inputs spending wallet-owned coins before displaying them.

• Lightweight clients sacrifice node independence for speed: Electrum operates as a Simplified Payment Verification (SPV) client that queries remote servers for mempool activity to avoid requiring users to host complete transaction ledgers.
• Mempool verification lacked cryptographic checks: While confirmed transactions receive mathematical proof against the chain, prior versions accepted unconfirmed incoming data into the visual transaction history without verifying input signatures.
• Attacks occurred actively in production: Developers confirmed 2 distinct user incident reports between October 11 and October 18, 2026, with 1 confirmed loss resulting from the advisory cataloged under GHSA-6jp4-8v48-cc5v.

• Suppression and Injection: When a user attempted a transfer, the rogue server suppressed the broadcast of the legitimate transaction. In its place, the server returned a crafted, zero-fee unconfirmed transaction.
• Visual Mimicry: The rogue entry used an address crafted with an identical suffix to the user’s intended destination, reducing the likelihood of detection during a casual visual inspection of the transaction history.
• Induced Execution: Because the rogue transaction paid zero fees, it remained indefinitely unconfirmed. When the operator clicked the standard wallet prompt to bump the transaction fee, the client treated the malicious server-supplied template as the base transaction.
• Legitimate Authorization: The wallet rebuilt the transaction using the attacker's recipient address, applied a valid fee, and prompted the operator to sign it. Because the operator believed they were merely paying a higher miner fee to accelerate their original outbound payment, they authorized the cryptographic signature. Once broadcast, the network confirmed an irreversible transfer directly to the attacker.

• Self-custody treasury operators using default network settings: Teams connecting hardware or desktop wallets to random public Electrum servers face direct exposure when adjusting pending transfers.
• Crypto-native finance desks managing active settlements: High-volume desks that routinely use fee-bumps during network congestion risk authorizing fraudulent outputs if transaction verification is automated or visually abbreviated.
• Private node operators running dedicated infrastructure: Users pointing their clients exclusively to self-hosted or trusted internal Electrum servers remain insulated, as the attack requires a compromised or hostile node in the connection loop.

• Adoption velocity of client version 4.8.3: Track the rate at which individual node operators and software aggregators update client binaries using verified GPG release signatures.
• Cross-client mempool handling reviews: Watch whether other SPV, mobile, and lightweight wallet frameworks implement identical signature verification checks on unconfirmed mempool feeds.
• Migration toward self-hosted full node connectivity: Monitor whether enterprises and active desks phase out public remote server routing in favor of private, authenticated backend nodes.