Electrum, one of the longest-running Bitcoin wallets, released version 4.8.3 on Saturday and told users to upgrade immediately. The update fixes a flaw that let a malicious server swap a legitimate outgoing payment for an attacker's transaction. That fake transaction could then become a real theft once the user tried to speed it up by raising the fee. Developers say this was not a theoretical risk. At least one user lost bitcoin this way.

Every version before 4.8.3 is affected, according to Bitcoin.com News' report on the patch. The bug is tracked in GitHub security advisory GHSA-6jp4-8v48-cc5v. Coverage describes the severity differently: Bitcoin.com calls it high-severity, while bloomingbit's report calls it critical. Both carry the same advice: update now.

Why Electrum trusts servers at all

Electrum is a "lightweight" wallet. It does not download and check the whole Bitcoin blockchain itself. Instead, it connects to outside Electrum servers that give it transaction history and fee estimates, and that broadcast its payments to the network.

Electrum does run its own checks on transactions that are already confirmed, meaning included in a block. Unconfirmed transactions, which are waiting in the queue for a block, were handled differently. Older versions accepted some of these without checking their digital signatures. A signature is the cryptographic proof that the owner of the coins approved the spend.

That gap is what the attack used. A server that wanted to cheat could hold back a real payment instead of broadcasting it, then hand the wallet a different transaction that spent the same coins to an address the attacker controlled. The swapped transaction had invalid signatures, so the Bitcoin network would never accept it. Electrum still showed it as a normal pending payment.

How a fee bump turned a fake payment into a real theft

On its own, a transaction with bad signatures cannot move any money. The theft happened when the user tried to fix what looked like a stuck payment.

Bitcoin has a feature called Replace-By-Fee (RBF). It lets a sender rebroadcast an unconfirmed payment with a higher fee so miners pick it up sooner. To do that, the wallet builds a new version of the pending transaction and asks the user to sign it.

If the "pending transaction" was the attacker's substitute, the user ended up signing a properly authorised payment to the attacker. In the words of Bitcoin.com's write-up, the wallet protected the user's private keys but could still be tricked into requesting a valid signature for a payment the owner never meant to make.

The attackers took steps to make this more likely to work:

  • Look-alike addresses. They used receiving addresses whose last four characters matched the intended recipient's, so a quick glance at the end of the address would not catch the swap.
  • Zero-fee bait. At least one fraudulent transaction carried no fee at all. That seems designed to make the payment look stuck and prompt the victim to bump the fee, which is exactly the step the theft needed.

Two reports, one confirmed loss

Electrum's developers got two private reports. On 11 October, a user going by dannydeezy reported that transactions were being substituted, though how the fee bump fit in was not yet fully understood. On 18 October, a user named Raju-K12 reported losing funds after approving a fee increase.

The second report showed the flaw was being actively exploited. The sources do not say how many users were affected or how much bitcoin was taken. They confirm only that funds were stolen.

What the patch changes

The fix, made in commit 90fe308, makes Electrum check signatures on any unconfirmed transaction that spends coins belonging to the wallet. A transaction with invalid signatures is now rejected before it reaches the wallet's local history. A malicious server can no longer plant a fake payment for the user to bump later.

Users who connect only to trusted Electrum servers they run themselves are not exposed to this particular attack, because the attack depends on a dishonest server. Most people use the default public servers, though, and those are run by third parties.

What users should do now

  • Update to 4.8.3. Download it only from electrum.org and verify the release's cryptographic signatures before installing. A security scare is a common time for fake "update" downloads to appear.
  • Check the whole address before signing. Until you have updated, compare every destination address and amount in full before approving any transaction, and that includes fee bumps. Matching the last few characters is not enough.
  • Look over recent fee bumps. If you raised a fee on an older version, compare the address the bumped transaction actually paid with the address you meant to pay.
  • Think about which servers you use. Running your own Electrum server, or connecting only to servers you trust, takes away the leverage this attack relied on.

The flaw also affects how fee bumps should be treated more generally. Many users see RBF as routine housekeeping, not a new payment that needs the same care. This attack relied on that habit.

What to watch

  • The full advisory. GHSA-6jp4-8v48-cc5v may be expanded with more technical detail, including whether specific malicious servers were identified.
  • Scale of losses. Only one confirmed loss has been described so far. Further victim reports or on-chain tracing could show how widely the attack was used.
  • Other wallets. Watch whether other lightweight wallets that accept unconfirmed data from servers check their own handling of RBF transactions.
  • Update uptake. Older Electrum installs stay exposed until they are updated, so attacks could continue against users who don't upgrade.