Over the weekend of 17 to 18 October 2026, someone broke into teamupdraft.com, the vendor site behind the UpdraftPlus plugin. The company's incident notice says the customer database was probably accessed, including connection keys for UpdraftCentral, the plugin's remote-management service. Within a day, those keys were being used to plant backdoor plugins on customers' WordPress sites.

Nothing on the affected sites was out of date or misconfigured; every check passed. The weak point was a key most owners did not know existed, created by default and never expiring.

What happened

Each site connected to UpdraftCentral stores a key and accepts signed commands sent to its front page. According to Patchstack's analysis, the attacker used the stolen keys to send a plugin.upload_plugin command. WordPress installed and activated a new plugin.

That plugin is the backdoor. It waits for a request carrying a secret parameter with a 32-character token, then creates a user with the Editor role and a hard-coded password and grants it manage_options and install_plugins, enough to become administrator and run arbitrary code. It sets the login cookie directly, so two-factor authentication and login-protection plugins never run. The account survives removal of the plugin.

Patchstack's telemetry puts the first install at 15:32 UTC on 18 October and the latest at 09:23 UTC on 19 October, roughly an 18-hour window. Early samples had a coding error that crashed sites with HTTP 500, which is how some victims noticed. Do not repair such a plugin, Patchstack warns: fixing the error switches the backdoor on.

Why so many sites had a key

UpdraftPlus runs backups on more than three million sites, according to Search Engine Journal (Patchstack says 4M+). Most owners never set out to use remote management, but linking a site to a TeamUpdraft.com account had "Add this website to UpdraftCentral" ticked by default, so a key was created anyway. Keys never expired: Patchstack found keys from November 2025 still working in October 2026. Only sites with an active UpdraftCentral Cloud connection were exposed, but that group is far larger than the people who used the feature.

Patchstack's line on 19 October was that "this is not a vulnerability in UpdraftPlus, and as of 19 October no plugin update stops it." There is no CVE, because there is no code flaw; the attacker held legitimate keys.

What the fix does, and what it does not

Just after 22:00 BST on 19 October, TeamUpdraft published UpdraftPlus 1.26.13 (free) and 2.26.13 (Premium); WordPress.org pushed them automatically. The update revokes UpdraftCentral Cloud keys issued before 13:07 BST on 18 October, closing the channel (1.26.13 also corrected the revocation logic of the build just before it). UpdraftVault credentials were reissued and UpdraftClone keys replaced. Self-hosted UpdraftCentral is not affected.

The update does not remove a backdoor plugin that is already installed, and it does not delete the rogue Editor account. TeamUpdraft says so plainly: the extent of the attacker's activity is unknown, so every connected site must be checked by hand.

Who is affected

  • Any WordPress site running UpdraftPlus, free or Premium, that held an UpdraftCentral Cloud key. If you ever linked the plugin to a TeamUpdraft.com account, assume you did.
  • Anyone with a teamupdraft.com account: names, emails, billing addresses, hashed passwords and 2FA settings are believed accessed. No card data was stored.
  • Not affected: self-hosted UpdraftCentral, the plugin downloads, and backups in your own remote storage.

What to do now

  1. Check for a key. Any output means exposed, even if you never opened UpdraftCentral.
wp option get updraft_central_localkeys
  1. Delete the key. Settings > UpdraftPlus > Advanced Tools > UpdraftCentral, or wp option delete updraft_central_localkeys.
  2. Hunt for the rogue account. Editor-role users that also hold manage_options. Known usernames look like data-ops43 or media-staff96, with an @example.org email and display name "Site Tools".
wp user list --role=editor --fields=ID,user_login,user_email,display_name
wp option list --search='*_sync_token'
  1. Hunt for the plugin. Patchstack catalogued 99 names; "Site Health Cache" was reused most, the rest are random pairs like "Css Forge". The reliable marker is the description "Small maintenance toolkit: keeps option storage tidy." Check Must-Use plugins too.
grep -rl 'keeps option storage tidy' wp-content/plugins wp-content/mu-plugins
  1. Check the logs. Search access logs for a 32-character token parameter, and the UpdraftCentral log for Command received: plugin.upload_plugin.
  2. If you find anything, treat the site as fully compromised. Move the plugin out of the web root rather than uninstalling from wp-admin, because its uninstall routine erases its traces. Delete the account and the _sync_token option. Restore from a backup taken before 17 October, rotate admin passwords, storage credentials and API keys, and turn 2FA back on.
  3. Rotate the vendor side. Change your teamupdraft.com password, reset its 2FA and re-authorise remote storage.
  4. Decide whether you need remote management at all. If not, stay disconnected. If so, record which sites are connected and rotate keys on a schedule; the vendor will not expire them for you.

How Scantinel helps

Scantinel scans your site from the outside, as an attacker sees it: outdated plugin versions, known-vulnerable components, missing security headers, exposed files. It can also notice new plugin paths appearing between scans, sometimes the only outside hint that something was planted.

What an external scan cannot see is a rogue Editor account in your database or a key in wp_options. That part is manual. The lasting lesson is inventory: know every remote-management connection your sites hold, who issued the key, and when it expires. If the answer is "never", change that today.