Best way to accept #Bitcoin. No fees, no intermediary. Free, open source & self-hosted Bitcoin payment processor for self-sovereign individuals and businesses.
๐ข Security Incident Affecting BTCPay Server 2.4.1 and Earlier
Read the full security advisory, including details & timelines, on our blog: https://t.co/YTlthDbLIM
If you were impacted, please send all details and logs to [email protected]
For @lightning node runners out there, LND in @BtcpayServer has been updated to 0.21.7-beta.
In the age of AI, I highly recommend keeping all your software on the latest versions ๐ช
๐ข Security Incident Affecting BTCPay Server 2.4.1 and Earlier
Read the full security advisory, including details & timelines, on our blog: https://t.co/YTlthDbLIM
If you were impacted, please send all details and logs to [email protected]
๐จ We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers.
If you're running an instance, please shut it down (./btcpay-down.sh) until we complete the investigation.
๐ข 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 [email protected]
๐ข 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 [email protected]
๐ข 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 [email protected]
๐ข 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 [email protected]
๐ข 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 [email protected]
๐ข 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 [email protected]
๐ข 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 [email protected]
We will publish a blog post going to more details.
But at least for those who already updated at least once since the release of 2.4.2, there is no reason to panic.
Please update often. Especially those days!
Also, don't keep too much in your Hot Wallet.
If you run BTCPay Server through a hosting provider, your instance may have been shut down automatically to keep older versions from being exploited.
We thank @LunaNode and other hosting providers for their swift action after our initial announcement.
๐ข 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 [email protected]
Update on my part: Our public servers were not attacked (on 2.4.7), it seems reports are on before 2.4.2.
The attacker managed to log in as admin on those instance, we are still trying to figure out how.
Thanks @r0ckstardev and @MrKukks for leading the way on CVE 2026-98432. I used both sources and one from Akamai to deploy a fix until kernel update available for my other servers in the wild. If you use BTCPay Server you don't need this.
https://t.co/LlLu4YYKXk