News Wallets and security Bitcoin basics
LNbits 1.7.0: security update follows wallet thefts
LNbits released version 1.7.0 on 10 November 2026 following attacks it had warned about two days earlier. The project requires operators to upgrade before restarting and says all previous versions are affected. Where compromise is suspected, recovery also involves replacing secrets and connections: installing the new version cannot invalidate credentials already stolen.
Checked on 11 November 2026.
On 8 November, LNbits' official X account told all users to stop their servers immediately while security patches were being prepared after a wave of attacks. Its official recovery guidance (Opens in a new tab) now sets out the work required before returning to service. This concerns software used internationally, including by payment operators in Israel, rather than a local regulatory requirement.
For anyone who has only heard of Lightning, the first distinction matters: the announcement does not mean every Lightning user was affected. It concerns LNbits and services built on it. Someone with an account at such a service also depends on the operator's response, even if they have never installed a server or run a node themselves.
The software between the funding source and the checkout
LNbits is an open-source system for managing accounts, wallets and payment applications. Its documentation describes support for different funding sources, including LND and Core Lightning. Operators can build user accounts and extensions for functions such as checkout, donations or tips above that connection. It is an application with permissions, not another name for the Lightning protocol.
For example, an operator might connect one source of funds to a service displaying separate accounts for different users. That is an illustration of a possible setup, not a description of a business affected here. Such a service needs credentials that authorise operations. Its security therefore matters even when the funding source runs on a separate computer or service.
Permissions also differ within LNbits. The documentation distinguishes a key that can authorise outgoing payments from a more restricted key used for invoices and reading information. Not every key grants identical control, but an exposed credential with sufficient permissions can remain useful after the software has been fixed. That explains why recovery requires key replacement, rather than a version check alone.
The guide to Lightning payment channels explains how channel payments differ from transactions on Bitcoin's main chain. Here there is another boundary to understand: the network and an account service connected to it. A flaw in that service does not, by itself, establish a failure in the network's rules or identical exposure across all Lightning wallets.
What has been reported about losses
Kevin Ravensberg, the operator of BitTipBot, wrote on X on 8 November that newly created accounts withdrew 2,285,545 sats from his instance before he could stop the server. He gave an attack window of 09:22 to 14:00 UTC that day. This is an operator's report about his own system, not an incident-wide loss total confirmed by LNbits.
The official guidance dates discovery of the vulnerability to 8 November and warns that funds on versions earlier than 1.7.0 are at risk. It promises a separate report explaining the exploit. At the check for this handoff, the guidance reviewed did not provide an aggregate loss estimate or a complete technical account establishing how every attack occurred.
The GitHub release notes describe hardening of authentication, extension management and payment handling, alongside new features. A broad changelog cannot identify the attack path by itself. Nor does the presence of a particular fix prove that the corresponding bug caused this incident. Assigning responsibility to an extension or funding source would require additional evidence.
Recovery extends beyond the LNbits server
The project's first requirement is to install 1.7.0 before operating the service. If compromise is suspected, it recommends a fresh server and preserving relevant logs and records before replacing the old one. Preserving those records has a practical purpose: deleting the environment too early can make it harder to understand the incident and reconcile balances and payments.
Operators should then reset users' wallet keys, revoke and replace funding-source credentials such as API keys or macaroons as appropriate, and rotate other secrets stored in settings. Revocation must also happen at the service that issued the credential. Changing a value displayed in LNbits does not necessarily disable an old key held by another service.
The guidance also calls for reviewing and recreating extension connections. Users and connected applications will need their replacement keys. Operationally, it helps to map the checkouts, bots and other services that depend on those connections. A failure after rotation may reflect a correctly disabled old credential; that is not a reason to keep an exposed credential active to speed up recovery.
What users of someone else's service can check
An end user can ask the operator specific questions: which version is running, whether credentials have been replaced, and whether their connected app needs reconfiguration. A website coming back online cannot prove that its server is clean. Keep available balance and payment records and compare them with the operator's notices, without sending secrets to someone who contacts you offering recovery.
This is another alert involving a self-hosted payment tool after the reported BTCPay Server wallet thefts. Timing alone does not establish a common cause. LNbits advises keeping only working funds online, reviewing outgoing payments and moving excess funds to an on-chain wallet whose spending keys stay offline. The operational lesson is to decide in advance how much money and authority a live service actually needs.