
Key takeaways
- LNbits releases version 1.7.0 as a critical security update and says older versions put funds at risk
- LNbits says updating alone cannot remove attacker access, so operators rotate wallet keys and funding credentials
- BitTipBot operator Kevin Ravensberg reports that attackers created new accounts and then withdrew 2,285,545 sats
An Urgent Release for Every LNbits Server
LNbits released version 1.7.0 as a critical security update after a vulnerability discovered on November 8, and told all LNbits users to update immediately. LNbits says versions prior to 1.7.0 are affected and that funds running on older LNbits versions are at risk of being stolen. The GitHub release describes 1.7.0 as "a critical security release containing extensive security hardening, important vulnerability fixes."
BitTipBot operator Kevin Ravensberg reported that attackers created new accounts and withdrew 2,285,545 sats. LNbits has not published an aggregate loss total or the exploit details, and says a full technical report on the exploit will follow.
LNbits first told operators to disable its Paywall extension, then about an hour later urged them to shut down their servers. The project also took its own hosted LNbits instances offline.
Why Updating Alone Is Not Enough
LNbits says updating alone cannot remove access an attacker may already have gained. Credentials exposed before the upgrade may still give an attacker access afterwards, so operators should treat any secrets stored in LNbits settings as compromised.
LNbits tells operators to rotate all user wallet keys with the Super Admin "Reset Wallet Keys" function. Operators should also replace funding-source credentials such as application programming interface (API) keys and macaroons, and move to a fresh server if they suspect a compromise.
Operators should also review LNbits extension connections such as Bolt Cards and Bleskomat as part of recovery. LNbits has not confirmed which component the attackers used, so every connected credential deserves the same suspicion.
New Features Ship With the Fix
Version 1.7.0 also adds on-chain wallet support, Lightning BOLT12 offers, two-factor authentication and a job scheduler. It adds superuser functionality to reset all wallet keys, the same tool LNbits now tells operators to use for recovery.
Why It Matters
LNbits shows the real price of sovereignty: running your own Lightning server means you hold the keys, and you also own the cleanup when credentials exposed before the upgrade still give an attacker access afterwards. Operators who rotate wallet keys, replace funding-source credentials and move to a fresh server keep custody of their sats, while those who only update leave the door open. We still prefer that trade to a custodian, because a self-hosted Bitcoin stack lets you verify and fix your own exposure instead of waiting on a gatekeeper. Open-source code put the warning, the fix and the wallet key reset tool in public, which is the security culture closed platforms rarely match.





















