BTCPay Server warns hot wallet drains hit versions 2.4.1 and older, urges upgrade to 2.4.7

BTCPay Server warns hot wallet drains hit versions 2.4.1 and older, urges upgrade to 2.4.7

BACOOR NEWS2 min read

BTCPay Server says attackers are draining hot wallets on instances running version 2.4.1 or older. It urges operators to upgrade to 2.4.7, which has no credible drain reports.

In brief

  • BTCPay Server traced the hot wallet drains to an attack vector affecting version 2.4.1 or older, released on 23 July 2026.
  • The project says it has no credible reports of drains on the latest release, version 2.4.7, and urges all operators to update.
  • BTCPay has not disclosed how many operators were affected or how much Bitcoin was stolen.

What happened

BTCPay Server, a free open-source tool that businesses run on their own servers to accept Bitcoin BTC payments, said attackers are draining hot wallets on outdated instances.

The project identified an attack vector targeting version 2.4.1 or earlier, which was released on 23 July 2026, according to Cointelegraph.

A hot wallet keeps the wallet's seed on the internet-connected server so it can sign transactions automatically.

BTCPay's own documentation labels the feature "DANGER" and warns it carries security implications, Decrypt reported.

The project first told operators to shut down their servers on Sunday while it investigated, as reports of swept hot wallets spread across multiple instances.

It later said it had no credible reports of drains among users running the latest release, version 2.4.7, and urged everyone to update, narrowing the warning to older versions.

Version 2.4.7 was released on Thursday as an emergency update fixing one critical and several medium-severity vulnerabilities found by Anthropic's scanner.

BTCPay has not said whether the attacks exploited any of those flaws.

Some hosting providers, including LunaNode, shut down BTCPay instances automatically to stop older versions from being exploited.

BTCPay has not disclosed the number of affected operators, the value of stolen funds or the technical details of how attackers gained access.

Why it matters

Because BTCPay is self-hosted, no central operator can switch every instance off.

Each merchant must act on its own server, and the project asked affected users to send logs to its security team.

The reports come less than three months after an August attack that used compromised Lightning Network Daemon (LND) credentials to steal funds, prompting BTCPay to restrict remote Lightning access.

It remains unclear whether the two attacks are connected.

Bitcoin traded near $78,160 at 13:46 UTC, up +0.28% in 24 hours, according to Hyperliquid data.

What to watch

Operators on 2.4.1 or older should upgrade to 2.4.7 and rotate any credentials stored on the server.

Merchants running a hot wallet may also consider moving funds to a setup where the seed stays offline.

BTCPay has not published a full post-mortem.

Watch for its disclosure of how many servers were affected and whether the vector overlaps with the August flaw.

Sources

  1. Coin Bureau - Coin BureauSource
  2. Cointelegraph - Cointelegraph report on BTCPay attack vectorReport
  3. Decrypt - Decrypt report on BTCPay server shutdown warningReport

Related articles

More in Security

Nothing on BACOOR NEWS is financial advice.

BACOOR NEWS is developed by BACOOR's Japan team and provides news, editorial content, and market data for informational purposes only. Nothing published constitutes financial or investment advice, or an offer, solicitation, or recommendation to buy, sell, or hold any financial product or digital asset. Coverage of any token, trading pair, company, protocol, or project does not imply endorsement or promotion. Digital asset markets involve significant risks. Always conduct your own research (DYOR) and review our Disclaimer before making investment decisions.

AI Content Transparency: Market Pulse summaries are automatically generated using artificial intelligence (AI) based on third-party information and market data. News articles and other editorial content may also be drafted, edited, or otherwise prepared with AI assistance. BACOOR does not independently verify all third-party information before publication. AI-generated or AI-assisted content may contain errors, omissions, or outdated information. Readers are encouraged to verify important claims against the original sources. BACOOR may correct, update, or remove inaccurate content when identified.

Product Promotions: BACOOR NEWS may display clearly identified promotional content about BACOOR's own products and services where permitted by applicable law. Crypto-related promotional banners are not displayed on the Vietnamese-language edition or to visitors in Vietnam. Such promotional material is separate from editorial news and market data.

Data and Information Sources: alternative.me, Bankless, Arkham, Binance, Bitget, Bybit, Coinbase, Coin Bureau, DefiLlama, DEX Screener, ExchangeRate-API, Farside Investors, U.S. Bureau of Labor Statistics, U.S. Bureau of Economic Analysis, Federal Reserve, Bank of Japan, Cabinet Office of Japan, Gate, Hyperliquid, Lookonchain, MEXC, OKX, PatternPlus, Forex Factory, SEC EDGAR, Solid Intel, SoSoValue, Trust Wallet assets, Wikidata, CoinGecko, GeckoTerminal, e-Stat, FRED (Federal Reserve Bank of St. Louis), Japan Customs (Ministry of Finance), Wikimedia Commons, the official blogs and GitHub releases of the projects we cover, and Watcher Guru. External information may be delayed, inaccurate, or incomplete. Source attribution does not imply affiliation or endorsement.

This service uses the API function of e-Stat (Portal Site of Official Statistics of Japan), but its content is not guaranteed by the Japanese government.

Build version: 11403dc · 2026-11-20 06:04 GMT+7