Act nowVulnerabilities

BTCPay Server flaw is being used to steal Lightning funds: if you run LND, update to 2.4.2

BTCPay Server's own advisory says every version before 2.4.2 lets an unauthenticated attacker obtain LND credentials and move funds, and that attackers have already stolen money. The advisory dates from 7 Aug 2026 and the project updated its pages on 2 Nov, when press headlines said thefts on outdated instances continue. Who is exposed and what to do.

How urgent

Act now

Who is affected

Anyone who runs their own BTCPay Server (the open-source payment server for accepting Bitcoin) on a version older than 2.4.2 with the LND Lightning backend. The project says BTCPay's own on-chain wallets are not affected

What to do

If you run BTCPay Server with LND, update to 2.4.2 now (Server Settings, Maintenance, Update), check the admin footer shows 2.4.2, rotate the credentials of any LND access you set up yourself, and review your node for payments or channel closures you did not make. If you cannot update today, take the server offline

Published 3 Nov 2026 · Sources last checked 3 Nov 2026No. 44 / 87

What happened

BTCPay Server, an open-source tool that businesses host themselves to accept Bitcoin, published a security advisory dated 7 August 2026. It says every version before 2.4.2, including the 2.4.2 release candidates, has a critical flaw. An unauthenticated attacker on the internet could obtain the LND credential files (macaroons) of an instance. Those files can give control of an LND Lightning node and let the attacker move its funds. The advisory confirms that attackers exploited it and stole funds. The project withholds the technical details so operators have time to update.

The project updated both pages on 2 November 2026. A BleepingComputer headline the same day says thefts continue on outdated instances. We could not open that article, so we do not know what it adds.

Who is affected, and who is not

  • LND users are at risk and should update immediately.
  • Other Lightning backends and non-Lightning users do not face the LND credential risk. The project still encourages them to update.
  • BTCPay's own on-chain wallets, including hot wallets, are not affected. An earlier precaution to move on-chain funds out was withdrawn. Funds in LND's own on-chain wallet belong to the affected node and may still be at risk.

What to do

Steps follow the project's advisory; the numbering is ours.

  1. Update to 2.4.2. On a standard install go to Server Settings, Maintenance, Update, then confirm the admin footer shows 2.4.2 and that LND is 0.21.1. If unsure the update applied, run it again. On a self-managed install, use your normal update process.
  2. The update regenerates the LND admin credentials. You can also rotate them by hand.
  3. Rotate any other route to LND that you set up yourself: your own reverse proxy, a Tor service or a forwarded port. Updating BTCPay does not close those.
  4. If you cannot update today, take the server offline. Do not leave an affected LND deployment reachable from the internet.
  5. Check the node after updating: payments you did not make, unexpected channel closures or unfamiliar peers, and whether on-chain and channel balances match your records.
  6. If you lost funds, the project asks you to email [email protected] with the addresses and transactions, and to report the theft to the authorities.

Note: version 2.4.2 removes public access to the LND API on Docker deployments, so external wallets such as Zeus cannot connect through your BTCPay domain or Tor address for now.

If you accept crypto for your business

Our advice, not the project's: keep most funds in cold storage and move excess funds out of hot wallets regularly, as the project also recommends, and treat a self-hosted payment server as a production system that needs updates like any other.

What we could not confirm

The project's pages say some users lost funds but give no total and no number of victims. They do not name the attacker or say whether funds were recovered, and the technical details are withheld. We could not open the 2 November press article, so we do not know whether it reports new attacks or repeats the August ones. Supporters are funding a bounty of 10% of recovered funds, up to 3 BTC.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks