BTCPay Server operators saw hot-wallet drains on old versions.
The open-source Bitcoin payment processor reported thefts from servers still running 2.4.1 (July 2026) or earlier; the fix had shipped in 2.4.2 months before. If you self-host one, check the version at the bottom of the UI and treat anything older as potentially exposed—hot keys on an internet-facing box are a different risk than a hardware wallet. Official advisory:
#selfcustody
Most flagged Lightning nodes were still on vulnerable LND lines two months later.
A study of public gossip data found that 71% of a group of LND nodes marked exposed in an August disclosure were still announcing the affected release lines as of mid-October, even though the patches had been available for over a year. Upgrades clustered more around platform releases (like Umbrel) than around security warnings themselves. Paper:
Lightning Labs opened Wavelength so AI agents can hold and spend Bitcoin over Lightning without running a node.
Agents can now use the toolkit (via MCP tools and L402) to pay for API calls or services in tiny amounts, with the wallet self-custodial and no human approving each transaction. It is early and still alpha, but it is open tooling for machine-to-machine Bitcoin payments. Announcement:
Practical notes on local AI and self-custody at cryptodecentral.co.za
Security Incident Affecting BTCPay Server 2.4.1 and Earlier | BTCPay Server Blog
Official BTCPay Server Blog

arXiv.org
Who Patches the Lightning Network? Evidence from Release Lines in Gossip, 2023-2026
Every implementation of Bitcoin's Lightning payment network disclosed security vulnerabilities in 2026, and every advisory told operators to upgrad...
Ride the Wave: Integrate Bitcoin Payments with Wavelength on Mainnet 🌊
Today we're announcing that Wavelength, our toolkit for integrating payments into any app, is now live on mainnet for everyone. That means humans a...








