LNbits Disables Hosted Bitcoin Services and Urges Operators to Halt Servers Following Wave of Attacks

Popular Bitcoin payments and wallet-account platform LNbits has issued an urgent directive calling on all users and node operators to immediately halt their LNbits servers following a wave of coordinated attacks targeting the infrastructure. The sudden shutdown instruction has introduced significant operational friction across the ecosystem, directly interrupting live payment processing, retail checkouts, tipping tools, and donation services while administrators await comprehensive security patches and explicit restart guidance from the development team.

In official communications shared across social media channels, LNbits confirmed that security patches are currently being prepared for deployment and that further updates will be issued as the situation evolves. However, the lack of an immediate, all-clear timeline has left merchants and platform operators in a state of uncertainty regarding when normal operations can safely resume.

The project’s official product documentation outlines a wide array of utility tools heavily relied upon by merchants, creators, and community spaces. These include point-of-sale systems, online checkout integrations, customizable donation buttons, digital tipping widgets, underlying wallet accounts, and developer APIs. The platform operates primarily by facilitating both self-hosted and managed deployments that draw liquidity and transaction capability from underlying Lightning Network funding sources, making it a critical bridge for merchants looking to accept decentralized microtransactions and sovereign digital currency payments.

The security crisis unfolded in stages across the weekend of November 8 and November 9, 2026. In an initial notice published on November 8, LNbits announced that it had proactively disabled all active instances across its own managed, hosted service as a precautionary measure to insulate users from ongoing threats. At the time, project representatives expressed optimism that hosted services would resume normal operations within a 24-hour window.

However, as the security assessment deepened, the scope of the emergency widened to encompass independent operators. For self-hosted operators—individuals and businesses running their own independent instances of the software for Bitcoin payment processing—the directive was clear: halt the active LNbits instance immediately to mitigate exposure. While hosted customers are entirely dependent on the provider’s direct administrative actions, self-hosted operators must manually intervene to secure their localized servers, creating a fragmented response across the global user base.

LNbits disables hosted Bitcoin services with no restart timeline

The project’s warning effectively spans both major hosting arrangements, though the pathways to mitigation differ significantly. Industry observers have noted that while a development merge has taken place, it does not automatically translate into a stable security release or immediate restart clearance for production environments, leaving operators to weigh business continuity against severe cybersecurity risks.

Latest Stable Release Predates the Shutdown Warning for Bitcoin Payments

A critical point of confusion for many operators has been the discrepancy between active development repositories and officially designated stable releases. As of November 9, data from GitHub’s latest-release application programming interface still identified version 1.6.2 as the most recent stable release for LNbits. Published originally on September 18, the accompanying release notes for v1.6.2 described a routine PostgreSQL backup hotfix rather than an emergency security patch suite.

Subsequent development activity moved rapidly behind the scenes. On November 9, LNbits merged pull request #4310 into its primary development branch. Code descriptions associated with this pull request outline crucial hardening measures, including stronger request protections, mechanisms to block the server from making unauthorized requests to itself, and the disabling of new-account creation by default to prevent unauthorized administrative escalation or resource abuse.

Despite the merger of pull request #4310 into the development branch, no official all-clear has been published on the project’s public timeline. Neither of the two primary notices issued by LNbits announced formal restart clearance or verified that the newly merged code was fully prepared for general production deployment. Consequently, operators are currently grappling with two distinct operational questions: determining precisely which released software version definitively addresses the vulnerabilities exploited in the recent wave of attacks, and ascertaining when the core project maintainers will explicitly clear servers to restart without risk of compromise.

Until official, verified builds are pushed through stable release channels alongside explicit instructions, the broader LNbits ecosystem remains on high alert, with payment gateways offline and administrators monitoring development channels for further guidance.