In 30 seconds

Electrum, one of the oldest Bitcoin wallets, has shipped an emergency patch for a critical flaw that attackers have reportedly already used in the wild. The vulnerability, tracked as CVE-2026-117601 with a severity score of 9.3 out of 10, reportedly let a malicious wallet server secretly swap a pending Bitcoin transaction for a fraudulent one, so a routine fee increase could send coins to an attacker's address instead. Every version before 4.8.3 is said to be affected, and the message from the disclosure is blunt: update the wallet now.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What happened
According to a security post published on November 17, 2026, the attack starts inside the wallet's own history. A malicious server replaces the pending, unconfirmed transaction the user sees. When the user tries to speed it up with Replace-by-Fee, or RBF, a standard feature that lets you resend a stuck transaction with a higher fee, the replacement they sign is actually a payment to the attacker. The user thinks they are paying a fee; the coins leave for an address they never chose.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
The same report says Electrum confirmed that malicious servers exploited the flaw in the wild, and that at least one user has come forward reporting stolen funds. Those claims arrive through a single third-party account, so the exploitation details should be read as reported rather than independently verified.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Why it matters
This bug matters because it turns the wallet's own plumbing into the weapon. Electrum relies on a network of remote wallet servers to fetch balances and transaction data, and a user has no easy way to tell an honest server from a hostile one. The attack also hides inside a normal, helpful moment: bumping the fee on a stuck payment is something Bitcoin users do all the time. On the described mechanics there is no glaring error message, just a signed transaction that looks like the user's own.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
With a reported CVSS score of 9.3 and every release before 4.8.3 said to be affected, the exposure is broad on paper: anyone running an older Electrum and touching a pending transaction fits the attack's requirements.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What to do
Update Electrum to version 4.8.3 or later before doing anything else with the wallet. The disclosure urges exactly that, and with all earlier versions reportedly vulnerable there is no good reason to stay behind.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Until the update is in place, treat fee-increase prompts on pending transactions with suspicion, since that is the precise action the attack hijacks. If a pending transaction looks unfamiliar or a fee bump request appears out of nowhere, stop and verify the destination address through another source before signing anything.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Confirmed and still uncertain
What is on the record so far, on the strength of one report: the flaw is assigned CVE-2026-117601 with a CVSS score of 9.3, it sits in all versions before 4.8.3, a patch exists, malicious servers have reportedly exploited it, and one user says funds were stolen.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What remains unknown: how many users were hit, how much Bitcoin was taken, which servers were hostile, and whether the single victim report reflects the true scale. The evidence batch contains no vendor advisory, no CVE database entry, and no independent confirmation, so the picture could still shift in either direction.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What people are saying
The public chatter in this batch comes from one voice: DarkWebInformer, a security-focused X account, which framed the flaw as critical and actively exploited. The post also relays two other actors, Electrum, which reportedly confirmed exploitation in the wild, and an unnamed user who reported stolen funds. Neither of those has spoken directly in the evidence available here.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Evolution
The timeline, as far as a single report can carry it: the flaw sat in every Electrum version released before 4.8.3, malicious servers then began exploiting it, and the patch plus public disclosure arrived with the November 17, 2026 post. Each step is reported rather than independently dated, and questions like when exploitation first started remain open.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Reach
1 independent groups, 1 updates, and 6 engagements.
Technical detail
The mechanics as described: Electrum clients query remote servers for wallet history instead of downloading the full blockchain, and a malicious server can lie about that history by replacing a pending transaction with a crafted one. The flaw, CVE-2026-117601, scored 9.3 on CVSS, becomes dangerous at the moment the user invokes Replace-by-Fee, or RBF, to bump a fee: the replacement transaction they sign redirects funds to attacker-controlled addresses. Version 4.8.3 is the fixed release.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Sources and evidence
The entire evidence base is one item: an X post from DarkWebInformer published November 17, 2026, which names the CVE, the CVSS score, the affected versions, and the reported in-the-wild exploitation, and carries a screenshot. That is enough to justify urgent caution, but every claim in this story currently traces back to that single account. A vendor advisory, a CVE database entry, or a second independent source would materially strengthen the record.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Sources
- DarkWebInformerx.com · DarkWebInformer · x


