DKDKCISSP
Self-Hosted Payment Server — Wallet Theft

BTCPay Server: the patch was out for twelve weeks and the thieves still found servers that never installed it

A critical flaw let an attacker take a payment server's Lightning credentials. Merchants who never updated were swept months later, with 18.38 BTC and 3,405 LTC traced to the thieves in 682 transfers. BTCPay says the thefts targeted old versions using a different method. How, exactly, is still unclear.

Fix shipped
2.4.2 on Aug 7
Fix-to-sweep gap
84 days
Traced theft (Bitquery, a minimum)
18.38 BTC and 3,405 LTC
Transfers
682 between Oct 30 and Nov 2
Main wave
87% on Nov 1
Method used in November
Not published

Background

BTCPay Server is a free, open-source payment processor that merchants run themselves to accept Bitcoin and other crypto payments. Because they self-host, merchants keep the wallet and the keys instead of handing them to a company, and they also take on the job of patching and securing the server.

Some merchants connect their server to a Lightning Network node, LND, using credential files called macaroons. Others keep an on-chain hot wallet on the server so payments can be processed automatically. Both put spendable keys on an internet-facing machine.

From an August flaw to a November sweep

Critical flaw exposes LND credentialsUnauthenticated attacker, August 2026Fix shipped in 2.4.2Aug 7, 2026Servers on 2.4.1 or older stay unpatchedAbout twelve weeks laterHot wallets swept from Oct 30682 transfers to two addresses by Nov 2Shutdown warning at 22:25 UTC on Nov 1Rebuild on a fresh server and wallet
Fig. 1 — A fixed flaw is still dangerous on every server that was never updated.

What actually happened

In August 2026 BTCPay Server disclosed that a critical vulnerability was being exploited. The flaw let an unauthenticated remote attacker obtain the .macaroon credential files for LND, and those credentials could be used to take control of an LND node and move funds. The attacks BTCPay reviewed targeted only files with the .macaroon extension. A fix shipped in version 2.4.2 on 7 August, and updating to it also updates LND and regenerates its admin macaroon. The project thanked the researchers who disclosed the flaw and funded a recovery bounty of 10% of any amount recovered, up to 3 BTC.

On 2 November BTCPay said new thefts from hot wallets had hit servers running 2.4.1 (released 23 July) or earlier, and that attackers used a different method to exploit the vulnerability fixed in 2.4.2. Blockchain analytics firm Bitquery traced 18.38 BTC and 3,405 LTC to two addresses BTCPay named, moved in 682 transfers between 30 October and the morning of 2 November. That is about $1.62 million. It said 87% of the money moved in one wave on 1 November, between 14:12 and 22:16 UTC, and that the thief signed in to the servers as an administrator.

BTCPay told operators to shut down at 22:25 UTC on 1 November. Bitquery counted 267 further transfers, worth about $150,000, after that warning. BTCPay's advice for anyone on 2.4.1 or earlier was to move to a fresh server with a new wallet and seed, even if they had not seen a theft and even if they had since updated, because updating alone cannot remove access an attacker may already have. Operators on a hosting provider may have had their instance shut down automatically. BTCPay reported no credible hot-wallet drains on version 2.4.7.

Still unknown: how the attackers got in this timeBTCPay says the November attackers used a different method against the vulnerability fixed in 2.4.2, and that they signed in as an administrator. The exact method, when exploitation began, how many servers were hit, and whether credentials stolen in August were reused have not been published. Bitquery's total is a floor, and BTCPay says some activity at the two addresses predates the reported thefts, so the balance is not a confirmed loss figure. BTCPay has not published a loss total.

Root cause

Confirmed
  • A critical flaw in BTCPay Server let an unauthenticated remote attacker obtain LND .macaroon credential files, which let them take control of the LND node and move funds. Fixed in 2.4.2 on 7 August 2026.
  • The November thefts hit servers running 2.4.1 or earlier, using a different method against the vulnerability fixed in 2.4.2, according to BTCPay.
  • Hot wallets held on the server could be swept once the attacker had access, and the thief signed in as an administrator, according to Bitquery.
  • The servers hit had not updated for about twelve weeks after the fix shipped (7 August to 30 October).
  • BTCPay says updating alone cannot remove access an attacker may already have gained.
Reasonable hypothesis — not confirmed
  • Credentials or secrets taken in August may have been reused in November. Neither BTCPay nor the press confirmed this.
  • The November method may have exposed administrator credentials or sessions. That is an inference from Bitquery's observation of an administrator sign-in.
  • Why some servers stayed on old versions for twelve weeks, whether through neglected installs, missing update notices or hosting set-up, has not been reported.

