Join our Newsletter — 33% off our NHI Course
Home› NHI Breaches› UpdraftCentral Key Theft 2026: How Stolen Connection Keys…
Breach analysis Incident: 19 Oct 2026

UpdraftCentral Key Theft 2026: How Stolen Connection Keys Were Used to Backdoor WordPress Sites

PDF for newsletter subscribers · free to read online

← All NHI breaches
By NHI Mgmt Group, edited by Lalit Choda Updated 26 October 2026 12 min read
On this page

Over the weekend of 17 and 18 October 2026, an attacker got into teamupdraft.com, the site behind the UpdraftPlus WordPress backup plugin, and, according to the company, most likely its customer database. That database held the connection keys that let the cloud version of UpdraftCentral, TeamUpdraft's remote management dashboard, send commands to customers' WordPress sites. From 18 October the attacker used those keys to send validly signed commands that installed backdoor plugins. Patchstack counted 99 distinct backdoor plugin names, and Nethemba, which found the campaign on its own sites, showed the commands carried genuine signatures. BleepingComputer, citing the vendor, puts the number of sites potentially exposed at about 400,000. TeamUpdraft disclosed the incident on 19 October 2026 and released UpdraftPlus 1.26.13 and 2.26.13 to disconnect old UpdraftCentral connections. Site owners still need to delete keys and check for backdoors.

Key takeaways

  • TeamUpdraft says an attacker accessed teamupdraft.com over 17 and 18 October 2026 and believes its customer database was taken, including password hashes, two-factor settings and connection keys for UpdraftCentral, UpdraftVault and UpdraftClone.
  • Patchstack saw the first backdoor installed at 15:32 on 18 October and recorded 99 distinct backdoor plugin names in an 18-hour window, many disguised as maintenance tools such as "Site Health Cache".
  • Nethemba proved the commands were signed with real dashboard keys and that the sites were fully patched. Keys never expire, so keys from November 2025 still worked.
  • BleepingComputer reports about 10% of UpdraftPlus sites have an UpdraftCentral or Migrator key, which puts around 400,000 sites potentially at risk. How many were actually backdoored has not been disclosed.
  • The identity lesson: a non-expiring remote management key held by a vendor is a standing admin credential for every connected site, and a vendor database breach turns all of them into an attack channel at once.

At a glance

OrganisationsTeamUpdraft (UpdraftPlus, UpdraftCentral, UpdraftVault, UpdraftClone); WordPress site owners connected to UpdraftCentral cloud, including Nethemba
WhenVendor site accessed 17 to 18 October 2026; backdoor installations from 18 October to 19 October 2026; disclosed by TeamUpdraft, Patchstack and Nethemba on 19 October 2026
AttackerUnknown. No actor has been named by TeamUpdraft or the researchers
Entry pointUnauthorised access to teamupdraft.com; TeamUpdraft's 21 October update says the attacker used a compromised key, without saying which
Identities abusedUpdraftCentral cloud dashboard keys used to sign remote management commands; customer database also held UpdraftVault and UpdraftClone keys and account password hashes
Impact99 distinct backdoor plugins observed by Patchstack; backdoors installed on two of Nethemba's three sites; about 400,000 sites potentially exposed according to BleepingComputer; total number of compromised sites not disclosed
CategoryNHI. Incident class: confirmed NHI breach (stolen vendor-held connection keys used to sign commands to customer sites)

What happened

UpdraftPlus is one of the most used WordPress backup plugins, with more than 4 million installations according to Nethemba. Every copy ships with the UpdraftCentral client, which lets a site be managed remotely from an UpdraftCentral dashboard. Patchstack explains the model: when a site is connected to the cloud dashboard or to a teamupdraft.com account, a key pair is created, and the site will then execute any command signed with the dashboard's private key, with nobody confirming individual commands. Those dashboard keys are generated and held by UpdraftCentral Cloud, not by the site owner. Patchstack and Nethemba both note that the option to add a site to UpdraftCentral is ticked by default when an owner logs in to their teamupdraft.com account, so some owners had keys they did not know about. The keys do not expire.

