Bitcoin funds and wallet-account platform LNbits has known as on all customers to cease their LNbits servers after reporting a wave of assaults.
Stopping these servers can interrupt fee, checkout, and tipping companies whereas operators await safety fixes and clear restart steerage. LNbits stated it had safety patches to push and would offer additional updates.
The undertaking’s product description lists point-of-sale instruments, on-line checkout, donation buttons, tipping, pockets accounts, and APIs. It helps each self-hosted and managed deployments over underlying Lightning funding sources.
In a separate Nov. 8 discover, LNbits stated it had disabled all situations on its hosted service as a precaution and anticipated companies to renew inside 24 hours.
For self-hosted operators, the request is to cease the LNbits occasion they run for Bitcoin funds. Hosted clients as a substitute rely upon the supplier’s motion, which LNbits stated it had already taken.
The undertaking’s shutdown warning spans each internet hosting preparations. A growth merge shouldn’t be a secure safety launch or restart clearance.
Level-in-time public materials, about 18:20 UTC Nov. 9, 2026. Hosted shutdown is attributed to @lnbits; restoration was solely an estimate. PR #4310 shouldn’t be established because the assault treatment, and no restart clearance was seen within the reviewed notices/timeline.
Newest secure launch predates the shutdown warning for Bitcoin funds
As of Nov. 9, GitHub’s latest-release API nonetheless recognized v1.6.2 as LNbits’ newest secure launch. Printed Sept. 18, its launch notes describe a PostgreSQL backup hotfix.
LNbits merged pull request #4310 into its growth department on Nov. 9. The descriptions cowl stronger request protections, blocking the server from making requests to itself, and disabling new-account creation by default.
No all-clear was seen on LNbits’ public timeline, and neither of its two notices introduced restart clearance.
Operators face two separate questions: which launched model addresses the incident, and when the undertaking will explicitly clear servers to restart.
