Fact-check findings
What an automated fact-checker found when it re-read BTCPay Server — LND Macaroon Credential Exploit (August 2026) against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
link rot
2 claimsA cited source no longer resolves or no longer says what the page attributes to it.
- #8[link rot][awaiting moderator]in the cited sources
“https://web.archive.org/web/20260809230610/https://blockonomi.com/amd-amd-stock-taalas-acquisition-targets-faster-ai-inference-growth/”
reviewerArchive URL for Blockonomi 'critical vulnerability' article points to an unrelated articleArchive snapshot is of an unrelated article (AMD/Taalas). The live URL is fine. - #9[link rot][awaiting moderator]in the cited sources
“https://web.archive.org/web/20260809230610/https://blockonomi.com/gsr-warns-dao-treasury-concentration-creates-a-negative-feedback-loop/”
reviewerArchive URL for Blockonomi 'suspends remote access' article points to an unrelated articleArchive snapshot is of a GSR/DAO treasury article, not the BTCPay piece. Live URL not separately fetched.
partially supported
4 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Patch and Remediation
“Following the exploit, BTCPay Server supporters pledged a recovery bounty of 10% of any stolen funds returned, capped at 3 BTC (approximately $190,000 at the time of reporting), open to anyone providing actionable information leading to the return of funds, explicitly including the attacker.”
reviewerBounty: 10% of recovered funds, capped at 3 BTC (about $190,000), open to the attackerTerms confirmed; USD figure is in the CoinDesk headline (not fetched in full) and attacker eligibility was not confirmed in The Block text. - #4[partially supported][awaiting moderator]in section: Affected Versions and Scope
“On-chain hot wallets held within BTCPay Server were separately described as at risk if an attacker also obtained Greenfield API access, and operators were advised to move funds from BTCPay-generated hot wallets and recreate them.”
reviewerOn-chain hot wallets described as at risk; operators advised to move fundsEarly press reported hot-wallet migration advice, but the advisory as now published says on-chain wallets are unaffected. The page's framing and the Remediation step 3 may be outdated. - #5[partially supported][awaiting moderator]in section: Patch and Remediation
“revoke and regenerate all LND macaroons at the node level by deleting the macaroons.db root signing key file and restarting LND, not merely deleting the credential files”
reviewerRemediation includes deleting macaroons.db root key and moving hot-wallet funds; patch sets Basic auth to disable after five minutes; LND 0.21.1Patch contents, LND 0.21.1 and Basic-auth change check out. The specific macaroons.db procedure was not found in the official advisory; only secondary sources mention a macaroon database. - #6[partially supported][awaiting moderator]in section: LND Macaroon Architecture and Structural Risk
“The Bitcoin Red Team, comprising Craig Raw (Sparrow Wallet developer), Rob Hamilton, Calle and Evan Kaloudis, is credited with disclosing the vulnerability to BTCPay Server and providing details that enabled the patch”
reviewerBitcoin Red Team members credited with disclosureCraig Raw and the Red Team are credited, but the full member list was not verified.
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“On August 7, 2026, the project disclosed and patched (version 2.4.2) a critical, actively exploited vulnerability, present in all earlier versions, that let remote attackers obtain LND macaroon credential files and drain merchants' connected Lightning nodes.”
reviewerOn August 7, 2026 BTCPay disclosed and patched an actively exploited flaw in all earlier versions letting remote attackers obtain LND macaroon filesMatches the official advisory and release notes. - #2[confirmed][no action needed]in section: Active Exploitation and Confirmed Victims
“Foundation, the company behind the Passport hardware wallet, had its BTCPay-connected Lightning node emptied overnight; CEO Zach Herbert confirmed that attackers closed the company's payment channels and swept the funds, and Foundation said its primary on-chain hot wallet was not affected.”
reviewerFoundation (CEO Zach Herbert) and Citadel21 confirmed as victims; Foundation's on-chain hot wallet unaffected; losses undisclosedSupported. The Passport product detail was not checked in the fetched text but is not contested. - #7[confirmed][no action needed]in section: Vulnerability: LND Macaroon Credential Exposure
“BTCPay intentionally withheld technical details of the exact exposure path while operators remained on vulnerable versions, and promised a full postmortem that had not been released as of mid-August 2026.”
reviewerPostmortem not released as of mid-August; no CVE assignedAccurate as of mid-August; the page is over two months old and does not say whether a postmortem has since appeared.