Timeline

A critical flaw is used to take LND macaroon credentials from BTCPay instances and move funds. BTCPay discloses it.
T1657 · Financial Theft
Version 2.4.2 ships. Updating also updates LND and regenerates its admin macaroon.
BTCPay donates 0.21 BTC to each of the two disclosing parties and funds a recovery bounty with help from supporters, working with exchanges and analytics firms.
Servers that were not updated carry on running, with spendable keys on an internet-facing machine.
A wallet of 42 addresses is emptied into a second wallet tied to the thief, less than a day after version 2.4.7 shipped.
T1657 · Financial Theft
87% of the traced money moves in one wave, with Litecoin sweeps starting that day and Bitcoin within the hour.
BTCPay tells operators to shut down instances. Bitquery counts 267 more sweeps, worth about $150,000, after this.
BTCPay says servers on 2.4.1 or earlier were targeted and urges operators to rebuild on a fresh server and wallet.
Fig. 2 — The fix was public for twelve weeks before the sweeps began.

Detection

How it was discovered

Operators reported stolen funds to BTCPay, and the project then investigated and named two thief addresses. Bitquery traced the money on-chain. Reports began around 1 November, and when the attackers first began is not known.

Time to detect

First sweep on 30 October. Reports from operators around 1 November. Shutdown warning at 22:25 UTC on 1 November.

Warning signs that were missed
  • Servers on version 2.4.1 or earlier were still online twelve weeks after a critical fix, with no process telling their owners.
  • Administrator sign-ins to a payment server from unfamiliar addresses.
  • Large outbound transfers from a hot wallet to an address that had never been paid before.

What to monitor for in your own environment

A server reporting a version older than the latest security release, with a critical fix outstanding for more than a few days

Version inventory and update checks

A successful administrator sign-in from a new IP address or country

Application authentication logs

Repeated outbound sweeps from one wallet to a new address, especially in many small transfers

Wallet and node transaction logs, or an on-chain monitor

Spending from a hot wallet far above its normal daily volume

Payment and wallet alerts

Access to credential files such as .macaroon files from outside the application

Web server and file access logs

Containment, eradication & recovery

Containment

Nov 1 – 2
  • Told operators to shut down instances at 22:25 UTC on 1 November, and published two thief addresses so exchanges and analytics firms could watch them.
  • Hosting providers may have shut instances down automatically to stop older versions being exploited.
  • Asked affected operators to report to BTCPay, to local authorities and to any exchange the stolen funds reached.

Eradication

Nov 2 onward
  • Told anyone on 2.4.1 or earlier to treat the whole machine and all its secrets as compromised, and to move to a fresh server with a new wallet and seed, even without a visible theft.
  • Advised enabling two-factor authentication, changing administrator passwords and rotating API keys.
  • Version 2.4.7 fixed one critical and several medium-severity flaws found through a scan with Anthropic's open-source scanner.

Recovery

Aug – Nov 2026
  • Funded a recovery bounty of 10% of any amount recovered, up to 3 BTC, with help from exchanges, analytics providers and law enforcement.
  • Is adding code-scanning and review with outside organisations and is putting security releases ahead of new features for now.
  • Advised keeping only operating funds on the server and moving the rest to cold storage, or to a wallet whose spending keys are held off the server.

Security control analysis

Failed
Authentication of the credential files and admin surface

An unauthenticated remote attacker could obtain LND macaroon files in August. In November the thief signed in as an administrator.

Failed
Patch management on self-hosted servers

Servers on 2.4.1 or earlier were still online about twelve weeks after the 2.4.2 fix.

Failed
Hot wallet key custody

Spending keys sat on an internet-facing server, so one compromise emptied the wallet. BTCPay says wallets with spending keys held off the server were not affected.

Partial
Credential rotation after a fix

Updating to 2.4.2 regenerates the LND admin macaroon, but BTCPay warns updating alone cannot remove access an attacker already has.

Held
Vulnerability disclosure and recovery bounty

The flaw was reported responsibly, BTCPay thanked and paid the researchers, and funded a bounty to recover funds.

Partial
Incident communication

BTCPay published clear steps and addresses, but the shutdown warning at 22:25 UTC came after the main wave, and 267 more sweeps followed.

Unknown
Monitoring for new-address administrator sign-ins and large outbound sweeps

There is no public detail on whether any merchant had alerts, or whether they would have fired in time.

