Checked as of 4 November 2026. On 2 November 2026 the BTCPay Server project published a security incident notice after receiving reports on 1 November of Bitcoin and Litecoin stolen from hot wallets. A hot wallet keeps the spending keys on the server itself. The project traced the attacks to instances running version 2.4.1, released 23 July 2026, or earlier. The attackers used a different method to exploit the vulnerability that was fixed in 2.4.2 on 7 August 2026. The Hacker News also covered the incident on 3 November, but the project’s own notice is the authoritative source for what to do.
If you run BTCPay Server for an online shop, this is not a call to rebuild every deployment. It is a rebuild decision only for instances that were still on 2.4.1 or earlier when the project issued its warning, and for any instance showing signs of compromise. For everyone else it is a verification task. Here is the checklist.
1. Find out which version was running when the warning went out
Log in and look at the version number at the bottom of the page. The question is not only which version you run today, but which version was running when the project warned the community on 1 November at 22:25 UTC. If someone updated after that moment, write down the date and the previous version. If you cannot establish this from your own records, treat the history as uncertain and ask your hosting provider to confirm it from theirs. The current release when we checked was 2.4.7, which is well past the 2.4.2 boundary that matters here.
2. Pick the branch that applies
- Already on 2.4.2 or later at the time of the 1 November warning. The project says it has seen no impact from these attacks on such servers. That is not a blanket all-clear. Keep installing updates as they are released, and review wallet activity and logs for anything unexpected.
- On 2.4.1 or earlier at the time of the warning. The project strongly recommends moving to a fresh server with a new wallet. This applies even if your balance looks untouched, and even if you updated after the warning. An unchanged balance does not prove nobody got in.
- Funds missing or signs of unauthorized access. Treat the whole machine and every secret on it as compromised. Follow the full recovery path even if you have already updated.
If your wallet’s spending keys live off the server, for example on a hardware wallet, the project says those funds were unaffected by these thefts. The rebuild advice for an older server still applies.
3. Recovery steps, in order
Do each of these from a trusted device, not from the old server.
- Create a new wallet with a new seed and sweep any remaining hot-wallet funds into it. Do not reuse the old seed on the new server.
- Take the old server offline. Before replacing it, preserve logs and transaction records you may need for the investigation and your own records.
- 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 new machine. Rebuilding from a known-good base is the same principle we describe in our backup strategy guide.
- Revoke and replace credentials the old server could reach: hosting panel, SSH keys, application logins, API keys, and Lightning credentials. Never type new credentials into the old machine.
Updating in place cannot remove access an attacker already has. That is why this is a rebuild, not a patch.
4. If your instance is hosted
On 1 November the project asked VPS providers, including LunaNode, to take BTCPay Server instances offline as a precaution. If your server is hosted, ask your provider two specific questions: which version your instance was running at 22:25 UTC on 1 November, and whether any update happened before or after that warning. Then ask for help provisioning a fresh VM. Keep provider requests limited to your own instance and authorized by you. Do not run disruptive commands yourself to check anything.
5. Report what you can, without secrets
If you lost funds or saw unauthorized activity, email security@btcpayserver.org with the version at the time, when you last updated and from which version, when you noticed the incident with your timezone, and relevant public transaction IDs. Never send seed phrases, private keys, or passwords, and strip secrets from any logs you share. Report a theft to local authorities as well.
Going forward
Keep only the funds needed for daily operations in any hot wallet, and move the rest to a wallet whose keys stay off the server. Watch for release announcements and apply updates promptly. Our guides on monitoring beyond uptime and what to do when a website is hacked cover the broader habits.