According to Cointelegraph, BTCPay Server has temporarily restricted public remote connections to Lightning Network nodes after attackers exploited a critical vulnerability in LND (Lightning Network Daemon) to steal node credentials and transfer funds. Version 2.4.2 has been upgraded to LND 0.21.1, which automatically rotates macaroon credentials in standard installations. The project advises operators to promptly check for unusual payments, channel closures, and balance changes; those exposing their nodes via self-hosted reverse proxies, Tor services, or port forwarding must manually rotate associated credentials. The Foundation and Citadel21 have reported compromised node funds, though the full extent of losses has not been disclosed.
BTCPay Temporarily Restricts Remote Access to the Lightning Network Due to LND Vulnerability
TechFlowShare
Summary
BTCPay Server has temporarily restricted public remote access to Lightning Network nodes following a report of a critical vulnerability in LND. Attackers exploited this flaw to steal node credentials and transfer funds. Version 2.4.2 has been upgraded to LND 0.21.1 and now automatically rotates macaroon credentials. Operators are urged to review payments, channel closures, and balance changes. Nodes exposed via reverse proxies, Tor, or port forwarding require manual credential updates. The Foundation and Citadel21 have confirmed losses, though the amounts have not been disclosed.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.