BTCPay Server Urges Operators to Shut Down After Hot-Wallet Sweep Reports
The open-source bitcoin payment project BTCPay Server told operators to shut down their servers after reports of drained hot wallets. The project has not published a loss figure or a patch, and its founder said the affected versions appear to be those older than 2.4.2.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
What BTCPay Told Operators
BTCPay Server, the open-source bitcoin payment software, advised operators to shut down their instances while it investigates reports that hot wallets were being swept. According to The Defiant, the instruction was to run ./btcpay-down.sh, and the alert did not identify affected versions or announce a patch. CoinDesk reported the same request, describing it as a move to switch off servers after reports of drained wallets.
Affected Versions Remain Unclear
The sources differ in how much they say about scope. The Defiant's account stresses that the alert itself named no affected versions. CoinDesk reports that the project's founder said the reports appear to involve releases older than 2.4.2. Taken together, the founder's statement is the only version-level guidance publicly attributed to the project so far, and it is not stated in the alert itself. Neither outlet confirmed the figure independently, and operators should treat the 2.4.2 boundary as a founder's preliminary read rather than a confirmed finding.
Losses and Next Steps
Neither report includes a loss figure, and the project has not said how many wallets or how much bitcoin may be involved. The project says it is still investigating and has not announced a fix. Until a patch or a formal post-mortem is published, the scope of the incident, including whether any version after 2.4.2 is affected, remains unresolved.
Why It Matters
For Traders
Merchants and services accepting bitcoin via BTCPay may face payment disruption, but the absence of a loss figure makes the broader market effect hard to size.
For Investors
A security incident in widely used open-source payment infrastructure can weigh on confidence in self-hosted bitcoin payment rails, even when the damage is contained.
For Builders
Operators and integrators should check their installed version against the founder's 2.4.2 reference point and audit hot-wallet keys until an official advisory is published.
This article is for information only and is not financial advice. Read the full disclaimer.
