News Wallets and security Bitcoin basics

BTCPay Server thefts: an update alone is not enough

BTCPay Server said on 2 November 2026 that hot-wallet thefts affected servers running version 2.4.1 or earlier. Its recovery guidance goes beyond installing an update: exposed operators should move to a clean server with a new wallet and replace potentially compromised credentials. The project said it had seen no impact from these attacks on servers already running version 2.4.2 or later when the initial warning was issued.

Checked on 6 November 2026.

Navy server with an open drawer of orange coin discs beside a shield
Illustration: a payment server, hot wallet and protective shield. AI-generated conceptual artwork, not a depiction of the attack.

The incident concerns software that businesses around the world use to accept payments. It is not an announcement that the Bitcoin network was breached. For a business in Israel, the practical questions are whether it runs BTCPay Server, which version was installed at the relevant time and where its spending keys were stored. Holding bitcoin alone does not put someone in the affected group described by the project.

What BTCPay Server does, and what the server holds

BTCPay Server is open-source payment-processing software that a business can host on infrastructure it controls. It generates payment requests, tracks incoming funds and helps manage transactions without requiring a central payment processor to hold the money. Operators can use a wallet whose keys live on the server or arrange for signing to happen elsewhere. That choice helps determine what an intruder could do after gaining access.

A hot wallet keeps the keys needed to sign transactions in an online environment. The convenience is straightforward: payments and refunds can be handled without reaching for a separate device each time. But the computer running the service also becomes part of the security boundary around the funds. A server that only watches incoming payments, without holding spending keys, cannot sign a transfer simply because someone has compromised it.

This makes custody and control of private keys more informative than the product name alone. The same software can operate in configurations with different exposure. BTCPay said funds in wallets whose spending keys were kept off the server, including hardware wallets, were unaffected by these thefts. Its recommendation to replace an older server still applies even when keys are held elsewhere.

The flaw was patched in August; these thefts surfaced in November

In its official incident notice (Opens in a new tab), the project said it received reports of stolen bitcoin and litecoin on 1 November. Operators were initially asked to shut down servers during the investigation. The following day's update identified version 2.4.1, released on 23 July 2026, and earlier versions as the targets of the attacks it examined.

The project said attackers used a different method to exploit a vulnerability fixed in version 2.4.2 on 7 August. The earlier incident involved exposed credentials for LND, software used to run a Lightning Network node. November's reports concern on-chain hot wallets. The incidents are connected through the patched vulnerability, but they should not be collapsed into one account of identical thefts.

Version 2.4.7 was subsequently released on 29 October. Its release notes list 85 security findings addressed: 1 critical, 13 high, 52 medium and 19 low, using the original report's severity ratings. That total describes the scope of fixes in the release. It is not a count of break-ins, and it does not establish that every finding was exploited to steal money.

Why a newer version does not erase an earlier intrusion

A business operator can readily check the version number now displayed at the bottom of the interface. The more consequential question is which version was running before the warning. A server updated afterwards can display a current number while still belonging to the exposed group. Installing a patch before an attack and recovering from a potentially compromised system are different situations.

The official recovery route is to move remaining hot-wallet funds to a new wallet created on a trusted device, preserve records, retire the old server and build a clean replacement. Potentially exposed credentials must also be replaced. Operators should not restore the whole old server or reuse its recovery phrase. An unchanged balance does not establish that no intrusion occurred.

Operationally, there are two jobs here. Updating closes weaknesses in the software; replacing the environment and credentials addresses what an attacker may already possess. A new release cannot make a copied secret private again. Before restarting payment operations, the operator therefore needs to understand the condition of both the server and the wallet, rather than stopping once the checkout page loads successfully.

What remains unknown, and which records matter

The notice does not give a confirmed victim count or total loss. It also cautions against treating all funds at the published destination addresses as proceeds of this incident. Activity can predate the reports, and linking individual transactions to theft requires investigation. This article therefore offers neither an independent loss estimate nor an identification of the attackers.

Operators who find unfamiliar activity should preserve the software version used at the time, update dates, transaction identifiers and relevant timestamps. Incident material sent to the security team should have secrets removed; private keys and recovery phrases are not evidence to share. For an Israeli business, these records also support an internal reconciliation of payments and refunds while the service is unavailable.

The broader operational lesson concerns responsibility for the infrastructure that accepts payments. BTCPay recommends keeping only the funds required for day-to-day operations in a hot wallet when one is necessary. How much money remains on the server, and whether that server can sign transactions, are security decisions with financial consequences, not merely convenient interface settings.

Correction and clarification

Found an error? Contact the editors

Share article Back to top