Crypto thefts hit out-of-date BTCPay Server installs
Attackers drained Bitcoin and Litecoin hot wallets on out-of-date BTCPay Server installs; 2.4.7 is the fix
BTCPay Server, the self-hosted crypto payment software many online shops and donation pages use, says attackers targeted servers on version 2.4.1 (released 23 July 2026) or older. The project has not said how many servers were hit, how much was stolen or how the attackers got in. It says it has no credible reports of hot wallet drains on the latest release, 2.4.7.
What to do this week
- Find out whether you, or anyone you rely on, runs BTCPay Server.Ask the business, charity or developer behind any crypto payment page. Ask in writing which version they run and whether the wallet is a hot wallet on the server.
- Update to 2.4.7.In the admin screen, go to Server Settings, then Maintenance, then Update. Docker installs: sign in over SSH, run
sudo su -, change to thebtcpayserver-dockerfolder and run./btcpay-update.sh. The admin page footer shows the version afterwards. - If the server was on 2.4.1 or older, treat the wallet as compromised.Create a new wallet with a fresh recovery phrase, ideally on a hardware device, and move the funds across. Build the server again on a new machine rather than restoring the old one, and keep the old server's logs. Do this even if you updated after the warning, because an update doesn't remove an attacker who is already in.
- Keep little in a hot wallet.Sweep the balance to a hardware wallet or other cold storage regularly. The project says funds held outside the server weren't affected.
- Report any loss.Email security@btcpayserver.org with the transaction details and your server logs, and report the theft to your local police and any exchange the funds moved through.
Working out which of your family's businesses and advisers run software like this, and checking before the thieves do, is part of what private cybersecurity is for.
What happened
On Sunday 1 November, the team behind BTCPay Server told everyone running it to switch their servers off. Reports were coming in that attackers were emptying the cryptocurrency wallets those servers control. BTCPay Server is free, self-hosted software that lets a shop, charity or website accept Bitcoin and other coins without a middleman, and each server is run by whoever installed it.
Within hours the project narrowed the warning. It said the attacks targeted servers running version 2.4.1, released on 23 July 2026, or older, and that it had no credible reports of drained hot wallets on the latest release, 2.4.7. Bitcoin and Litecoin have both been taken. The project has not said how many servers were hit or how much was stolen, and it has not published how the attackers got in.
- Severity
- High Funds are being stolen from servers still running old versions.
- Software
- BTCPay Server, self-hosted crypto payment processor
- Targeted
- Version 2.4.1 (23 July 2026) or older
- Latest version
- 2.4.7, released 29 October
- Stolen
- Bitcoin and Litecoin from hot wallets. Amount not disclosed.
- Not affected
- Hardware wallets and other wallets where the keys are not on the server
- Entry method
- Not published. The founder says the attacker logged in as an administrator.
The full story3 more sections
What a hot wallet is, and why it's the target
A hot wallet is one whose secret keys sit on a connected computer so it can send payments automatically. In BTCPay Server, the server signs outgoing payments with a recovery phrase it stores itself, so anyone who takes control of the server can move the money. That's convenient for a shop and exactly what thieves look for.
A hot wallet is a till drawer, not a vault. It should hold what you need this week.
What we know, and what we don't
BTCPay Server's founder, Nicolas Dorier, said the attacker logged in to affected servers with administrator access. BleepingComputer reports the access seems to have come through flaws in versions before 2.4.2, the release of 7 August. The project has not confirmed the method, and The Paypers reports that it has not said whether the attacks used the August flaw or another one.
That August flaw was a different kind of problem. It let an attacker without a login take the credentials for a server's Lightning node, and the project said funds were stolen. Its advisory[1] said on-chain hot wallets weren't affected then. This is the second serious incident in under three months. Nobody has said the two share a cause.
On 29 October the project also shipped 2.4.7 as an emergency update. Its release notes[2] list 85 findings from an Anthropic security scanner, one rated critical. BTCPay has not said whether the thefts used any of them. The project says it has no credible reports of drained hot wallets on 2.4.7.
Who is affected
Mostly whoever takes crypto payments for you
Few families run BTCPay Server at home. But a family business with an online shop, a foundation taking crypto donations, a family office or a relative with a side business might. Some hosting companies shut down old BTCPay installs on their customers' behalf, so an instance that went offline isn't necessarily broken. It may have been switched off.
No report says that customers paying through a BTCPay checkout have lost money. The reported thefts are from the wallets of the people running the servers.
If you run one yourself, three groups need different action. Servers already on 2.4.7 are in the best position. Servers on 2.4.2 to 2.4.6 are considered safe by the project if they were updated at least once since 2.4.2, though BleepingComputer reports the project urging everyone to move to 2.4.7. Servers on 2.4.1 or older are the ones the attackers went after, and the project's advice is to treat any wallet on them as compromised. Cointelegraph reports the same advice for those who updated only after the warning.
Timeline
-
HARD publishes its article, at High.
After the news
- How to update every device phones, computers, browsers, TVs and routers
References8
- ^ BTCPay Server (). “Security Advisory: Update BTCPay Server to 2.4.2 Immediately”. The August Lightning credential flaw, affected versions, fix, on-chain hot wallets not affected.
- ^ BTCPay Server (GitHub). “BTCPay Server releases (v2.4.7 and v2.4.2 notes)”. 2.4.7 dated 29 Oct, fixes 85 scanner findings incl. one critical; 2.4.2 dated 7 Aug.
- BleepingComputer (). “BTCPay Server warns of hot wallet crypto thefts on outdated instances”. Affected versions, 2.4.7 fix, Dorier's admin-login statement, update steps, reporting address.
- Cointelegraph (). “BTCPay Server Identifies Attack Vector After Bitcoin Wallet Theft Reports”. Hardware wallets unaffected; rebuild-and-move-funds guidance; losses undisclosed.
- Decrypt (). “BTCPay Tells Merchants to Switch Off Servers Amid Hot Wallet Attack Reports”. Timeline of the 1 November shutdown request, 2.4.7 release, hosts shutting instances.
- The Paypers (). “BTCPay Server links hot wallet attacks to outdated server versions”. How hot wallet mode works, 'updated since 2.4.2' safety statement, root cause unconfirmed.
- The Hacker News (). “Hackers Exploit BTCPay Server Flaw to Steal Bitcoin and Litecoin From Hot Wallets”. Only the feed summary was available: targeted servers on 2.4.1 (23 July 2026) or earlier.
- BTCPay Server (). “BTCPay Server Security Incident: Our Response and Next Steps”. August thefts, cold storage advice, reporting address, recovery bounty.
Situation Room articles are updated as events develop: updates are added to the timeline, and never edited away. Follow them by email or RSS.

