
Akshita Jhalani
Crypto Analyst
TL;DR
BTCPay Server says it has identified an attack vector behind hot wallet thefts on version 2.4.1 and older. It has seen no credible reports of drained wallets on 2.4.7 and urges operators to update. The project has not reported how many operators were hit, how much was stolen, or how attackers got in.
Key takeaways
- BTCPay Server said on Monday, November 2, that it identified an attack vector targeting installations on version 2.4.1 or older.
- The project has seen no credible reports of drained hot wallets on the current release, 2.4.7, and told operators to update.
- Version 2.4.1 was released on July 23, 2026, and BTCPay had earlier told operators to shut down their instances while it investigated.
- BTCPay has not published a count of affected operators, a figure for stolen funds, or an explanation of how attackers got in.
- In August, an attack exploited a vulnerability to obtain LND credentials and steal funds, and it is unclear whether the new vector is connected.
Version 2.4.7. That's the number BTCPay Server wants every operator to check this week, and I think the story behind it deserves more attention than it's getting.
On Monday, November 2, the Bitcoin payment project said it had pinned down an attack vector behind a run of BTCPay Server hot wallet thefts. The vector targets installations running version 2.4.1 or anything older. The project said it has seen no credible reports of drained hot wallets from people on the current release, 2.4.7, and told operators to update, as Cointelegraph reported.
That sounds like a tidy fix. It isn't one yet, and I'll explain why.
BTCPay Has Said Less Than It Seems
The sequence matters. Before Monday's update, BTCPay had already told operators to shut their server instances down while its team looked into reports of unauthorized withdrawals, and it circulated instructions for doing so. Monday's statement came after that investigation produced a narrower answer: older builds are the exposed ones.
The version 2.4.1 cutoff carries a date. According to the report, that release went out on July 23, 2026. So the exposed population is anyone who installed the software in the summer and never moved forward. When operators run their own servers, that could be a lot of people, or a handful. Nobody outside BTCPay can say.
The project hasn't published a count of affected operators. It hasn't put a dollar figure on the stolen funds. It hasn't explained how the attackers got into the wallets in the first place. Affected users were asked to send information and logs to the security team, which suggests the picture is still being assembled.
Cointelegraph said it asked BTCPay for comment and had no reply by publication time.
A Hot Wallet Is the Soft Target
A hot wallet keeps keys on a machine that's online. That's the whole point: a merchant taking payments needs coins moving without someone typing a passphrase at 3 a.m. The cost is that the server itself becomes the vault, and if the software guarding it has a hole, the vault door is open.
BTCPay is self‑hosted. No help desk can freeze an account or reverse a transfer. When a bug lands, the operator is the only line of defense, and the only patch schedule that counts is the one they actually follow. I've covered enough incidents like this to know the uncomfortable pattern: the fix often ships well before the people who need it install it, and thieves work in that gap.
This Is the Second Scare in Under Three Months
This isn't BTCPay's first hot wallet problem this autumn. Less than three months ago, in August, an attack exploited a vulnerability to obtain credentials for the Lightning Network Daemon (LND) and steal funds. BTCPay's response then was to restrict remote Lightning access.
Whether the two incidents are related is unknown. The project hasn't linked them, and the same report notes it remains unclear if the new vector connects to the August flaw. I'd hold off on assuming a single root cause. Two thefts in one quarter could be one sloppy seam or two unrelated ones, and the remedies differ.
What I will say is that a cautious merchant is going to think harder about where the keys live. Some will move funds to cold storage and sweep only what a day's sales require. Others will decide that running their own payment stack is worth the maintenance. Both are reasonable. Neither is advice, just what the situation invites.
The Market Backdrop Makes It Louder
Crypto security news has been heavy lately. The same Cointelegraph page carries related coverage of a record hack at Binance, with net outflows of $5.8 billion as withdrawals resumed, and $1.6 billion in liquidations after that breach. Bitcoin was trading around $78,000 when the BTCPay story ran.
BTCPay's problem is a different animal. It's a software project with operators scattered across the world, not a single exchange with a balance sheet. Yet the effect on trust can be similar. A merchant who just watched a giant exchange get robbed isn't in a forgiving mood about a payment server that may have a leak.
I was struck by how little BTCPay has said about scale. A project that urges people to power down their servers is signaling real concern. Silence on the numbers reads as caution or as not knowing yet, and I can't tell which.
Operators Should Update Right Now
The project's own guidance is plain enough. Check the installed version. If it's 2.4.1 or earlier, update to 2.4.7 or newer. Anyone who saw unexplained withdrawals should gather logs and send them to BTCPay's security team, since that's how the investigation gets its evidence.
A few practical points follow from the facts as stated:
- A server shut down at the project's earlier request should come back only after the update, not before.
- Running 2.4.7 appears safe based on what BTCPay has heard, but that's an absence of reports, not a guarantee.
- Anyone who held large balances on a vulnerable instance should treat the host as suspect until the cause is public.
That last point is my own judgment, not the project's instruction. If you can't say how the attacker got in, you can't be sure what else they touched.
Three Answers Will Show How Serious This Is
First, whether BTCPay publishes a technical write‑up of the vector once users have had time to patch. Second, whether it ever states a figure for stolen funds or the number of operators hit. Third, whether the project ties this episode to the August LND credential theft.
If the third answer is yes, the conversation shifts from patching to design: how a payment tool built on self‑custody should handle keys that sit online. If it's no, BTCPay has two separate flaws to explain in a single quarter. My guess is the write‑up comes first and the numbers last, if they come at all. Either way, operators on old builds have a clear task and a short window to finish it.
