Electrum Wallet Under Attack: How a “Pending Payment” Trap Exploited Bitcoin’s Replace-by-Fee Feature to Steal Funds

A silent threat lurked inside one of Bitcoin’s most trusted wallets, and security researchers are still piecing together the damage.

In a coordinated attack that has sent ripples through the cryptocurrency community, users of the popular Electrum Bitcoin wallet found themselves staring at an unnerving sight: legitimate payments that never seemed to confirm. What appeared to be a routine network delay was, in reality, an elaborate phishing-and-exploitation scheme designed to trick users into surrendering their funds to unidentifiable attackers. The trap was set on malicious servers that intercepted wallet connections, and the trigger was a well-known but poorly understood Bitcoin feature called Replace-by-Fee. What unfolded over a period of several weeks in October is a stark reminder that even the most reputable self-custody tools remain only as secure as the ecosystem around them — and that a single moment of impatience can prove extraordinarily costly.

Electrum has long held a respected position in the cryptocurrency ecosystem as one of the oldest and most reliable lightweight Bitcoin wallets. It offers deep functionality for experienced users and newcomers alike, supporting hardware wallets, multisignature configurations, and a robust set of security features. But its reliance on public servers to broadcast and monitor transactions creates an opening that determined attackers can exploit. In this case, the attackers seized control of that connection and displayed a fabricated transaction history directly inside the wallet interface. Users saw outgoing payments marked as pending for extended periods of time, mimicking a familiar and usually harmless situation in which network congestion delays confirmation. The deception, however, was only the first layer of the attack. When users inevitably attempted to push their supposedly stuck transactions through, they unknowingly triggered a mechanism that handed their coins directly to the attacker — a final step executed by the victim’s own wallet software.

To understand how the heist worked, it is essential to understand the mechanics of Bitcoin’s unconfirmed transaction pool. When a user sends a payment, the transaction is broadcast to the network and enters what is called the mempool, where miners pick it up and include it in a block. During periods of high demand, transactions with lower fees can linger in this pending state for hours or even days. To address this, Bitcoin introduced a feature known as Replace-by-Fee, or RBF, which allows a sender to replace an unconfirmed transaction with a new version that carries a higher fee, effectively bribing miners to prioritize it. Electrum, like many wallets, offers this option directly in its interface. The attackers weaponized this convenience. When a victim opened the wallet and saw a fake payment stuck in a pending state, the natural response was to select the RBF option to speed things up. But the “pending” transaction displayed by the malicious server was not the user’s genuine payment at all — it was a fraudulent transaction created by the attacker. By choosing to replace it, the user inadvertently instructed Electrum to take that bogus transaction and sign a valid replacement, transferring the coins to an address controlled by the attacker. In essence, the victim became an unwitting accomplice in their own loss.

The sophistication of the campaign did not end with the technical exploit. In at least one reported case, the malicious transaction was deliberately submitted with no fee whatsoever, ensuring it would languish in the mempool indefinitely and appear exactly like a typical stuck payment. To reduce the chance of detection, the attackers also generated receiving addresses whose final four characters matched those of the legitimate destination address. Bitcoin addresses are long and unwieldy strings of alphanumeric characters, and many users perform a quick spot-check of only the first few and last few characters when confirming a payout. That habit proved to be a vulnerability in itself. A user who glanced at the endpoint of the address would see a match and assume everything was correct. The combination of impatience, plausible network behavior, and the psychological comfort of a matching tail made the attack extremely difficult to spot even for users who exercised a reasonable degree of caution. It serves as a brutal lesson that in cryptocurrency, where transactions are final and reversible only by consensus, partial verification is often no verification at all.

The first known report of the attack surfaced on October 11, when a user described a disturbing anomaly involving a two-of-three multisignature wallet secured by a pair of Trezor hardware devices. Multisignature wallets are typically considered one of the most secure configurations available, because they require multiple independent keys to authorize a transaction. The victim reported checking the legitimate payment on both hardware devices, receiving confirmation that the transaction was correct on each screen. Yet upon returning to the wallet’s history later, they noticed an entirely different outgoing transaction that they had never authorized. While that particular user did not report losing funds, the mere presence of an unexplained transaction in a multisig wallet raised alarms that the attack was far more sophisticated than a simple phishing page. A second and more troubling report followed on October 18, when another user disclosed that they had explicitly used the fee-raising feature on a substituted transaction and subsequently lost real money. Since that disclosure, Electrum developers have remained tight-lipped about the extent of the losses, declining to release the total amount stolen or the identity of the malicious servers involved in the operation.

In response to the escalating threat, the Electrum development team pushed out version 4.8.3 on October 24. The update introduced additional signature verification checks designed to detect unconfirmed transactions that attempt to spend coins from the user’s own wallet. Under the new protocol, the wallet validates the origin and authorization of such transactions before allowing any RBF action to proceed. This is a meaningful security improvement that closes the specific loophole exploited in the reported attacks. However, the team has issued a sobering caveat: older versions of Electrum remain vulnerable to the attack when connected to malicious servers. Because Electrum relies on a decentralized network of community-operated servers rather than a centralized infrastructure, the update alone is not sufficient to protect users who have not upgraded. The real defense requires both prompt action at the individual level and ongoing maintenance of the server ecosystem. The attack also highlights the dual-edged nature of Replace-by-Fee as a feature: what began as a practical solution for stuck transactions has become a weapon in the hands of adversaries capable of manipulating ambient trust within the network.

For the broader cryptocurrency community, this incident serves as a pointed reminder that self-custody is not a passive state. It demands constant vigilance, compulsory update hygiene, and a willingness to question what the software claims to show. Security experts recommend that users verify the full address of any destination rather than truncated versions, avoid the urge to manually bump fees on transactions that appear suspicious, and ensure their wallet software is updated to the latest available version. The Electrum episode is also part of a larger pattern of increasingly creative attacks on wallet infrastructure, from malicious browser extensions and clipboard hijackers to fake mobile applications and now server-level transaction poisoning. As the value of digital assets continues to climb, so too will the sophistication of those seeking to steal them. The attackers in this case were able to turn the wallet’s own functionality against its user, exploiting neither a mathematical flaw in Bitcoin nor a brute-force vulnerability but rather the gap between what software displays and what users believe. The open question is how many other features in the cryptocurrency ecosystem carry hidden dangers waiting for the right adversary — and how many impatient users will fall into the very trap designed for them. In the fast-moving world of digital money, the most valuable habit may simply be slowing down.