We checked this claim: is it true that

unauthorized attackers breached administrator accounts to drain hot wallets on older BTCPay Server installations?

Confirmed

BTCPay Server confirmed older versions through 2.4.1 are vulnerable to administrator-level wallet drains while version 2.4.7 remains secure

Crypto
  • ClaraAuthorComing December 1
  • JolinaMarketingComing December 1

BTCPay Server warns of hot-wallet thefts

Self-hosted merchants face wallet drains unless they halt and patch outdated software

Published
Quantum Otter — crypto markets and AI trading bots

In a nutshell

BTCPay Server ordered merchants worldwide to take their checkout servers offline after intruders exploited administrator access to drain online Bitcoin wallets. The project isolated the vulnerability to version 2.4.1 and older, confirming the current version 2.4.7 is secure, but the lack of centralized patching leaves independent store owners responsible for stopping the thefts themselves.

Highlights

  • BTCPay Server issued an emergency shutdown alert on November 1, 2026, following active wallet drains
  • The exploit affects software deployments running version 2.4.1 and earlier from July 2026
  • The project confirmed no verified breaches on current release version 2.4.7
  • Merchants must shut down servers, check ledger histories, rotate credentials, and upgrade to stop attacks

From the Editor’s Diary

Self-hosted payment networks eliminate middleman fees, but they shift full operational risk onto merchants who must patch software themselves when security breaks.

Who's involved

  • BTCPay Server

    open-source payment processing software project

    goal → prevent automated fund drains and patch software vulnerabilities

  • Nicolas Dorier

    co-founder and lead developer of the payment project

    goal → identify compromised versions and guide merchants through emergency repairs

  • cryptocurrency merchants

    business owners operating independent payment checkout nodes

    goal → stop financial theft and restore customer checkouts safely

  • unidentified threat actors

    unauthorized intruders exploiting administrative access

    goal → compromise administrative privileges to sweep merchant funds

In short

Merchants using BTCPay Server face immediate losses from automated digital wallet sweeps if their payment systems are not patched. The open-source payment software, which businesses run on their own servers to take Bitcoin payments, ordered an emergency shutdown after attackers seized administrator controls and drained connected digital cash registers, known as hot wallets.

Operators running outdated deployments will have to take their stores offline and manually apply updates to halt further thefts.

Whether merchants avoid recurring losses is uncertain because operators run the software independently without automated central updates.

How it unfolded

01

Emergency shutdown alert issued on X

2026-11-01 – 2026-11-01

The breach surfaced on November 1, 2026, at 22:25 UTC when the official BTCPay Server account on social platform X warned operators that thieves were actively emptying hot wallets. The project urged merchants to shut down their payment engines immediately using terminal scripts while core developers investigated the vector.

1 source
02

Attack vector isolated to legacy software

2026-11-01 – 2026-11-02

The initial panic shifted to targeted maintenance after developers reviewed server logs and identified the vulnerability. Co-founder Nicolas Dorier confirmed that while intruders obtained administrator privileges, the exploit affected only legacy deployments running version 2.4.1 or older. The team found no compromises on the latest release, version 2.4.7, and issued step-by-step instructions for resetting passwords and updating code.

2 sources

Where things stand

BTCPay Server maintains that installations on version 2.4.7 are safe, though total merchant financial losses and the precise method used to steal administrator credentials remain unconfirmed. Developers continue to examine user log files to determine whether the intruders used an external weakness or an internal software bug.

Sources