Writing · October 2026

The fee bump was the theft.

A rogue server swallowed a Bitcoin payment, showed the wallet a fake in its place, and waited. The user clicked "increase fee." The wallet signed. The money went to the attacker.

On October 24, the Electrum developers published a security advisory and released version 4.8.3. I'm not writing about Bitcoin's design. I'm writing about a trust assumption that was documented, reasonable, and still got someone's money.

What the sources say

The advisory, CoinDesk and crypto.news agree on the mechanism. Electrum is a light wallet. It doesn't hold the blockchain. It asks a server what's going on, and for unconfirmed transactions it trusts the server by design. The advisory calls that documented behavior.

The attack, per the advisory, runs in five steps. The wallet broadcasts a payment. A malicious server swallows it. The server then feeds the wallet's history a conflicting transaction that pays the attacker. The wallet doesn't check that transaction's signatures, because of the light-client design. It shows the fake as an ordinary pending payment and doesn't show the real one. If the user then fee-bumps the fake with Replace-by-Fee, the wallet signs it at a higher fee. This time the signature is real.

The advisory says some servers are doing this in the wild. Two users reported it privately: one on October 11, who saw a transaction in their history they hadn't made, and one on October 18, who bumped the fee and lost money. The fix was tagged October 23 and released with the disclosure on October 24.

Both reports described the attacker's address as matching the last four characters of the real one. In the second case the fake carried a zero fee, so it looked stuck, which invites the bump.

Where the reporting thins out

The amount. CoinDesk and crypto.news both say at least one theft was confirmed. Nobody has published how much.

The scale. The advisory says two reports. It doesn't say how many servers are involved, how long this ran before October 11, or whether there are other victims who haven't come forward.

The affected versions. The advisory and crypto.news say everything below 4.8.3. CoinDesk says "earlier versions" and doesn't list them.

The fix's reach. The advisory is direct about this: the patch verifies signatures on unconfirmed transactions that spend the wallet's own coins. Incoming unconfirmed transactions aren't validated. Full coverage, it says, would need a consensus engine and recursive validation of unconfirmed parents. So 4.8.3 closes this path. It does not turn Electrum into a full node.

The check you skip

A fee bump feels like a setting. You aren't sending money, you're making a pending payment faster. But the wallet builds and signs a new transaction every time, and that transaction pays whatever the wallet thinks the original paid. If the wallet's picture is wrong, you've just signed the wrong picture.

A carpenter checks the cut against the plan, not against the last cut. The wallet history was the last cut. The plan is the address you meant to pay.

What I'd do

1. Update to 4.8.3, from the developer's own site. The advisory also says to update regularly in any case. Stale wallet software is a standing invitation. 2. Treat every fee bump as a new payment. Read the full address and the amount before you sign. Not the first few characters. Not the last four. An attacker who can grind four matching characters is counting on a glance. 3. Check the address on your hardware wallet's own screen. If the device shows a destination you don't recognize, stop. The screen on the device is the one thing the server can't edit. 4. Run your own server, or only trust one you control. The advisory says clients connected to trusted servers, such as your own, are not affected. That's the real fix for this class of problem: choose who you trust instead of inheriting it.

The boring conclusion

The wallet did what it was designed to do. The design assumed the server was honest. Some weren't. Every light client has a trust boundary somewhere, and the useful question is where yours is and who's standing on the other side.

Verify everything, especially the transaction you didn't build.

— Jon Tetreault, October 2026. The habits, tools, and checks behind this piece are what I teach in Crypto Security Mastery.