Nethemba's Pavol Lupták noticed the attack on three of the company's own WordPress sites on the night of 18 to 19 October. An address sent each site a plugin upload command through UpdraftCentral. Two sites installed a backdoor plugin; the third refused because its key belonged to a user without the right to install plugins. All three were running WordPress 7.1.3 and UpdraftPlus 2.26.11, already patched against CVE-2026-10795, a separate forged-command flaw fixed in June 2026. Nethemba ruled out a modified plugin, a swapped key, weak cryptography and that CVE, and concluded the commands were signed with genuine keys from the vendor side. "The fault was not on our side," the post says. Patchstack, crediting Nethemba with the discovery, wrote: "This is not a vulnerability in UpdraftPlus, and as of 19 October no plugin update stops it."

Patchstack's telemetry showed the first backdoor installation at 15:32 on 18 October, which BleepingComputer gives as UTC, and the latest at 09:23 on 19 October. It logged 99 distinct backdoor plugin names, mostly random two or three word names, with "Site Health Cache" reused many times. Each backdoor let the attacker create a hidden account and log in without the login form, which bypasses two-factor authentication and login protection plugins. Patchstack says removing a site from the dashboard is not enough because the key that matters is stored on the site, and Nethemba warns the attacker kept coming back to sites where a backdoor had been removed but the key had not.

TeamUpdraft published its notice on 19 October 2026. It says it believes the customer database was accessed, including names, email and billing addresses, order history, password hashes, two-factor settings and the UpdraftCentral, UpdraftVault and UpdraftClone connection keys. Card data was not stored, the UpdraftPlus plugin and its downloads were not affected, and self-hosted UpdraftCentral was not affected. UpdraftPlus 1.26.13 and 2.26.13, pushed through WordPress.org, disconnect UpdraftCentral connections made before 13:07 BST on 18 October. Nethemba and BleepingComputer warn that the earlier 1.26.12 and 2.26.12 releases did not remove keys. TeamUpdraft also disconnected every UpdraftVault site and replaced all UpdraftClone keys. Its 21 October update says the attacker used a compromised key, that it has engaged an external security firm and contacted the police, and that it has no evidence the attacker still has access. It has not said how the attacker first got in.

Timeline

DateEvent
June 2026TeamUpdraft fixes CVE-2026-10795, an unrelated forged-command flaw, in UpdraftPlus 1.26.5 and 2.26.5.
17 October 2026Unauthorised access to teamupdraft.com begins over the weekend of 17 and 18 October, according to TeamUpdraft.
18 October 2026Patchstack observes the first backdoor plugin installed through a signed UpdraftCentral command at 15:32.
19 October 2026Nethemba detects the attack on its sites and publishes an analysis; Patchstack publishes its research and blocks UpdraftCentral commands; TeamUpdraft publishes its incident notice and releases UpdraftPlus 1.26.13 and 2.26.13 late that evening.
20 October 2026BleepingComputer reports the campaign and the estimate of about 400,000 exposed sites.
21 October 2026TeamUpdraft says a compromised key was used, engages an external security firm and contacts the police.
23 October 2026TeamUpdraft last updates its notice, asking customers to check every UpdraftCentral-connected site.

How it happened: the identity attack path

  1. Vendor platform accessed. The attacker gained access to teamupdraft.com. TeamUpdraft says a compromised key was used but has not said which key or how it was obtained.
  2. Customer key store taken. The customer database held the UpdraftCentral cloud keys that sites trust to sign management commands, along with Vault and Clone keys and password hashes.
  3. Signed commands sent. From its own server, the attacker used the stolen keys to send validly signed plugin upload commands to connected sites. Each command ran with the rights of the WordPress user who created the key, with no confirmation from the site owner.
  4. Backdoor installed. WordPress installed the plugin through its normal installer. Sites whose key belonged to a user without plugin install rights were not affected in this way, as Nethemba's third site showed.
  5. Persistent admin access. The backdoor created a hidden account and allowed login without the login form, bypassing two-factor authentication. Because the key stayed valid, the attacker could return even after a backdoor was removed.

Impact

  • Confirmed: TeamUpdraft says its customer database was likely accessed, exposing connection keys, password hashes and two-factor settings for teamupdraft.com accounts. Patchstack recorded 99 distinct backdoor plugins; Nethemba confirmed backdoors on two of its three sites, one of which returned errors on every uncached request until restored.
  • Potential: About 400,000 sites with an UpdraftCentral or Migrator key, according to BleepingComputer. The number actually backdoored has not been disclosed, and Nethemba says it could not determine how many sites the attacker reached.
  • Not affected, according to TeamUpdraft: payment card data, the UpdraftPlus plugin and its downloads, backups stored in customers' own remote storage, and self-hosted UpdraftCentral.
  • Wider: All UpdraftVault sites were disconnected and every UpdraftClone key replaced, so customers had to reconnect and redistribute keys. Agencies and hosts that manage many client sites through one dashboard face the largest clean-up.

