What the project confirms
LNbits published version 1.7.0 on 10 November and describes it as an urgent security release. Its separate operator notice says a vulnerability discovered on 8 November affects all earlier versions and puts funds at risk of theft.
Independent reporting documented attacks on user-operated instances and one user report of about 2.3 million satoshis stolen. That individual report is not a verified aggregate loss figure.
Updating cannot evict an existing attacker
LNbits explicitly warns that credentials exposed before the upgrade may remain useful afterward. A software update changes code; it does not invalidate API keys, wallet keys, funding-source macaroons or secrets already copied from a compromised system.
The project recommends a fresh server when compromise is suspected and says operators should preserve relevant logs before replacing the old host.
Practical implications: operator checklist
- Keep the instance offline until version 1.7.0 is installed.
- Use a fresh server if the old system may have been accessed.
- Reset all LNbits wallet keys from the super-admin user settings.
- Replace funding-source API keys, macaroons and other credentials.
- Rotate every secret stored in LNbits settings and recreate extension connections.
- Review balances and outgoing payments, then move excess funds to keys held offline.
Risks and what to watch next
The exploit path, affected component, number of compromised installations and total losses remain unknown. LNbits says a separate report will provide full details. Until then, operators should not assume that a single listed feature or extension was the only entry point.
Watch for a technical advisory, indicators of compromise and any follow-up release that narrows the remediation steps.
Sources you can open
01Download releases only from the official LNbits repository. Preserve forensic logs before rebuilding a suspected compromised server.