BTCPay Server urged operators to shut down their servers after receiving reports of unauthorized attackers draining funds from hot wallets.
Hardware wallet maker Foundation and the Bitcoin zine Citadel21 both said their nodes were swept, in some cases hours before the project’s public alert. BTCPay says the flaw under attack is not the one disclosed in its changelog.
Attackers emptied Lightning nodes belonging to BTCPay Server users on Friday, including one run by hardware wallet maker Foundation, after the self-hosted bitcoin payment processor warned that a critical vulnerability was being actively exploited and told merchants to update to version 2.4.2 or shut their servers down.
Because BTCPay is self-hosted, there is no operator who can patch on behalf of its users. Every merchant, exchange and wallet running the software has to apply the fix on its own machine, and the thefts were already underway before the warning went out. The software sits behind bitcoin checkout for Namecheap, which ran $73 million in BTC revenue across 1.1 million transactions through BTCPay between May 2020 and October 2024, along with hundreds of smaller merchants and several wallet backends.
“There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds,” the project wrote at 11:51 a.m. ET. “If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.” The post passed 550,000 views within five hours.
Founder Nicolas Dorier published release 2.4.2 the same morning with a one-line warning at the top: “This release contains fix of a critical vulnerability that is being actively exploited. You need to update as fast as you can.” The notes also tell integrators to upgrade NBXplorer, BTCPay’s wallet-tracking backend, to version 2.6.10.
Zach Herbert, chief executive of Foundation, the company behind the Passport hardware wallet, said his node was gone before he read the alert. “How many BTCPay lightning nodes were swept? Our Foundation node was drained overnight by attackers,” he wrote at 2:01 p.m. ET.
Herbert narrowed the damage an hour later: “This was just our BTCPay server that we use for payment processing, the hot wallet was untouched – only the lightning node was drained. All channels were closed and funds were swept.”
hodlonaut, the pseudonymous bitcoin commentator behind the zine Citadel21, reported the same pattern. “This is an ongoing attack on BTCPayserver users. Citadel21’s lightning node was just swept,” he wrote. “Fortunately there were not much funds there.”
At least one other operator described closed channels and drained funds in the replies to BTCPay’s warning. Neither Herbert nor hodlonaut disclosed amounts, and no one has published a tally of how many nodes were hit or how much bitcoin moved.
The flaw surfaced because someone got robbed. Dorier credited Craig Raw, the developer of Sparrow Wallet, for working out what was happening.
“We got extremely lucky that a dev was impacted who could analyze the logs to understand what was going on,” Dorier wrote. “Somehow, this wasn’t found AI scans, but by him losing money. :(“
That cuts against the premise of the Bitcoin Red Team, the volunteer group that has spent this week running AI-assisted audits across bitcoin’s open-source stack and that BTCPay thanked for the disclosure. Dorier said the group’s scans missed it.
“The AI report we got from red team didn’t include this one,” he wrote. “But this bug was really sneaky, I am not surprised a simple scan didn’t find it, or thought it was low risk.”
BTCPay has not said which flaw is being exploited, and Dorier ruled out the one authentication bug the changelog does disclose. After a user posted a Grok-generated explanation pinning the attack on that bug, Dorier replied: “This bug was found by the Red team, this isn’t the critical bug in question.”
The disclosed bug is a two-factor authentication bypass in Greenfield, BTCPay’s API, fixed on Aug. 4. The handler checked only for FIDO2 hardware keys before enforcing a second factor, so accounts protected by an authenticator app could be reached with an email and password alone and receive an unrestricted permission claim. The browser login screen enforced 2FA correctly the whole time.
Dorier followed that with a breaking change switching off Greenfield basic authentication five minutes after an account is created, reasoning that the scheme is almost never used and that turning it off shrinks the blast radius of related bugs. The release also rate-limits public invoice creation on payment requests, and a commit landed on release day marked nine controller methods across five files as non-routable, removing endpoints reachable over HTTP by accident.
A technical writeup is coming. “We are working with Bitcoin Red Team to fully process the details of vulnerability and will follow up with detail technical post shortly,” core contributor Uncle Rockstar wrote. Dorier, asked about holding details back, said: “I am wondering if it makes sense to wait… now that it is exploited in the wild.”
Patching alone does not close the incident. BTCPay told users to completely refresh macaroons and macaroons.db, the credential files that authorize access to an LND Lightning node, and to refresh authentication strings for other Lightning backends. Anyone who generated a hot on-chain wallet inside BTCPay should move those funds and recreate the wallet.
Kaloudis, whose ZEUS wallet runs on LND, put it more bluntly: “Don’t assume you’re safe after upgrading.”
Stolen macaroons survive a software update. An attacker who copied them before the patch keeps node access until the credentials are destroyed and reissued, which matches what the victims describe: channels force-closed and balances swept rather than the server itself compromised again.
The alert lands nine days into the worst stretch for bitcoin infrastructure security in years.
A 2021 Coldcard firmware bug that routed seed generation to a weak software randomizer has drained roughly $114 million in BTC since July 30 across more than 5,200 addresses, with victims describing the loss of life savings. On Aug. 3, the swap bridge Boltz halted its service indefinitely, saying “attackers now iterate faster than a team our size can find and patch.”
The Bitcoin Red Team formed in response to Coldcard. Calle, who helps run it, said on Aug. 5 that 16 researchers had filed 4,962 findings across 390 projects in 27.5 hours, including 85 critical and 635 high-severity issues.
Bitcoin traded near $64,800 on Friday afternoon, up 0.7% over 24 hours and 2.6% on the week, per CoinGecko, showing no reaction to the disclosure.
Supporting 12,000 transactions per second across three active cloud regions, the Amdocs Entitlement Server sets a new benchmark on Microsoft Azure for performance, reliability, and availability needed by large telecom operators to confidently launch and sustain eSIM services at scale
JERSEY CITY, NJ / ACCESS Newswire / May 13, 2026 / Amdocs (NASDAQ:DOX), a leading provider of software and services for communications and media companies, today announced that its Entitlement Server, the core of the Amdocs eSIM Cloud, has achieved a sustained 12,000 Transactions Per Second (TPS) across three geographically distributed Microsoft Azure regions in a production-grade, active-active deployment. This milestone represents one of the highest publicly benchmarked throughput levels for a carrier-grade entitlement server.
Achieved in collaboration with Microsoft and aligned with Azure’s Well-Architected Framework, the benchmark demonstrates the platform’s ability to deliver sub-second latency, continuous availability, and resilience at scale, even during peak demand events such as device launches, mass eSIM activations, and nationwide Rich Communication Services (RCS) rollouts.
As the entitlement server evolves into a strategic control point between devices, networks, and digital services, performance and resilience have become critical differentiators. Industry recognition reflects this shift, with Counterpoint Research naming Amdocs the #1 Pacesetter in both the 2025 Entitlement Server and eSIM Orchestration rankings.
This benchmark highlights a new standard for evaluating entitlement platforms: sustained throughput and multi-region resilience under real production load. As eSIM adoption accelerates across smartphones, wearables, vehicles, and IoT, operators require platforms that can scale to billions of transactions without compromise.
Built as a cloud-based software platform (SaaS), the Amdocs Entitlement Server is designed to deliver the scale and reliability required by large telecom operators. Its modular architecture and automated cloud management enable it to scale on demand, introduce updates without service interruptions, and quickly launch new services. The platform supports the full range of entitlement capabilities – from eSIM activation and device pairing to advanced messaging (RCS), voice services over LTE and Wi-Fi (VoLTE/VoWiFi), 5G network capabilities, and emerging satellite connectivity – all within a single, proven platform used by operators worldwide. The Entitlement Server leverages the latest technology from the Amdocs aOS Cognitive Core, ensuring efficient scale and seamless operations.
Key benchmark highlights include:
Active-active deployment across three Azure regions, helping to ensure continuous service with no failover disruption
99.999% availability, meeting Tier-1 operator requirements for mission-critical services
Validation against Azure’s Well-Architected Framework for reliability, security, and performance
“This achievement reinforces our commitment to delivering proven, carrier-grade platforms for the world’s largest operators,” said Anthony Goonetilleke, Group President of Technology and Head of Strategy, Amdocs. “The Entitlement Server brings the same cloud-native and AI-enabled foundations that span our portfolio, capitalizing on Amdocs aOS and Cognitive Core capabilities. “Together with Microsoft, we are enabling service providers to scale confidently and support the next wave of digital services.”
“This benchmark demonstrates what becomes possible when carrier-grade telecom workloads are architected for the hyperscale cloud from the ground up,” said Igal Figlin, Corporate Vice President – Azure Compute at Microsoft. “By engineering the Amdocs Entitlement Server to the standards of our Well-Architected Framework across three active Azure regions, we’ve proven that the most demanding telco operations can run with the same resilience and elasticity that the world’s largest digital enterprises expect.”
Supporting Resources
About Amdocs
Amdocs helps the world’s leading communications and media companies deliver exceptional customer experiences through reliable, efficient, and secure operations at scale. We provide software products and services that embed intelligence into how work runs across business, IT, and network domains – delivering measurable outcomes in customer experience, network performance, cloud modernization, and revenue growth. With our talented people, and more than 40 years of experience running mission-critical systems around the globe, Amdocs runs billions of transactions daily. Our technology is relied on every day, connecting people worldwide and advancing a more inclusive, connected world. Together, we help those who shape the future to make it amazing. Amdocs is listed on the NASDAQ Global Select Market (NASDAQ:DOX) and reported revenue of $4.53 billion in fiscal 2025. For more information, visit http://www.amdocs.com.
Amdocs’ Forward-Looking Statement
This press release includes information that constitutes forward-looking statements made pursuant to the safe harbor provision of the Private Securities Litigation Reform Act of 1995, including statements about Amdocs’ growth and business results in future quarters and years. Although we believe the expectations reflected in such forward-looking statements are based upon reasonable assumptions, we can give no assurance that our expectations will be obtained or that any deviations will not be material. Such statements involve risks and uncertainties that may cause future results to differ from those anticipated. These risks include, but are not limited to, the effects of general macroeconomic conditions, prevailing level of macroeconomic, business and operational uncertainty, including as a result of geopolitical events or other regional events or pandemics, changes to trade policies including tariffs and trade restrictions, as well as the current inflationary environment, and the effects of these conditions on the Company’s customers’ businesses and levels of business activity, including the effect of the current economic uncertainty and industry pressure on the spending decisions of the Company’s customers. Amdocs’ ability to grow in the business markets that it serves, Amdocs’ ability to successfully integrate acquired businesses, adverse effects of market competition, rapid technological shifts that may render the Company’s products and services obsolete, security incidents, including breaches and cyberattacks to our systems and networks and those of our partners or customers, potential loss of a major customer, our ability to develop long-term relationships with our customers, our ability to successfully and effectively implement artificial intelligence and Generative AI in the Company’s offerings and operations, and risks associated with operating businesses in the international market. Amdocs may elect to update these forward-looking statements at some point in the future; however, Amdocs specifically disclaims any obligation to do so. These and other risks are discussed at greater length in Amdocs’ filings with the Securities and Exchange Commission, including in our Annual Report on Form 20-F for the fiscal year ended September 30, 2025, filed on December 15, 2025, and for the first quarter of fiscal 2026 on February 17, 2026.
Media Contacts
Mario Hajiloizi
Amdocs Public Relations
E-mail: [email protected]
SOURCE: Amdocs Management Limited