BTCPay Server Tells Users to Shut Down Instances After Hot Wallet Drains
BTCPay Server warned operators to shut down vulnerable instances and urged updates after detecting admin‑login attacks.
Founder Nicolas Dorier identified the attacker’s Bitcoin address, confirming 18.75 BTC moved and public servers remained safe.
Hosting providers like LunaNode automatically disabled outdated servers, compensating for BTCPay’s decentralized architecture.
BTCPay Server told its users to shut down their own servers. For a payment tool built specifically so no central party can do that for them, it was the only option available.
Because each merchant runs an independent instance, BTCPay had no way to pull affected servers offline itself—it could only ask operators to act. That structural limitation shaped the entire response.
BTCPay Server posted on X on Nov. 1, 2026, a warning: “We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers. If you’re running an instance, please shut it down (./btcpay-down.sh) until we complete the investigation.”
About two hours after the initial warning, BTCPay said its incident response investigation had identified an attack vector targeting instances running version 2.4.1 (July 23, 2026) or older. The project said it has “no credible reports of hot wallet drains for users running the latest 2.4.7 release,” while again urging all operators to update.
BTCPay has not disclosed a total loss figure or how many servers were affected. BTCPay asked anyone affected to send details and logs to security@btcpayserver.org.
Dorier Confirms Public Servers Were Safe, Traces Attacker’s Wallet
BTCPay founder Nicolas Dorier posted a further update on X confirming that BTCPay’s own public-facing servers, running version 2.4.7, “were not attacked,” and narrowed the affected range specifically to instances on “before 2.4.2.” He reiterated that the attacker “managed to log in as admin on those instances” and that the team is “still trying to figure out how.”
Dorier also published what he identified as the attacker’s Bitcoin address, showing on-chain data from mempool.space: roughly 18.75 BTC total received, about 18.28 BTC total sent out, a remaining balance of approximately 0.47 BTC, and 522 total transactions on the address—figures that, if the address is correctly attributed, suggest the attacker has already moved the bulk of the stolen funds elsewhere.
Dorier said BTCPay plans to publish a full blog post with further details but offered two pieces of immediate advice independent of that forthcoming write-up: anyone who has updated at least once since the 2.4.2 release has “no reason to panic,” and—regardless of version—users should “update often” and avoid keeping excessive funds in a hot wallet.
What a ‘Hot Wallet’ Means for BTCPay Users
BTCPay Server is open-source software merchants run on their own infrastructure to accept bitcoin payments without a third-party custodian. Its documentation offers a “hot wallet” option that stores the wallet’s seed phrase directly on the internet-connected server, letting BTCPay sign outgoing payments automatically—a feature BTCPay’s own documentation flags with a “DANGER” label, precisely because a compromised server exposes the seed itself, not just a session or API key.
Hosting Providers Stepped In Where BTCPay Couldn’t
BTCPay said that for users running the software through a hosting provider, instances may have been shut down automatically to keep older, vulnerable versions from being exploited further.
BTCPay specifically thanked LunaNode and other hosting providers “for their swift action after our initial announcement”—a response that filled the gap created by BTCPay’s own decentralized, self-hosted architecture.
This Isn’t BTCPay’s First Pre-2.4.2 Security Incident
In August 2026, BTCPay confirmed a separate flaw in versions before 2.4.2 that let attackers obtain credential files for LND, the Lightning Network node software, giving them control of affected nodes and letting them move funds out. That issue was patched in version 2.4.2. Both incidents involve the same pre-2.4.2 version range, though BTCPay has not said whether they share an underlying cause, and this week’s hot-wallet attack vector has not been publicly tied to the August Lightning-node flaw.
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


