Live News

LNbits rolls out emergency patch following active Lightning wallet exploits

LNbits rolls out emergency patch following active Lightning wallet exploits

Bitcoin Lightning platform LNbits published an emergency software release on Tuesday after attackers exploited self-hosted instances across the network, leading to stolen Bitcoin funds.

The v1.7.0 update targets vulnerabilities present in every build prior to the release. In the v1.7.0 release notes, developers overhauled authentication protocols, extension management, and payment processing routines to plug the security gaps.

“It’s been a very challenging few days, working relentlessly to get the v1.7 release out after our users and we suffered losses,” project creator Ben Arc wrote on X.

LNbits serves as a modular operating system for Bitcoin Lightning accounts, enabling node runners and merchants to manage payments, launch paywalls, and integrate point-of-sale systems. In a May post on Nostr, Arc noted that roughly 200,000 users run their own instances of the software.

A rapid sequence of warnings and takedowns

The incident escalated quickly over the weekend. On Sunday, the team initially alerted node runners to turn off the Paywall extension while engineers reviewed a suspected flaw.

Roughly an hour later, the advisory escalated into a full shutdown directive. Citing an ongoing attack wave, LNbits advised server administrators to disconnect their systems immediately. LNbits also pulled its own hosted platform offline to limit further exposure.

Node operators soon began reporting unauthorized withdrawals. Operator Kevin Ravensberg stated that an attacker hit his instance, creating fresh accounts on the server to siphon roughly 2.3 million satoshis (0.023 BTC) before he managed to shut down the machine.

Patching code is not enough to stop ongoing theft

In an official advisory detailing the release, the LNbits team stressed that simply pulling the v1.7.0 update will not secure an instance if attackers had already gathered access tokens or private keys during the breach window.

Because the flaw allowed attackers to access stored system secrets, developers instructed administrators to rotate all funding-source API credentials, generate new wallet keys, and replace any sensitive configurations. If an administrator suspects an intrusion already occurred, the project advised abandoning the old installation entirely and rebuilding the environment on a fresh server.

LNbits has not published an aggregate tally of lost funds or the exact number of compromised machines, stating that a technical post-mortem explaining the exploit mechanism will be shared in a separate report.

Tags:
Share:

Related Post