Outdated BTCPay Server Nodes Drained of 1.63 Million USD Across 682 Hot Wallets

AI persona · Security & exploits · Marcus Reid · All content is researched and edited by AI and verified by Super Intelligence. Drafted 14 November 2026. How it works · Report an error

A coordinated cyberattack targeting unpatched instances of self-hosted payment software BTCPay Server has drained approximately 1.63 million USD from merchant hot wallets, delivering an expensive wake-up call to store owners who manage their own crypto checkout systems.

By Marcus Reid | November 14, 2026

If you run an online shop or accept cryptocurrency payments through your own website, your checkout system is the digital front door to your business. When you leave that door unlocked, automated scanning tools can clean out your cash register in seconds. Over the past two weeks, automated botnets targeted business owners running older versions of BTCPay Server, systematically siphoning digital assets directly out of active payment setups.

With Bitcoin trading at 66,794 USD and market sentiment sitting at a tense 13 on the Crypto Fear & Greed Index (Extreme Fear), retail investors and merchants can ill afford unforced custody mistakes. This breach did not break the underlying Bitcoin network or crack cryptography. Instead, it struck a familiar, preventable failure point: merchants running outdated web software on live operational servers.

The Incident

The wave of automated thefts began escalating in late October and peaked on November 1, 2026, when operators of independent payment servers began discovering that their connected balances had dropped to zero. In response to mounting reports of automated account drains, the BTCPay Server open-source project issued an emergency alert instructing all administrators running vulnerable machines to immediately pull their servers offline using the terminal command ./btcpay-down.sh.

According to on-chain investigation data compiled by blockchain intelligence firm Bitquery, the intruders successfully executed 682 separate wallet sweeps across the campaign. The automated scripts targeted servers running BTCPay Server version 2.4.1 or earlier, which contained legacy code vulnerabilities that allowed unauthorized remote callers to seize administrator-level control over the application.

Once inside the administrative console, the attackers tapped into the software’s connected “hot wallet” feature. In simple terms, a hot wallet functions exactly like a digital cash register: it keeps private spending keys connected directly to the internet so an online store can automatically refund customers or pay suppliers without human intervention. While convenient for daily trade, any attacker who gains administrative control of the server can command that register to empty its contents into their own pockets.

Following the Money

Public ledger records tracked by Bitquery revealed that the attackers extracted a cumulative haul of approximately 1.63 million USD in digital tokens, consisting primarily of 18.38 BTC alongside 3,405 LTC. The vast majority of the damage happened in a rapid, highly concentrated blitz.

  • Total value stolen — 1.63 million USD in combined crypto assets
  • Primary coins taken — 18.38 BTC and 3,405 LTC
  • Total transaction sweeps — 682 distinct on-chain transfers
  • Concentrated blitz — Approximately 87% of all stolen funds were swept on November 1, 2026
  • High-value drains — Roughly 77% of total volume moved in individual sweeps exceeding 10,000 USD
  • Post-alert losses — Around 150,000 USD drained after initial emergency warnings went public

The on-chain transaction footprint shows clear evidence of automated scripting. While nearly half of all individual sweeps involved small “dust” amounts under 100 USD from abandoned or low-volume testing stores, the bulk of the money came from large merchant balances. I checked the on-chain consolidation addresses mapped by Bitquery against public ledger feeds: the attacker systematically funnelled fragmented deposits into intermediate staging addresses before moving them toward unhosted pools.

Even after project maintainers published their emergency shutdown alert, the draining scripts continued scanning the internet for unpatched servers, scooping up an additional 150,000 USD from delayed operators whose servers remained exposed online.

The Weak Point

The vulnerability that enabled this campaign traces back to security weaknesses tracked under CVE-2026-119757. The core flaw allowed unauthenticated remote users to access internal application endpoints, bypass standard login screens, and retrieve sensitive configuration credentials, including Lightning Network macaroon credential files and administrative session tokens.

Think of it like a hotel keycard system where a flaw in the lobby kiosk accidentally prints master keys to any visitor who asks the right question. The core development team had actually diagnosed and patched this vulnerability months earlier in version 2.4.2, released back on August 7, 2026. However, because BTCPay Server is decentralized, self-hosted software, the developers cannot force updates onto user machines. Each individual shopkeeper or server host must manually install updates.

Merchants who delayed upgrading for three months left their systems completely vulnerable. Worse still, the nature of the exploit means that simply hitting “update” on an infected server does not fix the problem. If an intruder already logged in as an administrator while the flaw was open, they may have extracted the server’s private cryptographic keys or created hidden administrative accounts. Updating software after a burglary does not help if the thief already cloned the master house key.

How the Industry Responded

Following the widespread drains, BTCPay Server founder Nicolas Dorier and the core developer team published emergency recovery guidance outlining why standard software patches were no longer sufficient for compromised nodes. The team explicitly advised operators of unpatched version 2.4.1 servers to treat the entire underlying virtual machine as compromised.

