Skip to content
PANTHER

LNbits Orders Servers Offline. A Patch Estimate Is Not a Restart Signal.

LNbits has told every operator to stop its servers after a wave of attacks. The warning covers the application—not the entire Lightning Network—and no fixed version has been identified in the notice.

By Panther@0xPnthr

2 min read

Illustration: silver payment terminal switched off beside LNbits shutdown typography; Panther Journal #101.
Illustration: Panther, created with ChatGPT.

Key points

  • LNbits told every operator to stop servers after a wave of attacks; the notice does not name a safe version.

PANTHER JOURNAL #101

The payment server may still look normal. LNbits is asking operators to turn it off anyway.

On November 8 at 13:56 UTC, the project’s official account instructed all LNbits users to stop their servers immediately, citing a wave of attacks and security patches still to be pushed. That is a concrete operational warning for businesses and individuals running the software, even while the technical explanation remains incomplete.

The instruction widened beyond Paywall

An earlier warning concerned the Paywall extension. The later notice addressed all LNbits servers. Operators should follow the broader instruction rather than assume disabling one extension satisfies it.

Bitcoin Security Watcher independently recorded the escalation. TFTC’s November 8 reporting also describes the shutdown and the suspension of the project’s hosted service.

The official shutdown post does not identify affected versions, disclose an attack mechanism or provide an aggregate loss figure. Those gaps prevent a reliable claim that a particular installation is exempt. They also prevent treating every Lightning wallet as affected: the warning concerns LNbits deployments.

One operator’s loss is not the incident total

In a public reply, BitTipBot operator Kevin Ravensberg reported that newly created accounts withdrew 2,285,545 satoshis from his LNbits instance. That equals 0.02285545 bitcoin ($BTC). He placed the activity between 09:22 and 14:00 UTC.

This is an operator’s account of one deployment, not an independently audited total for LNbits. It does not establish how many other servers were compromised or prove that the earlier Paywall concern explains every attack.

Wait for a release and explicit guidance

TFTC reported developer Ben Arc’s estimate that patches could become available within 24–48 hours. An estimate is not confirmation that software has shipped or that restarting is safe.

At this check, the project’s public release page still marked v1.6.2, the September PostgreSQL backup hotfix, as its latest release. The emergency notice did not name that version as a remedy. Operators need the project’s actual security release and subsequent instructions, rather than a countdown inferred from social posts.

For people using a service built on LNbits, an outage can reflect a precautionary shutdown; it does not by itself prove their balance was stolen. Seek status through the service’s established channels and avoid unsolicited recovery offers.

Panther’s earlier BTCPay incident coverage illustrates why application security and funds recovery require separate evidence. No connection between that incident and LNbits has been established here.

Panther Takeaway

If you operate LNbits, follow its instruction to stop the server. If you use an LNbits-powered service, verify its status directly. Keep the distinction clear: a promised patch window, a published fix and permission to restart are three different milestones.

Responses

Links, wallet addresses and contact details are not allowed.

0/1000

No responses yet. Start the conversation.

Panther Journal — The intelligence brief

Stay ahead of the story.

Free. New investigations delivered when published. Unsubscribe anytime.

Launching something?

Work directly with Panther.

Start a project

More from Panther Journal