We checked this claim: is it true that
all earlier LNbits versions were identified as vulnerable and operators were warned that upgrading without replacing compromised credentials might leave funds at risk?
LNbits released version 1.7.0 patching exploited flaws and warned that unrotated credentials leave funds exposed
JolinaMarketingComing December 1
LNbits patches exploited wallet flaw after fund drains
Open-source Lightning tool releases version 1.7.0 and warns operators that stolen credentials still put funds at risk
In a nutshell
Attackers used previously unknown flaws in LNbits, the open-source tool many people run to manage Bitcoin Lightning wallets and hold balances for others, to drain funds from self-hosted nodes. The developers released version 1.7.0 on 11 November that closes the holes, yet they and security firm 0xCERT both warn that any credentials already stolen remain usable until operators generate new ones. Because node runners often custody money for multiple end users, an unpatched or unrekeyed instance can wipe out both the operator and everyone connected to it. The amount taken so far is still unknown and further losses depend on how quickly each operator acts.
Highlights
- LNbits issued version 1.7.0 after attackers drained funds from self-hosted nodes
- All versions before 1.7.0 contain the vulnerabilities attackers actively used
- Operators must replace API keys and administrative credentials after the upgrade
- 0xCERT confirmed the flaws and the risk that stolen credentials persist
- Total volume of funds siphoned remains unconfirmed
From the Editor’s Diary
In Lightning infrastructure that holds money for other people, a code patch alone does not restore safety once credentials may already have left the machine; only deliberate key rotation closes the window attackers still have.
Who's involved
LNbits Development Team
open-source software maintainers of the LNbits Bitcoin Lightning suite
goal → remediate zero-day vulnerabilities, safeguard user funds, and push security releases
Unidentified Attackers
malicious actors exploiting unpatched LNbits instances
goal → extract API credentials and siphon Bitcoin funds from vulnerable Lightning nodes
Node Operators and Merchants
individuals and businesses running self-hosted LNbits instances
goal → protect hosted balances and restore secure operations by patching and rotating secrets
0xCERT
blockchain and software security advisory firm
goal → investigate security incidents and disclose vulnerability impact to the community
In short
Self-hosted Bitcoin Lightning nodes that use LNbits software remain open to further fund theft until their operators both install the emergency patch and replace any credentials attackers may already have copied.
The most important thing this makes likely next is that node operators will update to version 1.7.0 and generate fresh API keys and administrative credentials so previously stolen access no longer works.
This is likely, because the patch is already public and the warning is explicit, but success depends entirely on each operator acting by hand and the total amount already taken remains unknown.
How it unfolded
Discovery of Active LNbits Exploits and Unauthorized Drains
Automated monitoring and reports from independent node operators identified unauthorized withdrawals from LNbits instances, prompting security researchers and core developers to investigate zero-day vulnerabilities in previous releases.
Emergency Patch Release and Credential Rotation Warning
In response to the active compromises, the LNbits team published emergency release 1.7.0 and declared every earlier version vulnerable. Advisories warned that simply installing the new code would not be enough: attackers who had already copied API tokens or administrative credentials could still reach the wallets unless those secrets were revoked and replaced.
Where things stand
LNbits version 1.7.0 is publicly available, but remediation depends entirely on individual server operators manually updating installations and invalidating compromised keys. The total financial volume siphoned across affected nodes remains unconfirmed, and investigators continue to monitor network telemetry to determine whether automated bots are sweeping unrotated instances.
