Incidents

BTCPay Server Confirms Hot Wallet Thefts on Versions 2.4.1 and Earlier, Urges Operators to Rebuild Servers and Replace Wallets

Attacks hit BTCPay Server 2.4.1 and earlier via a flaw patched in August. Operators of affected instances should rebuild the server and replace wallets.

BTCPay Server Confirms Hot Wallet Thefts on Versions 2.4.1 and Earlier, Urges Operators to Rebuild Servers and Replace Wallets

On November 2, BTCPay Server published its findings on thefts of funds from wallets that store their keys on the server. The attacks affected version 2.4.1 and earlier. The project recommends updating the software. For affected instances, it also recommends moving to a new server and a new wallet.

What’s new

The public warning was issued on November 1 at 22:25 UTC. The next day, the project named the affected versions. Its official write-up confirmed that the attackers used a different method to exploit a vulnerability fixed in version 2.4.2, released on August 7, 2026.

BleepingComputer reported that the attackers gained administrative access and that the project urged users to update to version 2.4.7. The total number of victims and the overall losses have not been confirmed.

Who the warning applies to

According to BTCPay, no impact from these attacks has been observed on servers that were already running version 2.4.2 or later when the November 1 warning went out. The rebuild recommendation covers instances on 2.4.1 and earlier. That includes instances that were updated only after the warning.

What to do now

  • On a trusted device, create a wallet with a new recovery phrase and move any remaining funds to it.
  • Shut down the old server, but keep its logs and transaction history.
  • Deploy a fresh machine running the current version of BTCPay. Do not restore the entire old server.
  • Revoke and replace any passwords and access keys that may have been exposed.
  • Report the incident to security@btcpayserver.org, without sharing any secrets.

SecurHUB commentary

Updating closes the vulnerability, but it does not undo an earlier server compromise. Incident response should include preserving evidence, assessing which secrets were exposed, and rebuilding the environment securely.

Sources: BTCPay Server, BleepingComputer, Cointelegraph

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk