
BTCPay Server says attackers are draining hot wallets on instances running version 2.4.1 or older. It urges operators to upgrade to 2.4.7, which has no credible drain reports.
In brief
- BTCPay Server traced the hot wallet drains to an attack vector affecting version 2.4.1 or older, released on 23 July 2026.
- The project says it has no credible reports of drains on the latest release, version 2.4.7, and urges all operators to update.
- BTCPay has not disclosed how many operators were affected or how much Bitcoin was stolen.
What happened
BTCPay Server, a free open-source tool that businesses run on their own servers to accept Bitcoin
BTC payments, said attackers are draining hot wallets on outdated instances.
The project identified an attack vector targeting version 2.4.1 or earlier, which was released on 23 July 2026, according to Cointelegraph.
A hot wallet keeps the wallet's seed on the internet-connected server so it can sign transactions automatically.
BTCPay's own documentation labels the feature "DANGER" and warns it carries security implications, Decrypt reported.
The project first told operators to shut down their servers on Sunday while it investigated, as reports of swept hot wallets spread across multiple instances.
It later said it had no credible reports of drains among users running the latest release, version 2.4.7, and urged everyone to update, narrowing the warning to older versions.
Version 2.4.7 was released on Thursday as an emergency update fixing one critical and several medium-severity vulnerabilities found by Anthropic's scanner.
BTCPay has not said whether the attacks exploited any of those flaws.
Some hosting providers, including LunaNode, shut down BTCPay instances automatically to stop older versions from being exploited.
BTCPay has not disclosed the number of affected operators, the value of stolen funds or the technical details of how attackers gained access.
Why it matters
Because BTCPay is self-hosted, no central operator can switch every instance off.
Each merchant must act on its own server, and the project asked affected users to send logs to its security team.
The reports come less than three months after an August attack that used compromised Lightning Network Daemon (LND) credentials to steal funds, prompting BTCPay to restrict remote Lightning access.
It remains unclear whether the two attacks are connected.
Bitcoin traded near $78,160 at 13:46 UTC, up +0.28% in 24 hours, according to Hyperliquid data.
What to watch
Operators on 2.4.1 or older should upgrade to 2.4.7 and rotate any credentials stored on the server.
Merchants running a hot wallet may also consider moving funds to a setup where the seed stays offline.
BTCPay has not published a full post-mortem.
Watch for its disclosure of how many servers were affected and whether the vector overlaps with the August flaw.