Controls that would have prevented or limited this

Fix
Keep only the operating balance on a server-side wallet, and move the rest to a wallet whose spending keys are held off the server

A compromised server could only reach the small balance it holds, not the merchant's reserves.

Closes: Hot wallet key custodyCIS Control 3 — Data Protection
Fix
Subscribe to the project's security releases and apply critical updates within days, with a named owner for each server

Servers on 2.4.1 or earlier would have been updated within days of 7 August, not left online for twelve weeks.

Closes: Patch management on self-hosted serversCIS Control 7 — Continuous Vulnerability Management
Fix
After any credential-exposing flaw, rotate every secret on the host and rebuild from a clean image if compromise is suspected

Access an attacker already gained cannot be reused after the patch.

Closes: Credential rotation after a fixCIS Control 5 — Account Management
Fix
Turn on two-factor authentication for administrators, restrict the admin interface to known addresses and monitor sign-ins

A stolen or reused credential would not by itself give a thief administrator access.

Closes: Authentication of the credential files and admin surfaceCIS Control 6 — Access Control Management
Fix
Alert on large or repeated outbound wallet sweeps to new addresses and on an administrator signing in from somewhere new

The first sweep on 30 October would have been seen on the day.

Closes: Monitoring for new-address administrator sign-ins and large outbound sweepsCIS Control 13 — Network Monitoring and Defense

Blast radius

What was taken

  • 18.38 BTC and 3,405 LTC traced to two addresses, about $1.62 million, per Bitquery. A minimum, not a confirmed loss total.
  • Hot-wallet funds on servers running 2.4.1 or earlier
  • In August, funds reachable through stolen LND macaroon credentials
  • All secrets on an affected machine, which BTCPay says to treat as compromised

What stayed safe

  • Servers on 2.4.2 or later when BTCPay issued its warning, with no credible drains reported on 2.4.7
  • Wallets with spending keys held off the server, such as hardware wallets
  • Standard on-chain wallets in August, per BTCPay's earlier statement, though November's thefts hit on-chain hot wallets
Fig. 3 — Reach was set by where the keys lived and which version a server ran.

Time between the fix and the sweeps

Fix released → first sweep seen84 daysFirst sweep → shutdown warning2 daysShutdown warning → sweeps still counted by Bitquery267 more
Fig. 4 — The long gap was before the attack. The two-day gap after it is the part that a monitor could close.

What they got right

BTCPay disclosed the August flaw promptly, shipped a fix that also regenerates the LND credential, and paid the researchers who disclosed it.

It funded a recovery bounty and worked with exchanges, analytics firms and law enforcement to trace and freeze funds.

It told operators plainly that updating is not enough and that a fresh server, wallet and seed are needed, which is the hard advice.

It published the two thief addresses and the affected version range, so merchants could check quickly.

It apologised to those who lost funds and said it would put security above new features.

Why this keeps happening

Self-hosting hands the patching job to every merchant. Some have no process, no owner and no alert when a release lands.

A fix does not undo a compromise. If credentials leaked before the patch, an attacker may keep them for months.

Hot wallets put spendable keys on an internet-facing server, so one flaw can mean total loss.

Lessons for your own environment

  1. Patch a critical flaw in days, and track it

    Twelve weeks separated the fix from the sweeps. Give every server an owner and a rule for how fast critical updates land.

  2. Updating does not evict a thief

    Anything an attacker took before the patch is still theirs. Rotate secrets and rebuild from a clean image when compromise is possible.

  3. Keep only operating funds where the keys are online

    Spending keys held off the server were unaffected. The less a compromised server can spend, the smaller the loss.

  4. Watch the outflow, not just the inflow

    The first sweep emptied a 42-address wallet. Alerts on new-address transfers and unusual volume are cheap to add.

  5. Warn early and loudly

    267 more transfers happened after the shutdown warning. Hosting providers shutting old instances down automatically is the same idea at scale.

  6. Be honest about what is not known

    BTCPay stated it was unclear how the attackers got in and refused to treat the address balance as a loss figure. That precision is what readers can trust.

CISO & board lessons

  • Ask which of your internet-facing, self-hosted systems hold spendable keys or secrets, and who owns patching each one.
  • Set a maximum time for critical security updates on self-run software, measure it, and report exceptions.
  • After any flaw that exposed credentials, require secret rotation and a rebuild decision as part of closing the ticket, not only the patch.
  • Limit what a single compromised host can spend or move, and keep reserves where the keys are offline.
  • Pre-agree with your hosting provider or platform team how outdated instances are warned, isolated or shut down.

