Bitcoin Lightning Network
LNbits Says Shut Down Now. What Operators Should Do Next
LNbits told every operator to stop their servers after a wave of attacks on Nov. 8, 2026. What is confirmed, what is not, and five steps to take now.
On November 8, 2026, LNbits, the free, open-source Lightning wallet and accounts system that Bitcoin hobbyists run on their own servers, told every operator to stop their servers immediately. The LNbits shutdown notice followed what the project called a wave of attacks, and it came with a promise of security patches rather than a patch itself. As of 16:30 UTC on November 9, the newest release on the project's GitHub page is still v1.6.2 from September 18, so the fixed version has not shipped yet.
If you run an LNbits instance, or you hold sats in someone else's, this post walks through what is confirmed, what is not, and the steps that make sense while you wait. It ends with the part that matters for solo miners: why a balance sitting on a server is the thing attackers went after.
What Is Confirmed About the LNbits Attacks
The timeline below comes from the project's own posts on X and from reporting by The Hacker News, Bitcoin.com News and The Defiant. All times are UTC on November 8.
- 09:22 to 14:00. One operator, who runs a Telegram tipping bot on LNbits, says new accounts created on his server used an exploit to withdraw 2,285,545 satoshis, roughly 0.023 BTC. The attack started more than three hours before any public warning.
- 12:33. LNbits asks operators to disable Paywall, an extension that charges readers to unlock content, while it investigates a possible bug.
- About 13:56. A little over an hour later, the warning widens: every LNbits user should stop their server, because the project has several security patches to push.
- Later that day. The project switches off every instance on its hosted service, my.lnbits.com, and says service will return within 24 hours.
Ben Arc, an LNbits developer, estimated that the patches would be merged and available within 24 to 48 hours. The operator who lost funds has promised to repay his users, and he later said the developers had identified which extension was exploited on his server. As of the morning of November 9, nobody had named that extension publicly.
What Is Not Known Yet
Several gaps are worth keeping in mind before you draw conclusions. The project has not said how many servers were attacked or how much was taken in total. It has not confirmed whether Paywall is the extension behind the known loss, or whether the other patches fix separate bugs. It has not published a way for operators to check whether their own server was hit before they shut it down. The notice covers LNbits servers only. It does not mention Lightning nodes such as LND or Core Lightning, or other wallet software.
That last point matters. An LNbits server usually sits on top of a Lightning node and spends from its channels, so a bug in LNbits can drain the node's funds without the node software being broken at all.
LNbits Shutdown: Five Steps for Operators
- Stop the LNbits process now, and leave the Lightning node running. The notice asks you to stop LNbits. Your node keeps its channels open while the wallet layer is offline, and closing channels in a panic costs on-chain fees without fixing anything.
- Save your logs before anything rotates them. Copy the LNbits logs and database somewhere safe. If the project later publishes signs of compromise, you will want the record from November 8 and earlier, not a fresh log from after a restart.
- List every account and every extension you have enabled. Look for accounts you did not create and for outgoing payments you cannot explain, especially from new accounts. Write down which extensions are switched on, starting with Paywall.
- Compare your node's balance with what LNbits says it holds. Your node's own tools show what actually left your channels. If the numbers on the two sides do not match, treat the gap as a loss until you can explain it.
- Upgrade only from the project's own release page. When patches ship, take them from the official LNbits GitHub repository or its verified accounts, read the release notes, and check which extensions they mention before you restart. A wave of attacks is also when fake "patched" builds start circulating.
If you hold sats in an LNbits wallet that someone else runs, the useful step is simpler: ask the operator whether their server was stopped in time and whether they have checked it, and do not send new funds to that wallet until a fixed release is installed.
Why a Balance on a Server Was the Target
Strip away the extension names and the attack has a familiar shape. An LNbits instance holds a pool of sats on one node and keeps an internal ledger of who owns which part. Users trust that ledger. When a bug lets a stranger create an account and convince the ledger it may spend, the money leaves the node, because the node only sees a valid payment. The person who loses is whoever's balance was sitting there.
That is not a flaw unique to LNbits, and it is not a reason to stop self-hosting. Running your own wallet server is a real step toward self-custody, and the LNbits team moved fast to tell people to stop. The lesson is narrower: any balance that waits on a server, yours or someone else's, can be spent by that server's bugs. The smaller and shorter-lived that balance is, the less an attacker can take.
Mining pools face the same question. A typical pool credits your share of a block to an internal balance and pays it out later, so for a while your reward is a row in the pool's database. NexusPool takes the other path. Its fee is 0%, and when your rig finds a block, the coinbase transaction inside that block pays the whole reward to your own Bitcoin address. No pool-held balance sits between the found block and your wallet, so there is no internal ledger for a stranger to talk into a withdrawal.
You do not have to take that on trust. Payout Preflight shows the exact coinbase that would pay you on the current block, before any block is found, so you can confirm the address is yours. The Glass Ledger adds a BIP340-signed receipt for each rig, each hour, covering the shares the pool counted from it, checkable with any BIP340 library against the keys the pool publishes. The technology page explains how blocks are built, and the status page shows whether each region is up right now.
What This Post Does Not Claim
It does not say LNbits is unsafe to use once the fixes ship, or that the open-source project was careless. It does not say how many operators lost funds, because nobody has published that number. It does not claim the attack touched Lightning node software. And it does not claim that any pool, NexusPool included, changes your odds of finding a block: network difficulty sets the odds on each hash, and no pool can change them. What a pool can change is where the reward goes when you win.
The Steps, in One Line Each
Stop LNbits and keep the node up. Save the logs. Audit accounts and extensions. Reconcile the node's balance against LNbits. Upgrade only from the official release, then restart. And whatever you mine or hold, keep the time your coins spend in someone else's ledger as short as you can.
Trust nothing. Verify where your sats actually sit before you trust the number on the screen.