UpdraftCentral key compromise: who is affected and the cleanup order
TeamUpdraft reported unauthorised access to its systems over 17 and 18 October 2026, including the connection keys that let its hosted UpdraftCentral service manage customer sites. Those keys were used to push plugins and create administrators on connected sites. UpdraftPlus 1.26.13 revokes the old keys; it removes nothing that was installed through them. Sites that never connected to the hosted UpdraftCentral are outside the incident.
Prepared by G. Schad, WordPress and Linux security specialist
First published in the weekly briefing of 26 October 2026 and moved here unchanged, so the indicators and the cleanup order have a page of their own.
Affected
Sites connected to the UpdraftCentral cloud service hosted by TeamUpdraft on or before 18 October 2026
Not affected
Self-hosted UpdraftCentral, the UpdraftPlus plugin downloads, and sites that never connected
Fix
UpdraftPlus Free 1.26.13 or Premium 2.26.13 revokes the old connections
Then
Check plugins, must-use plugins, users and cron: the update revokes the key and removes nothing
Supply chain · UpdraftCentral
UpdraftCentral: stolen connection keys used against the sites they managed
TeamUpdraft, the company behind UpdraftPlus, says it identified unauthorised access to its systems over the weekend of 17 and 18 October. The customer database it believes was accessed held names, email and billing addresses, order history, password hashes, two-factor authentication settings, and the connection keys for three services: UpdraftCentral, the hosted console that manages WordPress sites remotely; UpdraftVault, its backup storage; and UpdraftClone. No card data was held; payments go through Stripe and PayPal. The attacker used UpdraftCentral keys to do what the console is for, sending commands to the connected sites, and TeamUpdraft reports administrator accounts created, malicious plugins installed, and a pattern of unexpected editor roles. It does not yet know the full extent.
The scope matters, because most UpdraftPlus installs are not in it. Affected are sites connected to the UpdraftCentral cloud service hosted by TeamUpdraft. A self-hosted UpdraftCentral is not affected. The UpdraftPlus plugin and its downloads were not tampered with. Backups kept in your own remote storage were not accessed, though TeamUpdraft says a site that was reached through UpdraftCentral should re-authorise its storage and rotate the storage credentials, since the attacker had the same access to them that the site did. UpdraftVault was disconnected from every site and reissued credentials, so Vault backups stop until each site reconnects; every UpdraftClone key was replaced.
The plugin fix is UpdraftPlus Free 1.26.13 or Premium 2.26.13, released just after 22:00 BST on 19 October. It revokes every UpdraftCentral cloud connection made before 13:07 BST on 18 October. The changelog records that 1.26.12, released the same day, was meant to do this and did not: 1.26.13 is described as properly applying the revocation in 1.26.12. By 20 October WordPress.org had pushed the release to all users, so most sites have it; check the version anyway, because a site with automatic updates disabled or a stuck filesystem lock has not. Wordfence’s analysis of the campaign, which this briefing draws on for the indicators below, describes the attacker sending signed plugin.upload_plugin commands over the console’s own protocol with valid keys, which is why nothing on the site side looked like an attack.
Figure 1 · At a glance
The update revokes the stolen key. It removes nothing the key was used to install.
Question
Answer
Affected
Sites connected to TeamUpdraft’s hosted UpdraftCentral on or before 18 October 2026
Not affected
Self-hosted UpdraftCentral; the UpdraftPlus plugin downloads
Fix
UpdraftPlus Free 1.26.13 or Premium 2.26.13 revokes the old connections
Look for
Plugins with generated names, must-use files, hidden administrators, class-udrpc.php requests
Order
Preserve, revoke and update, inspect from outside WordPress, remove and rotate
The points that decide what to do about the UpdraftCentral connection-key compromise, as stated in the sections below.
Indicator
Where to look
What it means
Requests with the user agent WordPress/6.4; class-udrpc.php
Web server access logs from 17 October onward
Traffic over UpdraftCentral’s remote-procedure channel. Legitimate console use produces it too; the question is the timing and what followed
Plugins with generated names such as Load Stack 35C, style-bridge-8f5, site-health-6a20 or cache-frame
wp-content/plugins and wp-content/mu-plugins on disk, not the Plugins screen
Payloads pushed through plugin.upload_plugin. The names vary; look for folders with no WordPress.org counterpart and recent creation dates
Code that calls wp_set_auth_cookie() after a hash_equals() check
Any PHP file on the site, by content
A backdoor that logs an attacker in as a chosen user when the right secret is presented, with no password
Filters on pre_user_query and pre_count_users
Plugin and must-use plugin code; wp eval of the filter table with plugins loaded
The mechanism that hides an administrator from the user list and the user count
Requests to / with one parameter of twelve hexadecimal characters carrying a 32-character value
Access logs, GET and POST
Observed as the trigger for the login backdoor. Treat it as a correlation pattern, not proof on its own
Administrators or editors you did not create, with recent registration dates
wp user list --skip-plugins --skip-themes, and the wp_users and wp_usermeta tables
TeamUpdraft reports both administrator creation and unexpected editor roles
An UpdraftCentral key the site still holds
wp option get updraft_central_localkeys --skip-plugins --skip-themes
A connection that predates the revocation if the site has not updated; delete it and reconnect fresh
Cleaning a site that was connected to UpdraftCentral cloud
For every site that was connected to the hosted UpdraftCentral on or before 18 October. The order matters: preserve first, revoke second, then look, then rotate. Work from a device that is not the one whose TeamUpdraft password may have been reused.
01
Preserve before you change anything
Copy the access logs from 17 October onward, the plugin and must-use plugin folders, and a database dump to somewhere outside the site. If the site turns out to be compromised, this is the evidence of what was done with it.
02
Revoke the key and update
Delete the UpdraftCentral connection key from UpdraftPlus, Advanced Tools, UpdraftCentral, or remove the option from WP-CLI, then update to 1.26.13 or 2.26.13 or later, which revokes any key that predates 13:07 BST on 18 October:
A site still on 1.26.12 believed it had revoked the keys and had not.
03
Inspect from outside WordPress
List users, plugins and must-use plugins with every plugin skipped, so a hiding filter cannot run, and compare against the folders on disk:
shell
$ wp user list --role=administrator--skip-plugins--skip-themes$ wp user list --role=editor--skip-plugins--skip-themes$ wp plugin list --skip-plugins--skip-themes$ ls-la wp-content/mu-plugins wp-content/plugins
Then search the whole site for wp_set_auth_cookie near hash_equals, for pre_user_query and pre_count_users, and for PHP in uploads, drop-ins such as advanced-cache.php and object-cache.php, the theme folders and the site root.
04
Remove what was installed, and rotate
Delete the plugins and users that do not belong, and the cron events they registered. Change every administrator password, invalidate all sessions and regenerate the salts in wp-config.php. If the site uses UpdraftVault or remote storage that UpdraftCentral could reach, re-authorise it and rotate the storage credentials.
05
Reset the TeamUpdraft account
From a clean device, type the address directly rather than following a link, change the password, change it anywhere else it was reused, and reset two-factor authentication. The database held password hashes and 2FA settings, so both are compromised.
06
If there is evidence, restore and investigate
A site with an unknown administrator, a generated-name plugin or the login backdoor should be restored from a backup taken before 17 October, then re-patched and re-inspected, and the account around it should be checked for what the attacker did with the site’s credentials. That is incident response, not maintenance.
07
Reconnect last
Create a new UpdraftCentral connection only after the site is clean and updated. Reconnect UpdraftVault with the new credentials and run a manual backup to confirm it works.
Keep reading
Briefings and advisories related to UpdraftCentral
Common questions about the UpdraftCentral incident
I use UpdraftPlus for backups but never set up UpdraftCentral. Am I affected?
Not by the key compromise. The plugin and its downloads were not tampered with, and backups in your own storage were not accessed. Update to 1.26.13 or 2.26.13 anyway. If you have a teamupdraft.com account, change its password and reset two-factor authentication, because the database held both.
I already updated UpdraftPlus to 1.26.13. Is the site safe?
The key is revoked, so nothing more can arrive through it. Anything that arrived before, a plugin, an administrator, a cron event, a login backdoor, is still there. Inspect users and plugins from WP-CLI with plugins skipped and from the file system, because the observed malware hides itself from the dashboard, and restore from before 17 October if you find anything.
Choose the response path
UpdraftPlus is updated and something was already installed: choose the response path.
The server under the sites
Get every PHP branch, the namespace setting and the account boundaries checked and proven.
Best when several servers need the PHP packages verified by changelog, the logs from 17 October read, the CloudLinux mitigation assessed against what customers run, and WP Toolkit’s cross-account risk reviewed, with a written result per host.
Get the finding classified and the site restored to a trusted state.
Best when an UpdraftCentral-connected site shows a plugin or administrator you did not create, a PHP worker wrote something it should not have, or an exploited plugin left an account behind, and you want every layer removed in one pass rather than one at a time.