Most wallet scams need you to make a mistake. This one waited for you to do something sensible: speed up a stuck payment.
On 24 October, Electrum, one of the oldest Bitcoin wallets, released version 4.8.3 and told all users to upgrade. The security advisory, rated high severity and covering every version before 4.8.3, says “some servers are performing this attack in the wild.” One of two users who reported it lost money.
How the trap worked
Electrum is a light wallet. It doesn’t download the whole blockchain; it asks a server what is happening, and by design it trusts that server about unconfirmed transactions. The advisory lays out what a hostile server did with that trust:
- You broadcast a real payment. The server quietly swallowed it, so it never reached the Bitcoin network.
- The server put a fake transaction in your wallet history instead, spending the same coins to the attacker’s address.
- The fake had invalid signatures, but older clients didn’t check them, so it looked like a normal pending payment.
- The fake carried a fee of about zero, so it would never confirm.
- If you then used Replace-By-Fee (RBF) to bump the fee, your wallet signed the fake for real, with valid signatures, and paid the attacker.
Step four is the bait. A payment stuck at zero fee is exactly the kind you’d want to speed up.
The first report, on 11 October, came from a user with a 2-of-3 multisig wallet who had checked the outputs on two Trezor hardware wallets before broadcasting. History then showed the full amount going to an unknown address. Their real transaction was never broadcast and was still valid. The second user, who reported on 18 October, bumped the fee and lost funds, according to the advisory’s timeline.
The original element: why four characters is a weak check
In both reports, the attacker’s address was “grinded to match the last four chars” of the real one. Many people check only the first or last few characters of an address. Here is our arithmetic on what that check is worth.
| Address type | Characters it can use | Combinations an attacker must search to match the last N |
|---|---|---|
| Legacy (starts 1 or 3) | 58 | 4 chars: 11.3 million. 6 chars: 38 billion. 8 chars: 128 trillion |
| Native SegWit (starts bc1) | 32 | 4 chars: 1.05 million. 6 chars: 1.07 billion. 8 chars: 1.1 trillion |
Each extra character you check multiplies the attacker’s work by 58 or 32. Four characters is a few million tries, which is small for a computer. Checking eight characters at each end makes a lookalike far harder to produce. The safest habit is still a full comparison, ideally on a hardware wallet screen, and every time you sign, including fee bumps.
What the fix does, and doesn’t
Version 4.8.3 now checks the signatures on unconfirmed transactions that spend the wallet’s own coins before adding them to history, per the release notes. The advisory is open about the limit: incoming transactions are still not validated this way, because a light client has no full script engine. Users who connect only to a server they trust, such as their own, were not affected.
Two practical warnings from Electrum itself: download only from electrum.org and check the GPG signature (the project doesn’t publish hashes, and says hashes add no security), and know that Windows Defender may flag a new QR-scanning file in this build, which Electrum calls a false positive for genuine signed downloads.
What it means for Indian investors
Many Indians buy bitcoin on an FIU-IND-registered exchange and move it to a self-custody wallet. That’s a reasonable choice, but it means no help desk can reverse a bad payment. India’s 30% tax on crypto gains also allows no set-off of losses, so coins lost to a scam don’t reduce what you owe on other gains. If you use Electrum on desktop or Android, upgrade before your next payment. For live prices, see our Bitcoin price page and Bitcoin price in INR.
BtcMedia verdict
A careful, fixed and openly disclosed bug, but a real lesson: the dangerous moment isn’t only sending, it’s re-signing. Treat a fee bump like a new payment and check the address in full.
FAQ
Am I affected if I use Electrum? Every version before 4.8.3 is affected unless you connect only to a server you trust. Upgrading fixes the attack described in the advisory.
I bumped a fee recently. How do I check? Look up the transaction ID on a block explorer you trust and compare the destination address in full with the one you meant to pay.
Does this affect hardware wallets? The attack fools the Electrum software. A hardware wallet shows the address you’re signing, so checking it in full on the device screen protects you.
How we calculated this: the combinations are 58 or 32 raised to the number of characters matched, using the Base58 and Bech32 character sets. Facts from Electrum’s advisory and release notes, checked 25 October 2026, 12:50 AM IST.
This is not financial advice.