LNbits releases emergency fix after thefts from Lightning wallets
The developers of the open-source software LNbits released version 1.7.0 on 10 November 2026 and describe it as a critical security fix. Since 8 November, attackers had been exploiting a flaw that, according to LNbits, puts funds on servers running any older version at risk. Operators should upgrade before restarting their servers and replace their keys and credentials.

In brief
- LNbits released version 1.7.0 on 10 November 2026 and urged all operators to upgrade immediately.
- According to LNbits, funds on servers running any version before 1.7.0 are at risk.
- LNbits has not yet published the technical details of the flaw, the total losses or the number of affected servers.
- The operator of one affected instance said attackers withdrew 2,285,545 satoshi from it on 8 November, roughly 0.023 BTC.
- According to LNbits, upgrading does not revoke access an attacker may already have obtained, so operators should also replace keys and credentials.
Article contents
A call to shut down servers immediately
LNbits is open-source software that merchants, communities and wallet services use to set up accounts and wallets for their users on the Lightning Network. It runs on top of the operator’s own Lightning node or on a third-party service and keeps funds online.
On Sunday 8 November 2026, at around 13:30 Prague time, the LNbits team advised operators to disable the Paywall extension because of a possible vulnerability, according to Bitcoin.com News and TFTC. About an hour and a half later it called on X for all operators to stop their servers immediately. According to TFTC and Cointelegraph, the team itself shut down the instances in its hosted service, my.lnbits.com.
The same day, according to TFTC, the project’s creator Ben Arc estimated that a fix would be ready within 24 to 48 hours. Version 1.7.0 was released on 10 November, after roughly two days.
Funds running on prior versions of LNbits are at risk of being stolen.
What is known about the damage
The only concrete figure on the damage comes from Kevin Ravensberg, who runs an instance for BitTipBot, a Telegram tipping service. According to his statement, reported by Bitcoin Magazine and Cointelegraph, attackers created new accounts on his instance on 8 November between 10:22 and 15:00 Prague time and withdrew 2,285,545 satoshi, roughly 0.023 BTC. According to TFTC, he promised to repay the affected BitTipBot users from his own funds.
The LNbits team has not yet said exactly how the attack worked. It promised details in a separate report. No one has yet substantiated any speculation about which part of the software contains the flaw.
What the new version brings
The release notes on GitHub describe version 1.7.0 as a critical security fix with extensive security hardening. The changes concern sign-in, extension management and payment processing, but the notes do not list individual vulnerabilities or their CVE identifiers.
According to the same notes, the version also adds new features, such as two-factor authentication, on-chain wallets and BOLT12 payments. It also moves to Python 3.13 and the Pydantic 2 library.
What operators must do
In its announcement of 10 November, LNbits asks operators not to run an older version any more and tells them to take the following steps:
Set up a new server if you suspect a compromise
If you suspect your server has been compromised, first save your logs and records, then bring up a new server running version 1.7.0.
Reset wallet keys
A super admin resets the keys of all wallets in the user settings. Users then have to update their apps and integrations.
Replace credentials for the node
Replace the API keys and other credentials for the Lightning node or the service LNbits runs on. Treat all secrets stored in the LNbits settings as compromised.
Reconnect extensions
Recreate the connections of extensions such as NWC Provider, LNDHub, Bolt Cards, TPOS, Bleskomat and FOSSA.
What this means for wallet users
The vulnerability is in the LNbits software, not in the Lightning Network or in the Bitcoin protocol itself. The security of a wallet on someone else’s LNbits server depends on whether the operator has upgraded and replaced the keys. Apart from updating apps after the keys are reset, LNbits has not issued any official guidance for end users.
An LNbits wallet is a hot wallet because it is permanently connected to the internet. In its announcement, LNbits therefore advises keeping only a working balance online, sending any surplus bitcoin to an on-chain wallet with keys stored offline, and regularly checking balances and outgoing payments. The guide Bitcoin wallet explains how the types of wallet differ, and the guide “Lightning Network” (in Czech) explains how fast Lightning payments work.
Frequently asked questions
What is LNbits?
Which LNbits versions are affected?
How much bitcoin did attackers steal from LNbits?
What should a user of a wallet on an LNbits server do?
Sources (6)
- LNbits 1.7.0 security updateLNbits · news.lnbits.com
- LNbits v1.7.0, release notesLNbits (GitHub) · github.com
- LNbits Releases 1.7.0 Urgent Security Update After November 8 Attacks Drain FundsBitcoin Magazine · bitcoinmagazine.com
- LNbits rushes emergency patch after reported Bitcoin wallet theftsCointelegraph · cointelegraph.com
- Lightning Network security scare forces LNbits servers offlineBitcoin.com News · news.bitcoin.com
- LNbits emergency shutdown, active attack, funds drainedTFTC · tftc.io


