On this page (7 sections)
Thieves have emptied Bitcoin and Litecoin hot wallets on out-of-date BTCPay Server installations, the open-source, self-hosted cryptocurrency payment processor. Infosecurity Magazine reports that the project's incident update of November 2 places the affected servers on version 2.4.1 or earlier.
If you run BTCPay Server yourself, or host it for clients, this needs attention today. The project's advice goes beyond patching: it says an update cannot remove access an attacker may already have gained. No primary advisory or CVE record was found for this story, so everything below rests on press reports of the project's statements.
What happened
The Hacker News quotes BTCPay Server saying the attacks hit servers on 2.4.1 (released July 23, 2026) or earlier, and that the attackers used a different method against the vulnerability fixed in 2.4.2 on August 7, 2026. Put simply, a fix had been available for months, and the drained wallets were on servers that never installed it.
Blockchain intelligence firm Bitquery followed 18.38 Bitcoin and 3,405 Litecoin to two addresses that BTCPay Server named. The coins moved in 682 sweeps from October 30 to the morning of November 2. Bitquery said the thief logged in to the servers as an administrator. The two outlets put slightly different dollar values on the same coin amounts (about $1.63m and $1.62m), and neither explains the gap.
- Bitcoin traced to the two addresses (Bitquery)
- 18.38 BTC
- Litecoin traced (Bitquery)
- 3,405 LTC
- Sweeps between October 30 and November 2 (Bitquery)
- 682
- Share of traced funds moved in one wave on November 1 (Bitquery)
- 87%
Treat the figures as a floor, not a total
Bitquery could not say how many servers were affected, since a blockchain shows wallets rather than machines. Its count also leaves out other addresses and coins, including Lightning funds. BTCPay Server noted that some activity at the two addresses seems to predate the reported thefts, so the balances are not confirmed losses. The project has not published a loss total.
Sweeps did not stop with the warning. Bitquery counted 267 more, worth about $150,000, after BTCPay Server told operators at 22:25 UTC on November 1 to shut their instances down.
Technical details: what is and is not confirmed
Without a vendor advisory or CVE record, the technical picture is thin. These are the points that can be stated with care.
- BTCPay Server says the attackers used a different method against the vulnerability fixed in 2.4.2. The research does not describe the nature of that vulnerability.
- In August 2026 the project disclosed a critical flaw that could let an unauthenticated remote attacker obtain .macaroon credential files for LND, a Lightning Network implementation, and use them to take over an LND node and move funds. It said at the time that on-chain wallets, including hot wallets, were not affected.
- The Hacker News says it is unclear whether the November thefts involve that same August vulnerability, so this article does not treat them as one issue.
- The start of exploitation is unknown. Reports surfaced around November 1, while Bitquery's earliest visible sweep was early on October 30, less than a day after version 2.4.7 shipped.
Who is exposed
The realistic exposure is operators of self-hosted BTCPay Server on 2.4.1 or earlier who keep a hot wallet, meaning a wallet whose spending keys live on the server. The project said wallets with spending keys held off the server, including hardware wallets, were unaffected.
Infosecurity Magazine reports the project had seen no impact on servers running 2.4.2 or later when it issued its warning. In a post on X, it also said it had no credible reports of hot wallet drains from users on the latest release, 2.4.7, which The Hacker News says addresses one critical and several medium-severity issues. If a hosting provider runs your instance, The Hacker News reports it may have been shut down automatically to stop older versions being exploited, so ask your provider before assuming an outage is unrelated.
How to check your exposure
Begin with the version, then look at what the server holds. Confirm the installed version in your BTCPay Server instance or deployment tooling. If you manage the host, review administrator accounts for any you did not create and recent logins you do not recognize, since Bitquery said the thief signed in as an administrator.
Then compare your wallet history with the two attacker addresses BTCPay Server published, listed in the Hacker News report. Funds sent to either address are a strong sign your server was hit. The research does not say where traces of this attack would appear in server logs, so no log search pattern is offered here.
Copy your logs somewhere safe before you investigate or change anything, as the project advises preserving them.
What to do now
- Check your BTCPay Server version. If it is 2.4.1 or earlier, treat the server as possibly compromised, even if you saw no theft.
- Preserve logs and transaction records before changing anything.
- Build a fresh server with a new wallet and a new seed, as BTCPay Server recommends, and move remaining funds there.
- Do not restore the old server onto the new one, so you do not carry over any access the attacker holds.
- Replace exposed credentials, including administrator logins and any API or LND credentials the old server held.
- Run the latest release (reports name 2.4.7) on the new server.
- Keep only operational funds in hot wallets and move the rest to a wallet whose spending keys are held off the server.
- If funds were stolen or you suspect unauthorized access, consider the whole machine and every secret on it compromised and follow the same recovery steps.
Detection and monitoring afterwards
Watch the wallets themselves. Set alerts in a block explorer or wallet tool for any outgoing transaction from your hot wallet addresses, and review administrator accounts regularly.
For the web front of your payment setup, keep an eye on certificate expiry, DNS changes and uptime so an unexpected change stands out. Webforta Monitor covers those checks, and the free SSL checker gives a quick read on your certificate. These help you notice changes around the server; they do not replace patching or the rebuild described above.
Timeline
| Date | Event |
|---|---|
| July 23 | BTCPay Server 2.4.1 released |
| August 7 | 2.4.2 released with the fix BTCPay Server refers to |
| August (exact date not given) | BTCPay Server discloses a critical flaw that could expose LND .macaroon files and says it was used to steal funds. The research does not confirm this is the same vulnerability exploited in the November thefts |
| October 30 | First sweep visible to Bitquery, less than a day after 2.4.7 shipped |
| November 1 | 87% of traced funds move; operators told at 22:25 UTC to shut down instances |
| November 2 | BTCPay Server publishes its incident update; sweeps traced through the morning |
| November 3 | Press reports published |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