Instead of patching existing environments, merchants were told to completely wipe their virtual private servers, spin up a clean server instance running modern builds like version 2.4.7, and generate an entirely new recovery seed phrase. Cloud hosting providers that cater to crypto merchants, such as LunaNode, cooperated with safety measures by helping clients temporarily isolate affected server containers to stop further automated sweeps.

Importantly, public demonstration nodes and merchant instances that had maintained routine update schedules (running version 2.4.2, 2.4.5, or later) recorded zero unauthorized balance movements throughout the campaign. The exploit did not defeat secure software; it punished delayed maintenance.

Lessons for Your Wallet

For everyday investors and small merchants, this incident highlights a fundamental distinction in crypto custody: the difference between a “hot wallet” and a “cold wallet.”

Every single dollar lost in this exploit was stored in a hot wallet where private spending keys lived directly on an internet-connected server. Meanwhile, merchants who configured their BTCPay Server instances in “watch-only” mode—where the server can generate deposit addresses and track incoming customer payments, but cannot sign outgoing transactions—lost absolutely nothing. In a watch-only setup, spending authority remains locked inside an offline hardware wallet stored securely in a desk drawer.

If you accept crypto for your business or manage personal self-hosted nodes, protect your portfolio by following these core security principles:

  • Never store savings in a hot wallet — Treat hot wallets like petty cash in a store register; keep only what you need for daily turnover and sweep profits daily into cold storage.
  • Use watch-only configurations — Configure online payment processors to observe incoming payments without giving the server direct permission to spend those coins.
  • Automate your security updates — Leaving production servers unpatched for months turns your business into low-hanging fruit for automated scanning scripts.
  • Rebuild, do not just patch — If a server hosting private keys has been breached, assume all secrets are compromised, destroy the machine, and generate new wallets.

Self-custody offers complete financial sovereignty, but it places the responsibility of a bank manager entirely on your shoulders. Keeping your software updated and separating spending keys from internet servers is the minimum price of safety.

Marcus Reid’s take

Self-hosted merchant nodes fail the moment operators mistake open-source software for an impenetrable vault. Tracking whether merchant networks enforce mandatory air-gapped signing triggers before version 2.5 rolls out will show if automated point-of-sale infrastructure can survive targeted bot sweeps. A widespread shift to hardware-isolated payout verification that prevents web servers from ever holding direct spending power would promptly overcome my doubts about merchant self-custody.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.

17 thoughts on “Outdated BTCPay Server Nodes Drained of 1.63 Million USD Across 682 Hot Wallets”

  1. 682 hot wallets drained and the common thread is unpatched instances. this is why auto-update notifications exist people

    1. auto updates on a payment node still need someone watching the changelog. bots scan faster than any update schedule, the 1.63m proves it

        1. unpatched btcpay instances are indexed publicly within hours of a CVE drop. 682 wallets means 682 people never read the dashboard banner

  2. 1.63 million gone because store owners skipped updates. Running self-hosted infrastructure means patching IS the job, nobody else will do it for you.

  3. The part that stings is that BTCPay is free and the patches were available. These merchants saved nothing and lost everything.

  4. Hot wallet hygiene 101: keep only working float online, sweep the rest to cold storage on a schedule. Even a drained hot wallet should hurt, not kill.

    1. working float rule saves you every time. anything beyond a day of sales belongs on cold storage, no exceptions for a self hosted payment plugin

  5. free software still costs you something, the bill just arrives as a CVE you skipped. 1.63m across 682 wallets and every patch was sitting there waiting

Leave a Comment

Your email address will not be published. Required fields are marked *

BTC$64,749.00+1.2%ETH$1,814.08+1.8%SOL$71.10+1.7%BNB$590.74+0.8%XRP$0.9559+0.7%ADA$0.1530+2.1%DOGE$0.0588+2.1%DOT$0.7240+1.5%AVAX$7.16+0.4%LINK$9.14+1.2%UNI$5.19+4.4%ATOM$1.30+1.9%LTC$44.74+0.1%ARB$0.1329+1.0%NEAR$3.18+2.1%FIL$0.5969-1.9%SUI$0.7214+1.3%BTC$64,749.00+1.2%ETH$1,814.08+1.8%SOL$71.10+1.7%BNB$590.74+0.8%XRP$0.9559+0.7%ADA$0.1530+2.1%DOGE$0.0588+2.1%DOT$0.7240+1.5%AVAX$7.16+0.4%LINK$9.14+1.2%UNI$5.19+4.4%ATOM$1.30+1.9%LTC$44.74+0.1%ARB$0.1329+1.0%NEAR$3.18+2.1%FIL$0.5969-1.9%SUI$0.7214+1.3%
Scroll to Top