Skip to main content
AVOID.NET
← LNbits1 decision on this page

Audit log

Every state-changing event for LNbits: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-11-16 12:11:59Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 470,127,000
    sig
    27fQ8NnNb7C1…q36VedSjexplorer ↗
    hash
    7Uaw5b5wz4Kd…cLR44dE2sha256 → base58
    verifying row…full verify ↗
    canonical bytes (8074 B) ▸
    {"actor":"system:backfill","investigation_id":"4bdb844f-8fbc-46bf-993b-e5b9376c665f","kind":"publish","page_slug":"lnbits","published_at":"2026-11-16T12:11:59.529Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"LNbits","sections":[{"content":"On November 8, 2026, the LNbits project posted a warning telling operators to disable the Paywall extension while it investigated a possible vulnerability. Roughly 80 minutes later, the project escalated to telling all operators to shut down their LNbits servers immediately, citing a wave of attacks resulting in stolen funds. LNbits also took its own hosted instances (my.lnbits.com) offline. As of approximately 09:00 UTC on November 9, 2026, no fixed software version had yet been released, the shutdown order remained in effect, and operators had no official guidance for determining whether their servers had already been compromised.","heading":"Emergency shutdown order and attack reports","severity":"critical","sources":[{"credibility":2,"name":"LNbits Urges All Operators to Shut Down (The Hacker News)","type":"news_article","url":"https://thehackernews.com/2026/11/lnbits-urges-all-operators-to-shut-down.html"},{"credibility":2,"name":"LNbits Rushes Emergency Patch After Reported Bitcoin Wallet Thefts (Cointelegraph)","type":"news_article","url":"https://cointelegraph.com/news/lnbits-rushes-emergency-patch-after-reported-bitcoin-wallet-thefts"}]},{"content":"An LNbits operator, Kevin Ravensberg, reported that attackers created unauthorized accounts on his server and withdrew approximately 2,285,545 satoshis (roughly 0.023 BTC), with the attack window running from about 09:22 to 14:00 UTC on November 8, 2026 — more than three hours before LNbits issued its first warning. Ravensberg's server ran BitTipBot, a Telegram tipping bot, and he said he would reimburse affected users, who could not access funds until the underlying flaw was fixed. No other specific loss amounts, nor a total figure across all affected installations, have been publicly reported. This claim currently rests on a single operator's account relayed through news coverage and has not been independently verified against on-chain data in available reporting.","heading":"Reported fund losses","severity":"high","sources":[{"credibility":2,"name":"LNbits Rushes Emergency Patch After Reported Bitcoin Wallet Thefts (Cointelegraph)","type":"news_article","url":"https://cointelegraph.com/news/lnbits-rushes-emergency-patch-after-reported-bitcoin-wallet-thefts"},{"credibility":2,"name":"LNbits Urges All Operators to Shut Down (The Hacker News)","type":"news_article","url":"https://thehackernews.com/2026/11/lnbits-urges-all-operators-to-shut-down.html"}]},{"content":"LNbits has not publicly confirmed the precise vulnerability exploited in the attacks. Some reporting indicates the project's developer, Ben Arc, and security testers privately confirmed the specific extension exploit used against at least one compromised server, but as of the available reporting the project had not named it, and had not definitively confirmed whether the Paywall extension — which operators were initially told to disable — was the vector. LNbits released version 1.7.0, described as a critical release addressing authentication, extension management, and payment-handling vulnerabilities; the project stated the underlying vulnerability affects all versions prior to 1.7.0. LNbits said a separate report detailing the exploit mechanics would follow, but no such detailed disclosure is reflected in available sources at this time.","heading":"Vulnerability disclosure and patch","severity":"high","sources":[{"credibility":2,"name":"LNbits Rushes Emergency Patch After Reported Bitcoin Wallet Thefts (Cointelegraph)","type":"news_article","url":"https://cointelegraph.com/news/lnbits-rushes-emergency-patch-after-reported-bitcoin-wallet-thefts"},{"credibility":2,"name":"LNbits security flaw: version 1.7.0 stops thefts from Lightning wallets (CryptoTicker)","type":"news_article","url":"https://cryptoticker.io/en/lnbits-security-flaw-emergency-update/"}]},{"content":"LNbits advised operators that simply updating to v1.7.0 does not protect installations whose credentials may already have been exposed. Operators were told to reset wallet keys, replace funding-source credentials, revoke potentially compromised access permissions, treat secrets stored in LNbits settings as compromised, and consider migrating to a fresh server if compromise was suspected. LNbits can be configured to connect either to an operator's own Lightning funding source or to a provider-managed one, meaning exposure and remediation responsibility vary by deployment. According to the project's creator, Ben Arc, roughly 200,000 people self-host the software, as he stated in prior reporting from May 2026; the number of installations actually affected by this incident has not been publicly disclosed.","heading":"Remediation guidance and scope of exposure","severity":"medium","sources":[{"credibility":2,"name":"LNbits Rushes Emergency Patch After Reported Bitcoin Wallet Thefts (Cointelegraph)","type":"news_article","url":"https://cointelegraph.com/news/lnbits-rushes-emergency-patch-after-reported-bitcoin-wallet-thefts"}]}],"sources_used":[{"credibility":2,"name":"LNbits Urges All Operators to Shut Down (The Hacker News)","type":"news_article","url":"https://thehackernews.com/2026/11/lnbits-urges-all-operators-to-shut-down.html"},{"credibility":2,"name":"LNbits Rushes Emergency Patch After Reported Bitcoin Wallet Thefts (Cointelegraph)","type":"news_article","url":"https://cointelegraph.com/news/lnbits-rushes-emergency-patch-after-reported-bitcoin-wallet-thefts"},{"credibility":2,"name":"LNbits security flaw: version 1.7.0 stops thefts from Lightning wallets (CryptoTicker)","type":"news_article","url":"https://cryptoticker.io/en/lnbits-security-flaw-emergency-update/"}],"summary":"LNbits, a widely self-hosted open-source Bitcoin Lightning wallet system, told all server operators to shut down immediately on November 8-9, 2026 after a wave of attacks drained funds from at least one installation through unauthorized account creation and withdrawals. The project released an emergency patch (v1.7.0) within days but had not, as of the most recent reporting, publicly identified the precise vulnerability or disclosed the full scope of affected instances.","timeline":[{"date":"2026-11","date_evidence":"The first warning was posted at 12:33 UTC (Nov 8).","date_original":"2026-11-08","event":"LNbits posts an initial warning telling operators to disable the Paywall extension while investigating a possible vulnerability.","source":"The Hacker News","source_url":"https://thehackernews.com/2026/11/lnbits-urges-all-operators-to-shut-down.html"},{"date":"2026-11","date_original":"2026-11-08","event":"Roughly 80 minutes after the initial warning, LNbits tells all server operators to shut down their servers immediately amid a wave of attacks; LNbits also takes its own hosted instances offline.","source":"The Hacker News / Cointelegraph","source_url":"https://thehackernews.com/2026/11/lnbits-urges-all-operators-to-shut-down.html"},{"date":"2026-11","date_evidence":"As of 09:00 UTC on Nov 9, no fixed version had been released.","date_original":"2026-11-09","event":"As of 09:00 UTC, no fixed software version has been released; the shutdown order remains in effect with no guidance for checking prior compromise.","source":"The Hacker News","source_url":"https://thehackernews.com/2026/11/lnbits-urges-all-operators-to-shut-down.html"},{"date":"2026-11-11","date_evidence":"published Nov 11, 2026","event":"Cointelegraph reports LNbits has released emergency patch v1.7.0, a critical release addressing authentication, extension management, and payment-handling vulnerabilities, and details operator Kevin Ravensberg's reported loss of roughly 2.3 million satoshis.","source":"Cointelegraph","source_url":"https://cointelegraph.com/news/lnbits-rushes-emergency-patch-after-reported-bitcoin-wallet-thefts"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 9c4d3a4b-cc04-4193-a849-46da17300dab
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.