BTCPay Server: hot wallets drained on outdated instances
Bitcoin and Litecoin stolen from hot wallets on BTCPay Server 2.4.1 and earlier: what happened, what is known about the attack vector and what to do now.

Between the end of October and 2 November 2026, someone drained the hot wallets of a number of BTCPay Server instances. BTCPay Server is the open-source payment processor that businesses install on their own servers to accept Bitcoin and other cryptocurrencies without intermediaries, including over the Lightning Network. According to the project, the affected instances run version 2.4.1 (23 July 2026) or earlier: operators should treat them as compromised, not just update them.
What happened
According to BleepingComputer, the first theft reports reached the project on the evening of 1 November (UTC). The project asked VPS providers to take the affected instances offline as a precaution and initially advised all operators to shut down their servers pending the investigation.
On 2 November BTCPay Server published an incident update: the investigation identified an attack vector targeting instances running 2.4.1 or earlier, which allowed the attacker to log in as an administrator and move funds out of the hot wallets, in Bitcoin and Litecoin. The project recommends updating to version 2.4.7 and says it has no credible reports of thefts on instances already running 2.4.7. According to Infosecurity Magazine, at the time of the warning there was no impact on servers running 2.4.2 or later.
Technical details
The sources do not give a CVE identifier and do not describe the vulnerability in detail. What is known:
- Affected versions: 2.4.1 and earlier. The fix is in 2.4.2, released on 7 August 2026: according to Infosecurity Magazine, the attacker used a different method to exploit a vulnerability fixed in that very version. The emptied wallets therefore sat on servers that had never installed a fix available for almost three months.
- August precedent: again according to Infosecurity Magazine, the same flaw had already been exploited in August to steal funds through LND, the Lightning Network implementation; at the time the project said on-chain wallets, hot wallets included, were not affected.
- Version 2.4.7: BleepingComputer notes that on 29 October the project disclosed a critical vulnerability, found with Anthropic’s Frontier OSS scanner, which led to the release of 2.4.7 as an emergency security update. The evidence gathered by the project, however, points to vulnerabilities in versions earlier than 2.4.2 being used in the attacks.
- Attack chain: administrator access to the panel of a network-exposed application, then transfer of funds from the hot wallets, i.e. wallets whose spending keys sit on the server. In MITRE ATT&CK terms the pattern falls under Exploit Public-Facing Application (T1190) and Financial Theft (T1657); the exact access mechanism has not been made public.
How much was taken
The project has not published a loss total. According to an analysis by blockchain intelligence firm Bitquery, reported by Infosecurity Magazine, 18.38 BTC and 3,405 LTC (about 1.63 million dollars) reached the two addresses named by BTCPay Server in 682 sweeps between 30 October and the morning of 2 November. 87% of the funds moved in a single wave on the afternoon and evening of 1 November, and a further 267 sweeps (about 150,000 dollars) happened after the call to shut down instances, issued at 22:25 UTC that night.
Bitquery cannot say how many servers were hit, because the blockchain records wallets, not systems, and it left out other addresses and coins, including Lightning funds: the figure is a floor. BTCPay Server, for its part, warns that some activity at those two addresses appears to predate the reported thefts, so their balances should not be read as confirmed losses.
Impact for European and Italian businesses
BTCPay Server is used by online shops, service providers and organisations that accept cryptocurrency payments without going through an intermediary. The sources give no figures by country, but anyone in Europe or Italy running a self-hosted instance with a hot wallet on 2.4.1 or earlier is within the scope of the attack. The case shows a problem common to much internet-facing software: the fix had been out since August, yet instances that were installed and then left without maintenance stayed vulnerable. For organisations subject to NIS2, unauthorised administrative access to an exposed payment system is an event to assess under their own incident management and notification procedures.
What to do now
Guidance from the project, as reported by BleepingComputer and Infosecurity Magazine:
- Instances on 2.4.1 or earlier: take them offline as soon as possible.
- Update to 2.4.7 from Server Settings → Maintenance → Update. For Docker installations: log in over SSH,
sudo su -,cd btcpayserver-dockerand./btcpay-update.sh. - Rebuild: anyone who ran 2.4.1 or earlier with a hot wallet should move to a fresh server with a new wallet and a new seed, even if they have since updated. According to the project, updating alone cannot remove access an attacker may already have gained. Do not restore the old server onto the new one.
- Credentials: replace all credentials exposed on the server.
- Evidence: preserve logs and transaction records.
- Funds: wallets whose spending keys are held off the server, such as hardware wallets, were not affected; keep only operational funds on the server.
- Report losses to security@btcpayserver.org and to local authorities.
For detection, beyond the project’s guidance, it is good practice to review the logs for administrative logins and for privileged accounts created or changed recently, and to compare outgoing hot wallet transactions with the two addresses listed in the project’s advisory.
How ARXDOME helps
ARX Expose shows which of your company’s services are exposed on the internet and which appear vulnerable, including administration panels such as that of a payment processor; ARX Shield keeps track of open vulnerabilities on monitored machines, so a fix like 2.4.2 does not stay pending for months; ARX Sentry collects logs and events from servers, useful for reconstructing anomalous administrative access.
Last updated:


