- BTCPay Server deployments running versions prior to 2.4.2 have been targeted by attackers gaining unauthorized administrator access.
- Founder Nicolas Dorier noted that public and demo instances on version 2.4.7 show no signs of compromise, though total losses and the exact entry point remain undisclosed.
- The security incident follows the rollout of version 2.4.7, an update that resolved 85 vulnerabilities uncovered through an Anthropic open-source AI security scanning project.
Operators of self-hosted cryptocurrency payment infrastructure are facing serious security challenges following targeted intrusions into BTCPay Server environments. Designed as an open-source payment processor, BTCPay Server allows merchants to accept Bitcoin (BTC) without third-party intermediaries, leaving the responsibility of node hosting and private key custody entirely in the hands of users. While total Bitcoin losses and the precise number of compromised merchants have not been officially disclosed, investigators are actively probing how attackers infiltrated targeted systems.
Investigation Focuses on Legacy Deployments Prior to Version 2.4.2
BTCPay Server founder Nicolas Dorier released preliminary findings indicating that the compromised instances were running software versions prior to 2.4.2. Forensic traces suggest that threat actors exploited vulnerabilities in these legacy versions to achieve administrator-level access. In contrast, public and demonstration servers operating on the recent version 2.4.7 have remained uncompromised. While this evidence indicates the latest release did not introduce the breach, developers emphasize that investigators have not yet finalized a full technical post-mortem.
The software previously underwent a targeted fix in August when the project addressed an unauthenticated vulnerability in version 2.4.2. That specific flaw permitted attackers to access Lightning Network Daemon (LND) macaroon credentials used for API authorization. Although developers stated at the time that BTCPay’s native on-chain wallets were not exposed by that flaw, investigators have not yet confirmed whether the current wave of unauthorized activity stems from that previous vulnerability, another legacy bug, or a chain of distinct exploits.
Massive AI-Assisted Security Audit Preceded the Incidents
The compromise occurred on the heels of a massive codebase overhaul. On October 29, the BTCPay Server development team deployed version 2.4.7 after reviewing security reports produced via Anthropic’s open-source security scanning initiative. The comprehensive update remediated 85 separate vulnerabilities, consisting of one critical flaw, 13 high-severity issues, 52 medium-severity concerns, and 19 low-severity findings.
These findings formed part of a widespread expansion of automated AI vulnerability auditing in 2026, driven by advanced scanning tools from Anthropic, OpenAI, and Google. Over a six-month duration, Anthropic’s initiative identified more than 29,000 potential software vulnerabilities across various open-source platforms, with a fraction moving through manual review. The ongoing situation highlights the structural lag between patch distribution and user implementation: patching upstream software code does not instantly remediate unmanaged, self-hosted deployments maintained by individual operators.
Operators Take Action as Developers Prepare Comprehensive Disclosure
In response to the exploit warnings, several crypto-commerce businesses took their payment nodes offline to prevent exposure. Merchant platform Coincards was among the operations that temporarily disconnected its BTCPay instances. The disruption forces store owners into a difficult operational bind, weighing lost revenue from paused checkout systems against the immediate risk to balances held in active wallets. As investigations proceed, Dorier reminded node operators to restrict hot-wallet balances strictly to sums they can afford to lose.
Why This Matters
Self-custodial software gives merchants complete sovereignty over their financial rails, eliminating dependence on centralized payment processors. However, this sovereignty also places the burden of rapid patch management entirely on the merchant. As AI-powered code auditing accelerates the pace at which code vulnerabilities are surfaced and publicly remediated, the window between patch publication and malicious exploitation is rapidly shrinking. The incident underscores the operational challenges decentralized finance platforms face when trying to keep independent node operators up to date with defensive patches.
Frequently Asked Questions
Which BTCPay Server versions are known to be affected?
Preliminary findings from founder Nicolas Dorier reveal that the compromised setups were running releases older than version 2.4.2. Test and public servers running the updated version 2.4.7 have not shown signs of intrusion.
How much Bitcoin was lost in the exploit?
Developers have not publicly disclosed the exact sum of stolen Bitcoin or the total count of impacted merchants, as the technical investigation remains ongoing.
What role did Anthropic play in the recent software patches?
Anthropic assisted in finding 85 potential software vulnerabilities through its AI-driven open-source scanning initiative. These issues—ranging from low-severity concerns to a critical flaw—were addressed in the version 2.4.7 update published on October 29.
