LNbits released version 1.7.0 on November 10 as an urgent security update following attacks that began on November 8. The project instructed all operators to upgrade before restarting their servers.

On November 8, LNbits discovered active attacks and posted that users should stop their servers immediately. The project disabled instances on its hosted service. Multiple reports documented unauthorized account creation and fund withdrawals across affected instances.

Kevin Ravensberg, operator of the Telegram tipping service BitTipBot, stated that attackers created new accounts on his instance and withdrew 2,285,545 satoshis, approximately 0.0229 BTC, between roughly 09:22 and 14:00 UTC on November 8.

According to upgrade guidance published with the release, versions prior to 1.7.0 are affected and "funds running on prior versions of LNbits are at risk of being stolen." The project stated that 1.7.0 includes security fixes in response to the November 8 incident. A full technical report on the exploit will follow.

LNbits advised operators to set up a fresh server if compromise is suspected, because updating alone cannot remove access an attacker may already have gained. Recovery steps include rotating all user wallet keys as Super Admin, replacing funding-source credentials, rotating secrets stored in settings, and reviewing or re-creating connections for extensions such as NWC Provider, LNDHub, Bolt Cards, TPOS, Bleskomat, and FOSSA.

Version 1.7.0 includes security hardening across authentication, extension management, and payment handling, plus dependency updates. New features include on-chain wallet support, BOLT12 offer payments, TOTP two-factor authentication, NIP-17 support, a job scheduler, automatic extension updates, and hold invoice support for the LNbits funding source.

The project noted that LNbits functions as a hot wallet and that operators should keep only operational balances online, regularly review activity, and move excess funds to offline keys. As of the v1.7.0 announcement, the project has not published an aggregate total of funds lost across all affected instances.