Key Insights
- Bitcoin news: BTCPay Server identified an attack vector affecting versions 2.4.1 and older.
- Attackers reportedly drained Bitcoin hot wallets, while the total losses remained undisclosed.
- BTCPay reported no credible wallet thefts involving its latest software version, 2.4.7.
BTCPay Server identified a security flaw targeting older software versions following reports of Bitcoin wallet thefts. The development added another security incident to Bitcoin news on Monday, Nov. 2.
The Bitcoin payment processor said attackers targeted instances running version 2.4.1 or earlier. However, its investigation found no credible wallet theft reports involving the latest version, 2.4.7.
The project urged operators to update their installations and report suspected compromises. BTCPay did not disclose the number of victims or the total stolen funds. Meanwhile, the update also gained traction after the recent Binance hack shook the broader crypto market.
Bitcoin News: BTCPay Server Identifies Attack Vector in Older Versions
BTCPay Server confirmed the findings in an official X statement on Nov. 2. Its investigation identified an attack vector affecting software released on or before July 23, 2026.
The affected versions included 2.4.1 and earlier releases. The project had not publicly explained the technical mechanism behind the latest attack.
The Bitcoin news followed an earlier warning concerning unauthorized withdrawals from operators’ Bitcoin hot wallets. BTCPay initially urged affected operators to shut down their server instances while investigators examined the incidents. The platform also provided shutdown instructions to help operators respond to potential compromises.
However, investigators had not disclosed how attackers accessed affected wallets. BTCPay also withheld information about the number of compromised installations and stolen Bitcoin. The project asked affected users to submit relevant information and server logs to [email protected].
These outstanding details limited the investigation’s public findings. They also prevented an independent assessment of the attack’s financial impact.
Bitcoin News: Latest BTCPay Update Follows Security Fixes
BTCPay Server’s GitHub repository confirmed that developers released version 2.4.7 on Oct. 29. The release addressed security, reliability, and payment-accounting issues. Developers recommended updating, particularly for servers supporting multiple merchants.
GitHub release notes documented 85 security findings addressed through the update. These comprised one critical, 13 high-severity, 52 medium-severity, and 19 low-severity findings.
The fixes covered authentication controls, application permissions, wallet operations, and payment-processing functions. However, the project’s Bitcoin news advisory did not identify which specific weakness enabled the reported hot wallet withdrawals. Consequently, the available statements did not establish whether one of the documented fixes directly addressed the latest attack.
BTCPay nevertheless reported no credible hot wallet drains involving installations running version 2.4.7. That assessment reflected reported incidents rather than a guarantee against future exploitation. The distinction remained relevant because the platform continued collecting evidence from affected users.
Bitcoin Hot Wallet Security Faces Renewed Scrutiny
BTCPay Server operates as an open-source, noncustodial cryptocurrency payment processor. Merchants can receive Bitcoin payments directly without transferring custody to a payment intermediary. However, its wallet documentation distinguishes hot wallets from externally managed wallets.
Hot wallets retain signing credentials on the server, allowing operators to authorize payments through the interface. This arrangement creates exposure when attackers compromise an account or server.
The platform’s Bitcoin news incident highlighted that distinction without establishing the attackers’ precise access method. BTCPay’s documentation also supports hardware wallets and configurations that keep private keys outside the server.
Operators using external wallets can receive payments through extended public keys. Those configurations do not ordinarily require exposing private signing keys to the payment server. Nevertheless, BTCPay warns that compromised hosting environments can create other payment-related risks.
These differences matter when assessing the potential reach of a crypto hack. A compromised payment installation does not automatically mean attackers can spend funds held externally.
Earlier Lightning Exploit Targeted Credentials
The November incident followed a separate BTCPay security breach involving Lightning Network Daemon (LND) in August. On Aug. 7, BTCPay confirmed that attackers exploited a critical vulnerability to obtain LND credential files.
The files contained macaroon credentials used to control Lightning nodes and authorize operations. BTCPay said attackers could use the exposed credentials to control affected nodes and move funds.
The project confirmed that attackers exploited the weakness and stole funds from users. Version 2.4.2 addressed the vulnerability and upgraded LND to version 0.21.1.
The update also automatically regenerated macaroon credentials on standard BTCPay installations. BTCPay advised operators to examine unauthorized payments, unexpected channel closures, unfamiliar peers, and discrepancies in their balances.
It also temporarily restricted public LND access on Docker deployments through BTCPay domains and Tor onion addresses. Operators using separately managed reverse proxies or forwarded ports had to rotate credentials themselves. BTCPay clarified that the August vulnerability did not affect regular on-chain wallets, including hot wallets.
The latest bitcoin news incident concerned unauthorized withdrawals from Bitcoin hot wallets rather than exposed Lightning credentials. BTCPay has not established whether the November attack shared any technical connection with the August vulnerability.
The investigation also has not identified the number of affected operators or quantified their losses. For now, BTCPay has identified the affected software range and urged operators to install version 2.4.7.