What this means for NHI governance

No WordPress vulnerability was used here. The sites did exactly what they were built to do: trust any command signed by a key the vendor held. That makes the connection key a machine credential with administrator power over each site, and the vendor's database a store of thousands of such credentials with no expiry and, in many cases, no owner who knew they existed. It is the same pattern as the ConnectWise Cloud Backup breach in the same week, where one vendor-held app secret reached hundreds of Microsoft 365 tenants, and it echoes platform breaches such as Railway and Zeabur, where customers' secrets were held centrally by the provider.

Three governance gaps stand out. The keys never expired, so year-old connections were still live. They were created by a default-on checkbox, so inventory was incomplete. And they carried the full rights of whichever admin made them, when remote backup management rarely needs plugin installation. Our API Key Management Guide and NHI Offboarding and Decommissioning Guide cover expiry, scoping and removing credentials that are no longer used, and the PHP and WordPress Security Guide covers site hardening.

Recommendations

  • Delete UpdraftCentral keys on every site. Update to UpdraftPlus 1.26.13 or 2.26.13 or later, not 1.26.12 or 2.26.12, then remove keys by hand under UpdraftPlus Backups, Advanced Tools, UpdraftCentral. Do this even if you never knowingly used UpdraftCentral. See our NHI Offboarding and Decommissioning Guide.
  • Check for backdoors and hidden accounts. Look for unrecognised plugins, including must-use plugins, unexpected administrator or editor accounts and unfamiliar addresses in logs. If you find one, treat the site as fully compromised and restore from a backup taken before 17 October 2026. See our PHP and WordPress Security Guide.
  • Rotate every related credential. Change WordPress administrator and teamupdraft.com passwords, end sessions, reset two-factor authentication, re-authorise remote storage and change storage access keys, as TeamUpdraft advises. See our Secrets Management Guide.
  • Scope remote management keys to least privilege. Nethemba's third site survived because its key belonged to a user without plugin install rights. If you reconnect, create keys under an account that cannot install plugins. See our API Key Management Guide.
  • Inventory and expire machine credentials you did not create on purpose. Default-on integrations create keys silently. Track them, give them owners and set expiry wherever the product allows.
  • Ask vendors where your keys live. Where a SaaS provider holds signing keys that can act on your systems, ask how they are stored, whether they expire and how you will be told of exposure. See our Third-Party Access Guide.

Frequently asked questions

Was UpdraftPlus hacked?

The UpdraftPlus plugin code and its downloads were not affected, according to TeamUpdraft. What was breached was the vendor's website, teamupdraft.com, and its customer database. Stolen UpdraftCentral connection keys from that database were then used to send signed commands to sites running UpdraftPlus, which is why Patchstack says it is not a vulnerability in the plugin.

Is my WordPress site affected by the UpdraftCentral key theft?

Your site is exposed if it holds an UpdraftCentral cloud key, which can exist even if you never used UpdraftCentral, because the connection option is ticked by default on login to a teamupdraft.com account. Update UpdraftPlus to 1.26.13 or 2.26.13, delete any remaining keys, and check for unknown plugins and accounts. Free users without a teamupdraft.com account need no action beyond updating, according to TeamUpdraft.

Does updating UpdraftPlus remove the backdoor?

No. Versions 1.26.13 and 2.26.13 disconnect old UpdraftCentral connections, but they do not remove a backdoor plugin or hidden account already installed. Patchstack and Nethemba both advise deleting the key first, then removing the backdoor, and treating any site with a backdoor as fully compromised, ideally restoring from a backup made before 17 October 2026.

ConnectWise Cloud Backup breach 2026 · Gravity SMTP exposed API keys 2026 · GoDaddy Managed WordPress breach 2021 · API Key Management Guide · PHP and WordPress Security Guide

How NHI Mgmt Group can help

Remote management keys, backup connectors and plugin integrations rarely show up in an identity inventory, yet each one can act on a system with admin rights. Our training helps teams find these machine credentials, give them owners and expiry, scope them to what the integration really needs, and respond quickly when a vendor that holds them is breached. See our NHI and AI agent security training.

References

PDF for subscribers

Take this breach analysis with you

The full analysis in one PDF: timeline, attack path, impact and recommendations, with links to the sources and related pages. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 26 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.