Editorial draft: This release-format summary was prepared by Bitnxt from CoinDesk reporting and BTCPay Server’s public security advisory. It is not a press release issued or approved by BTCPay Server.
BTCPay Server initially urged operators to shut down their instances on 1 November 2026 after receiving reports of unauthorised hot-wallet withdrawals. The project’s subsequent advisory identified attacks against versions 2.4.1 and earlier and set out recovery steps for operators of potentially compromised servers.
The initial shutdown warning was reported by CoinDesk in its 2 November coverage. This draft incorporates the project’s later official security advisory so that the original precautionary alert is not presented as the complete or latest guidance.
Initial Shutdown Alert and Investigation
In its initial public warning, BTCPay Server said:
“We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers.”
The project asked operators to shut down their instances while it investigated. CoinDesk reported that attackers had obtained administrator access on affected servers, while the method of access and the scope of losses had not yet been established at the time of its report.
That initial warning did not announce a confirmed loss total or a count of affected servers. The later official advisory also cautions against treating the balances and transaction histories of reported destination addresses as a confirmed total of incident losses.
Official Advisory Identifies Affected Versions
According to BTCPay Server’s subsequent advisory, the attacks targeted version 2.4.1, released on 23 July 2026, and earlier releases. The project says attackers used a different method to exploit the vulnerability fixed in version 2.4.2, released on 7 August 2026.
The advisory states that the project has seen no impact from these attacks on servers that were already running version 2.4.2 or later when the 1 November warning was issued. This is a finding about the reported incident, not a guarantee that a particular installation is free from every security risk.
For operators who were running 2.4.1 or earlier, the project recommends moving to a fresh server with a new wallet, even if they have not noticed a theft or updated after the warning. Where funds were stolen or unauthorised access is evident, it advises treating the entire machine and its secrets as compromised.
Recovery Guidance for Potentially Compromised Servers
The project’s published recovery guidance makes clear that updating software alone cannot remove access an attacker may already have obtained. An unchanged wallet balance does not rule out earlier compromise.
BTCPay Server outlines the following recovery steps for affected operators:
Create a new wallet using a trusted device and a new seed. Sweep any remaining funds from the existing hot wallet into the new wallet. Reusing the old seed on a new server leaves those funds at risk.
Take the old server offline. Preserve relevant logs and transaction records for the investigation before replacing the machine.
Provision a fresh virtual machine. Install the latest supported BTCPay Server release from trusted sources and connect the new wallet. Do not restore the entire old server onto the replacement machine.
Replace potentially exposed passwords and access keys. From a trusted device, revoke and replace credentials accessible to the old server, including applicable hosting, SSH, application, API and Lightning credentials. Do not enter replacement credentials on the old machine.
Operators should consult the complete official advisory and their hosting provider for instructions appropriate to their deployment, rather than relying on the original shutdown warning alone.
Hot-Wallet Exposure and Off-Server Signing
A hot wallet stores the keys needed to spend funds on the server itself. BTCPay Server’s wallet documentation warns that this feature has security implications because the server can automatically use the stored seed to sign transactions.
In its incident advisory, the project says funds in wallets whose spending keys were held off the server, including hardware wallets, were unaffected by these thefts. It continues to recommend accepting payments into wallets with off-server spending keys. Its recommendation to rebuild an older server still applies even where wallet keys are kept elsewhere.
For operators who need a hot wallet for everyday activity, the project recommends keeping only the funds needed for those operations on the server and moving the remainder to a wallet whose spending keys are held elsewhere.
Incident Reporting and Handling Sensitive Information
BTCPay Server asks affected operators to use the reporting channel listed in its official advisory and provide the software version running at the time, update history where known, when the incident was noticed and the relevant timezone, and public transaction identifiers and addresses. The advisory also recommends reporting stolen funds to local authorities.
Never share seed phrases, private keys, passwords or other credentials. Remove secrets from logs or configuration files before submitting incident information.
About BTCPay Server
BTCPay Server is free, open-source software that enables businesses to accept bitcoin payments directly into their own wallets. Operators can deploy the software on their own infrastructure and remain responsible for securing their installations. Its wallet tools support multiple signing approaches, including hardware wallets, partially signed bitcoin transactions and hot wallets.
For project information, visit btcpayserver.org. For incident-specific instructions, refer to the official security advisory.












































