What happened
BTCPay Server, a self-hosted, open-source cryptocurrency payment processor used by merchants, said on 2026-11-02 that attacks had "targeted servers running BTCPay Server 2.4.1" or earlier and stolen bitcoin and litecoin from hot wallets, meaning wallets that store the keys needed to spend funds on the server itself.1,5
BTCPay's timeline records a wallet drain at 13:46 UTC on 2026-11-01, the first emailed theft report at 20:56 UTC, and a public warning on X at 22:25 UTC asking operators to shut down their servers. It says it has not established when exploitation began. Bitquery, as reported by The Hacker News, found the first visible sweep on 2026-10-30, and said 87% of the traced money moved in one wave on 2026-11-01 between 14:12 and 22:16 UTC.1,5
The vulnerability involved was fixed in version 2.4.2, released on 2026-08-07, but BTCPay says the attackers "used a different method to exploit" it. BTCPay has not named the vulnerability or published a CVE identifier. DefiLlama classifies the technique as a key leaked via infrastructure.1,3
Who is affected
Affected parties are the operators of self-hosted BTCPay Server instances on 2.4.1 or earlier, typically merchants accepting crypto payments, and the hosting providers that run them. BTCPay says operators on those versions should treat their servers as affected even if they have not noticed a theft, and that servers updated only after the 2026-11-01 warning are also in scope. Where funds were stolen or unauthorized access is suspected, it says the whole machine and its secrets (hosting, SSH, application, API and Lightning credentials) should be treated as compromised.1,5
BTCPay contacted VPS hosting providers, including LunaNode, which took instances offline as a precaution. It says servers already on 2.4.2 or later when it issued the warning showed no impact. The Paypers reported that BTCPay's own servers, on 2.4.7, were not affected and that there were no credible reports of losses among up-to-date users. The number of affected instances and merchants has not been disclosed.1,6
Who is behind it
No attribution has been made public. BTCPay published one bitcoin and one litecoin destination address and noted that some activity at those addresses appears to predate the reported thefts.1
Financial and operational impact
BTCPay gives no loss total and warns that balances at the reported addresses "should not be treated as a confirmed total of losses." Blockchain data firm Bitquery, as reported by The Hacker News, traced 18.38 BTC and 3,405 LTC, about USD 1.62 million, to the two addresses across 682 sweeps; 77% came from 32 sweeps of USD 10,000 or more, and about half of all sweeps were under USD 100. DefiLlama lists the incident without an amount.1,3,5
The operational cost falls on operators: BTCPay told affected users to shut down, move to a fresh server with the latest release, create a new wallet with a new seed on a trusted device, sweep remaining funds into it, and rotate exposed credentials. It advised against restoring the old server onto the new one and recommended keeping only operational funds on the server.1
Response and recovery
BTCPay asked operators to report incidents to its security address and thefts to local authorities. The Paypers reported that founder Nicolas Dorier said operators who have updated at least once since 2.4.2 are considered safe, and that BTCPay asked affected operators for server logs and planned to publish preventive guidance. The Hacker News reported BTCPay's advice to update to 2.4.7 or later before bringing an instance back online, enable two-factor authentication, change admin passwords and rotate API keys.1,5,6
As of 2026-11-19, the BTCPay blog showed no follow-up post to the 2026-11-02 incident notice; the incident post's last update was 2026-11-02.1,2
What investors and lenders should watch
This is the second exploited BTCPay flaw in three months. On 2026-08-07 BTCPay warned that a critical flaw in all versions before 2.4.2 let an unauthenticated remote attacker obtain LND Lightning credential files and take over nodes, and confirmed funds were stolen. The Hacker News said it is unclear whether the November attacks relate to that vulnerability, and The Paypers said BTCPay has not confirmed whether the same flaw or a different one was used.4,5,6
Because BTCPay is self-hosted, only server operators, not the BTCPay team, can control or shut down merchant servers, according to The Paypers. For lenders and investors exposed to merchants or payment providers running BTCPay, the questions are which version they ran on 2026-11-01, whether they kept spending keys on the server, and whether they rebuilt rather than simply updated. BTCPay said it planned to publish preventive guidance, according to The Paypers; no follow-up post had appeared on the BTCPay blog as of 2026-11-19.1,2,6
What is not known
- The vulnerability and the different exploitation method used have not been described publicly; no CVE has been published.
- When exploitation began is not established by BTCPay; Bitquery saw a first sweep on 2026-10-30.
- The number of affected instances and merchants has not been disclosed.
- BTCPay has not published a total amount stolen.
- Whether outdated instances are still being exploited is unknown.
- No attribution has been made public.
Timeline
BTCPay Server 2.4.1 released.5
BTCPay releases 2.4.2 and warns a critical flaw exposing LND credentials is under active exploitation.4,7
First visible sweep to the attacker addresses, per Bitquery.5
Wallet drain at 13:46 UTC; first theft report at 20:56 UTC; hosting providers asked to take instances offline; public warning on X at 22:25 UTC.1
BTCPay publishes incident post identifying 2.4.1 and earlier as affected.1
Bitquery analysis traces about USD 1.62 million to the attacker addresses (The Hacker News).5
Video and further coverage
Reading video and press coverage...
Sources
- 1.Security Incident Affecting BTCPay Server 2.4.1 and EarlierBTCPay Server, 2026-11-02 · primary
- 2.BTCPay Server blog indexBTCPay Server, 2026-11-19 · primary
- 3.Hacks database (API), BTCPay Server entryDefiLlama, 2026-11-19 · research
- 4.Security Advisory: Update BTCPay Server to 2.4.2 ImmediatelyBTCPay Server, 2026-08-07 · primary
- 5.Hackers Exploit BTCPay Server Flaw to Steal Bitcoin and Litecoin From Hot WalletsThe Hacker News, 2026-11-03 · press
- 6.BTCPay Server links hot wallet attacks to outdated server versionsThe Paypers, 2026-11-04 · press
- 7.Bitcoin Payment Service BTCPay Warns Critical Flaw Is Under Active AttackDecrypt, 2026-08-07 · press
DFX Cyber Desk, "BTCPay Server hot wallets drained on outdated self-hosted instances," DFX Intelligence, published 2026-11-19, https://dfxintel.com/cyber/reports/btcpay-server
DFX Cyber Desk reports state only what the cited sources say. A ransomware group's claim is reported as a claim, losses are reported only as a source states them, and nothing is attributed without a named source. Methodology