Cryptocurrency Thieves Drain $1.63 Million from Outdated BTCPay Server Instances

A significant security incident has impacted users of the open-source payment platform BTCPay Server, resulting in the theft of approximately $1.63 million in Bitcoin and Litecoin. The breach specifically targeted servers running outdated software, highlighting the persistent risks associated with failing to apply critical security patches in decentralized financial infrastructure.

According to an official incident update published by the BTCPay Server project on November 2, the thefts affected servers operating on version 2.4.1 or earlier. Investigators discovered that malicious actors successfully utilized an exploit to compromise these systems, leveraging a vulnerability that had actually been addressed and patched in version 2.4.2, which was released to the public on August 7. Crucially, the development team confirmed that servers already running version 2.4.2 or later at the time of the warning showed no evidence of being impacted by the campaign.

Blockchain Analysis Reveals Scope of the Theft

The scale of the operation was brought to light through a detailed analysis conducted by the blockchain intelligence firm Bitquery. By tracking on-chain activity, the firm identified 18.38 Bitcoin and 3,405 Litecoin linked to two specific addresses associated with the attackers. These funds were systematically drained in 682 individual "sweeps" that occurred between October 30 and the morning of November 2.

Bitquery’s investigation suggests that the attackers gained administrative access to the compromised servers, which granted them the necessary permissions to interface directly with the platforms’ hot wallets and siphon off the stored cryptocurrency. The timing and coordination of these thefts underscore the methodical nature of the operation. Bitquery noted that 87% of the total traced funds were moved in a single, concentrated wave during the afternoon and evening of November 1.

The situation escalated even after the BTCPay Server team issued a public alert. Despite the project urging operators at 22:25 UTC on November 1 to immediately shut down their affected instances to prevent further losses, Bitquery recorded an additional 267 sweeps, amounting to roughly $150,000, that occurred after the warning had been broadcast.

While the $1.63 million figure represents a verified floor for the losses, the true impact may be higher. Bitquery clarified that because blockchain records track wallet addresses rather than individual server systems, it is impossible to determine the exact number of servers compromised. Furthermore, the firm noted that their analysis excluded other addresses and additional digital assets, including funds held within the Lightning Network, meaning the total financial damage remains an estimate. BTCPay Server also cautioned that some activity associated with the identified addresses appears to predate the recent wave of thefts, advising that these wallet balances should not be treated as a definitive record of the total losses incurred during this specific incident.

Recurring Vulnerabilities and Security Warnings

The vulnerability utilized in this breach has a documented history. The flaw had previously been exploited in August to target funds through LND, a popular implementation of the Lightning Network. At the time of that earlier discovery, BTCPay Server had informed users that while LND-related assets were at risk, standard on-chain hot wallets were considered secure. This assessment, however, proved to be insufficient as attackers eventually adapted their methods to target the hot wallets on systems that had failed to implement the August 7 security update.

The persistence of these thefts months after the patch release highlights a major challenge for operators of self-hosted financial software: the critical need for proactive maintenance. By failing to update to version 2.4.2, users left their infrastructure exposed to a known, weaponized vulnerability.

Urgent Remediation and Security Best Practices

In the wake of the incident, BTCPay Server has issued a stark warning to all operators of version 2.4.1 or earlier: simply updating the software is no longer sufficient. Because the attackers gained administrative access, the project’s security team has advised that those affected must move to an entirely fresh server installation, complete with a new wallet and a new seed phrase.

"Updating alone cannot remove access an attacker may already have gained," the project stated in its advisory. The concern is that if an attacker has already established a persistent foothold—such as a backdoor or secondary administrative account—merely patching the software would leave the malicious access point intact, allowing the intruder to continue monitoring or draining the wallet.

To secure their operations moving forward, the project provided a series of best practices for those affected. Operators were advised to:

  • Avoid restoring from backups: Do not attempt to restore the old server configuration onto a new one, as this may reintroduce the compromised environment or existing malware.
  • Preserve evidence: Keep thorough logs and transaction records, which are essential for potential forensic investigations and internal audits.
  • Rotate credentials: Replace all exposed API keys, passwords, and administrative credentials that were present on the old server.
  • Limit operational funds: Keep only the minimum amount of funds necessary for immediate operations on a hot wallet.

The project emphasized that users who held their spending keys off-server—such as those utilizing hardware wallets—were not affected by this breach. This distinction highlights the fundamental difference between hot and cold storage in the context of security. Hot wallets, which are connected to the internet and integrated into the server’s software, remain inherently more vulnerable to server-side exploits. Conversely, hardware wallets ensure that the private keys never touch the server environment, providing a layer of protection that remains effective even if the server itself is fully compromised.

As of the latest reports, BTCPay Server has not published a final, aggregate loss total, as the investigation into the extent of the impact on various individual operators continues. The incident serves as a significant case study for the broader cryptocurrency industry regarding the critical necessity of rapid patch management. For developers and users of open-source financial tools, the events of late October and early November underscore that security is a continuous process, not a static state. With the vulnerability identified and addressed months ago, the tragedy for many operators was not the existence of a flaw, but the failure to deploy the solution before malicious actors could capitalize on the delay.