Zimbuck – Your Market. Your Community.

LNbits Tells All Operators to Stop Servers Immediately After Lightning Wallet Attacks

6 min read
0
Comments
506
Views

LNbits, the open-source wallet and accounts system for the Bitcoin Lightning Network, told all operators on November 8, 2026 to stop their LNbits servers immediately amid a wave of attacks. The emergency instruction replaced a narrower warning issued earlier the same day, and the team said security patches are being prepared, with developer Ben Arc estimating they could arrive within 24 to 48 hours — an estimate, not a confirmed release date.

If you run an LNbits instance for a wallet, a business, a community project or a bot, this is not a routine update notice: the message was to shut the server down first and wait for guidance. Readers following the story through Zimbuck News should treat this as an active software security incident, with several important facts not yet confirmed.

What happened on November 8

The escalation happened in stages. Earlier on November 8, at 14:33 Asia/Gaza time, the LNbits team first asked operators to disable the Paywall extension. That step signalled an attempt to close one exposed route while a wider problem was investigated.

By 15:56 the same day, the advice had changed completely: operators were told to stop their LNbits servers immediately. A full shutdown is far stronger than disabling one extension, and it suggests the risk could not be contained by turning off a single feature. Reporting of the notice, including KuCoin's flash coverage of the LNbits shutdown warning, described multiple attack incidents behind the decision.

At the time of writing, no root cause has been confirmed and no CVE has been confirmed. Until the developers publish a technical explanation, nobody can say with confidence which component failed or how attackers got in.

One operator's reported loss — and what it does not prove

One operator, Kevin Ravensberg, self-reported that 2,285,545 sats were withdrawn from his instance between 11:22 and 16:00. That is a serious loss for the operator involved, and the timing helps show why the warnings escalated during the day.

It must be read carefully. That figure is one operator's self-reported loss from his own instance, not a global total, and no global loss total is confirmed. Other instances may have lost funds, some may have lost nothing, and some operators may not yet have checked or reported. Treating one instance as representative of every deployment would go beyond the verified facts. Similar caution applies to everyday wallet scams, which is why our guide on what address poisoning is and how scammers fake wallet addresses stresses checking the source before acting on a frightening claim.

This is an LNbits incident, not proof that Bitcoin or Lightning broke

The most important context is also the simplest: this is an LNbits software incident, not evidence that Bitcoin itself was broken, and not evidence that the Lightning Network itself was broken. LNbits is an application and accounts layer run on top of Lightning infrastructure. A serious flaw in software built on a network is not the same as a flaw in the underlying network or in Bitcoin's base rules.

That does not make the incident small. LNbits is popular precisely because it makes Lightning easier to use. It powers many small wallets, tipping tools, point-of-sale experiments, community projects and bots, often run by individuals or small teams rather than companies with dedicated security staff. Most users interact not with a protocol directly, but with a wallet, an extension and a server somebody maintains — if that layer is compromised, the loss is real, even when the base network operates normally.

What LNbits operators should do now

Follow the developers' emergency guidance first, and share only verified updates with other operators in the Zimbuck Market News group. The practical steps are:

  • Stop the LNbits server immediately if it is still running, as instructed on November 8.
  • Do not restart it just to check whether it works; a restart can reopen the exposure the shutdown was meant to close.
  • Keep the Paywall extension disabled until official patched guidance says otherwise.
  • Preserve logs and records first, including withdrawal times, amounts in sats, and unusual account or extension activity.
  • Check balances carefully and label your figures clearly as your own instance's figures only.
  • Wait for the official patch — the 24-to-48-hour window is an estimate, so follow the project's own channels rather than installing unverified fixes.
  • Warn your users plainly if others held balances on your instance: what is known, what is not, and when you will update them.

Users who only hold a balance inside someone else's LNbits wallet should contact that operator and wait for their instructions. Moving money hastily on rumours, following links in unofficial messages, or handing credentials to anyone offering emergency help can create a second loss on top of the first.

Why this incident matters beyond one project

Lightning wallet security matters because convenience tools spread fast. One open-source system can support many small services, each holding modest balances that add up to meaningful money and real trust, often maintained by volunteers who may learn of an attack from a public warning at the same time as their users. Developers therefore need a fast, clear emergency channel — which LNbits used by escalating publicly from an extension warning to a full shutdown — and operators need to act on such warnings quickly, even when shutting down is disruptive. As more is confirmed, the picture may change; until then, the verified story is the shutdown order, the warning timeline, and one operator's clearly labelled self-report.

Frequently asked questions

Was Bitcoin or the Lightning Network hacked? No such finding has been confirmed. The verified incident concerns LNbits software running on top of Lightning; it is not evidence that Bitcoin or Lightning itself was broken.

How much was stolen in total? No global total is confirmed. The 2,285,545 sats figure is one operator's self-reported loss from his own instance between 11:22 and 16:00, not a network-wide total.

When will the patch arrive? Ben Arc estimated patches could be prepared within 24 to 48 hours — an estimate during a developing incident, not a guaranteed release date.

I use a wallet run by someone else. What should I do? Contact your operator, follow their instructions, keep your records, and never share credentials or seed phrases with anyone offering emergency help.

We will keep following confirmed updates, and you can join the conversation on Zimbuck as the patch and technical explanation are published. This article is market news and general information only, not financial advice.