
Key takeaways
- BTCPay Server identifies an attack vector targeting instances running versions 2.4.1 or older after attackers drain hot wallets.
- BTCPay Server has no credible reports of hot wallet drains on 2.4.7 and urges everyone to stay updated.
- BTCPay Server has not disclosed the number of affected operators, the value of stolen funds or technical details.
BTCPay Server, the open-source Bitcoin payment processor, said its incident response investigation identified an attack vector targeting instances running versions 2.4.1 or older, after attackers drained funds from hot wallets. The project said it has no credible reports of hot wallet drains for users running the latest 2.4.7 release.
The finding follows an earlier warning, in which BTCPay Server urged operators to shut down their server instances while it investigated reports of unauthorized attackers draining funds from hot wallets. Version 2.4.1 was released on July 23, 2026.
What Operators Need to Do
BTCPay Server set out its findings and guidance in a post on X:
"Our incident response investigation identified an attack vector targeting instances running versions 2.4.1 (Jul 23, 2026) or older. We have no credible reports of hot wallet drains for users running the latest 2.4.7 release. We again urge everyone to keep their BTCPay Server updated. If you were impacted, please send all details and logs to security@btcpayserver.org"
That leaves operators with two steps: upgrade to the latest version, and send all details and logs to security@btcpayserver.org if affected.
No credible reports of drains on 2.4.7 is not a statement that 2.4.7 is safe, and the BTCPay Server post does not say the earlier shutdown advice was lifted. The post alone does not tell operators it is safe to restart.
What BTCPay Server Has Not Disclosed
BTCPay Server has not disclosed the number of affected operators, the value of stolen funds or technical details explaining how attackers accessed the wallets.
The reports come less than three months after BTCPay Server restricted remote Lightning access following an August attack that exploited a vulnerability to obtain Lightning Network Daemon (LND) credentials and steal funds. It remains unclear whether the latest attack vector is connected to the August vulnerability.
BTCPay Server also has no central operator who could push an emergency patch to every merchant. The project can issue an alert, and every individual operator has to act on it.
Why It Matters
BTCPay Server's attack vector targeted versions 2.4.1 or older, while it has no credible reports of drains on 2.4.7, and we believe the takeaway is simple: make sure the software you run is updated with all the patches. Self-custody removes the gatekeeper and the help desk with it, because no central operator can push an emergency patch to your server for you. We still prefer that trade to a custodial processor, where an intermediary holds your Bitcoin and your permission to spend it. Sovereignty comes with a maintenance schedule, so upgrade now and keep your keys away from anything you have not patched.





