Action plan

First 24 hours

  • Shut down any instance on 2.4.1 or earlier, and keep it offline until it is rebuilt.
  • Move funds out of the hot wallet to a new wallet with a new seed phrase, on a fresh server.
  • Report any theft to BTCPay, to local authorities and to any exchange the funds reached, with addresses and transaction details.

First 7 days

  • Rebuild on a fresh server on version 2.4.7 or later, and treat the old machine and every secret on it as compromised.
  • Change administrator passwords, enable two-factor authentication and rotate every API key.
  • Review sign-in and outbound transaction logs for the period since August.

First 30 days

  • Cut the server-side balance to what daily operations need, and move the rest to cold storage.
  • Subscribe to security release notices, assign an owner and write down the maximum time to apply critical updates.
  • Add alerts for new-address administrator sign-ins and for large or repeated outbound sweeps.

Could this happen in your organization?

  • Do you know which version every self-hosted payment or wallet server is running right now?
  • Is there a named owner and a deadline for applying critical updates on each one?
  • If a credential-exposing flaw were fixed today, would you rotate every secret and consider a rebuild, or only patch?
  • How much could a single compromised server move before anyone noticed?
  • Would you see an administrator signing in from a new place, or a wallet sweeping to a new address?
  • Are your reserves held where the spending keys are offline?

If this happened to you: what to ask, and what to say

Knowing the lesson isn’t the same as knowing what to do with it Monday morning. A security lead, a CISO, and a customer-facing team each need something different from this incident.

  • “What version is every server on, and who would notice if one fell behind a critical fix?”
    Twelve weeks went by with no one noticing.
  • “If a credential file leaked before we patched, would the patch evict the attacker?”
    BTCPay says updating alone cannot remove access already gained.
  • “How much can one server spend on its own?”
    Keep it to the operating balance.
  • “What alerts when funds leave to a new address?”
    The first sweep was seen on 30 October. An alert could have caught it that day.
  • Explain the cause in plain terms.
    A flaw was fixed, but servers that never updated were still open.
    “A flaw let attackers take the credentials of our payment server. A fix was available for twelve weeks, but some servers were never updated, and wallets on those were emptied.”
  • Separate what is confirmed from what is not.
    The November method and the loss total are not public.
    “The version range and the thief addresses are confirmed. How the attackers got in this time, and the total loss, have not been published, and we will not guess.”
  • Show the fix is broader than one product.
    Boards want to know self-hosted systems are covered.
    “We now track versions on every self-hosted system, apply critical updates within a set number of days, and keep only operating funds on any server that holds keys.”
  • Tell merchants exactly which versions are affected.
    Be specific.
    “Servers running 2.4.1 or earlier were targeted. If you are on one of those, shut it down, move your funds to a new wallet, and rebuild on a fresh server.”
  • Say plainly that updating is not enough.
    It is the hard message.
    “Updating cannot remove access an attacker already has. If you were on an affected version, treat the machine and everything on it as compromised.”
  • Explain what is changing.
    Concrete actions beat apologies.
    “We are adding code scanning and external review, putting security fixes ahead of new features, and working with exchanges and analysts to trace and freeze stolen funds.”

References & confidence

  • ConfirmedBTCPay Server — Security Incident: Our Response and Next Steps (blog) — Primary source for the August vulnerability, the fix in 2.4.2, the bounty and the response steps.
  • ReportedThe Hacker News — Hackers Exploit BTCPay Server Flaw to Steal Bitcoin and Litecoin From Hot Wallets (Nov 3, 2026) — Quotes BTCPay's incident update, the 2.4.1 and 2.4.2 versions and the Bitquery figures.
  • ReportedInfosecurity Magazine — Hackers Exploit BTCPay Server Flaw to Steal Cryptocurrency (Nov 3, 2026) — Source for the 22:25 UTC shutdown warning, the 267 later transfers and the caveat that Bitquery's figure is a floor.
  • ReportedBitquery — on-chain trace of the sweeps — Read through press coverage; we did not read the analysis itself.
  • DisputedWhether the November method matches the August flaw — BTCPay says a different method was used against the flaw fixed in 2.4.2. The Hacker News says it is unclear whether the attacks are related to the same vulnerability.
  • UnknownTotal confirmed loss and number of affected servers — Not published.
This case study is built entirely from public reporting on this incident — see References & confidence above for what's confirmed, reported, or still unconfirmed. Nothing here is an estimate or an illustrative placeholder.