In October 2026 an attacker used stolen UpdraftCentral keys to install backdoors on WordPress sites. It wasn't a vulnerability: the commands were signed with legitimate keys and the plugin obeyed them, so updating didn't fix it. You detect it by checking the updraft_central_localkeys option, a user with the Editor role and admin capabilities, and plugins with the description 'Small maintenance toolkit'. You fix it by deleting the keys first and the backdoor second.

The message always arrives on a Friday afternoon and always starts the same way: "the site is down". There's no campaign running, nobody touched anything, and the host replies that the server is perfectly fine. When you get in, every uncached request returns a 500 error. And in the plugin list there's one nobody installed, with a name that sounds like a system tool: Site Health Cache.

That plugin isn't the problem. It's the signature. Someone with permission to install plugins put it there, and that someone didn't come through the login form: they used a key your site considers legitimate. In October 2026 this stopped being a rare case and became a pattern: an attacker used stolen keys from the remote management service UpdraftCentral to plant backdoors on WordPress sites around the world. No vulnerability, no weak password, and no click from the victim.

The symptom: a site returning 500 and a plugin nobody installed

What makes this attack hard to believe is that, from inside WordPress, everything looks correct. The plugin was installed with the official installer, it has a plausible name and a normal description. There are no modified files, no new administrator, and the host's antivirus sees nothing. The site just fails.

The details that give the pattern away are three others, and none of them is in the administrator list:

  • A user with the "Editor" role who can actually install plugins. The account looks like an editor, so a quick review of administrators misses it. But it carries the manage_options and install_plugins capabilities, which is all you need to run code and promote yourself to administrator.
  • A plugin with an identical description in every case. The 99 backdoor names detected in that campaign were all different, but they all shared the same line: "Small maintenance toolkit: keeps option storage tidy." The description was the only reliable indicator; the name wasn't.
  • A login that never goes through the form. The backdoor sets a cookie directly, so two-factor authentication, login attempt limits and login protection plugins never run. If your security depends on the login, this attack walks in behind it.

And there's a fourth detail that explains why many people spotted it within minutes: the samples analysed had a coding error that threw a fatal error before the backdoor could activate. The site returned 500 on every request. That error was the luck of the first victims. A well-written backdoor doesn't throw errors: it waits.

Metal padlock resting on a computer keyboard on a dark desk The key that opens this door isn't on your site: it's on the vendor's dashboard. That's why changing your admin password doesn't protect you from it.

Why updating doesn't fix it

The natural reaction is to update the plugin, or delete it, and get on with the day. In this case neither closes the door, and understanding why is half the article.

The channel that listens at the root

UpdraftPlus is the most installed backup plugin in WordPress: over four million active installations. Inside it ships the UpdraftCentral client, a remote management service that lets you send commands to the site from a dashboard: run a backup, update, install. That channel listens on ordinary POST requests to the site root.

When you connect the site to the dashboard, an RSA key pair is generated: the site stores the dashboard's public key and, from then on, executes any command signed with the private key. There's no per-command confirmation. And the commands arrive properly encrypted and signed, so every check in the plugin passes: from your site's point of view, the instruction is legitimate because it's signed by the key holder.

The checkbox that comes ticked

Here's the part that stings: many sites hold a key without their owner knowing. When you connect a TeamUpdraft.com account, the screen includes a checkbox reading "Add this website to UpdraftCentral (remote, centralised control) – free for up to 5 sites". That box is pre-ticked in the code. If you don't untick it, the connection creates an UpdraftCentral key, with consent supplied by the plugin itself.

In plain terms: installing UpdraftPlus to have backups can enrol your site in a remote control system you never asked for.

Keys don't expire

The attack didn't exploit a code flaw: it used keys stolen from the vendor's environment. That's why the latest versions were just as exposed as older ones, and why updating wasn't the fix. The campaign was observed across an 18-hour window on 18-19 October 2026, with two source addresses that rotated within the same day: blocking IPs was useless.

And the detail that turns this into a years-long problem rather than a days-long one: keys don't expire. Keys issued in November 2025 still worked in October 2026. A key created by accident a year ago is still an open door today.

How to know if your site is on the list

You don't need to be an expert to find out. These five checks take an hour and, if everything is clean, leave you with a factual result for the report:

# What to look at What finding something means
1The updraft_central_localkeys option in the databaseA key is active: the site accepts remote commands. Even if you never used UpdraftCentral.
2Users with the Editor role and admin capabilitiesThat's the backdoor's disguise. Look by capability, not by name.
3Plugins with the description "Small maintenance toolkit"Backdoor installed. The name changes; the description doesn't.
4Channel log: plugin.upload_plugin with no admin actionUnauthorised remote installation.
5500 errors on every uncached requestMay be a broken backdoor sample. Don't repair it: remove it.

The fastest command, if you have WP-CLI, is wp option get updraft_central_localkeys. If it returns anything, there's a key. And yes: you need to check even if you never opened UpdraftCentral, because the pre-ticked box is enough.

What to do if you find it (in this order)

Order matters more than speed. If you delete the plugin before deleting the key, the attacker can push another one as soon as they notice.

  1. Delete the key first. From the dashboard: Settings → UpdraftPlus Backups → Advanced Tools → UpdraftCentral → "Manage existing keys" and remove them all. From the command line: wp option delete updraft_central_localkeys. Scheduled backups keep working; only remote management stops.
  2. Deactivate the malicious plugin and move it out of the folder rather than deleting it from the dashboard. Its uninstall routine is designed to erase its own traces, and running it destroys the evidence you need.
  3. Remove the backdoor account and the _sync_token option. The account outlives the plugin, and the attacker knows its password.
  4. Rotate anything that could have been exposed: admin passwords, backup dashboard access, API keys, and end all open sessions.
  5. Restore from a backup taken before the attack and compare files against a clean installation. If the trigger appears in the access logs, treat the site as fully compromised, not "suspicious".

If you can only do one thing today

Delete the UpdraftCentral keys. You don't need to migrate hosts, reinstall WordPress or hire a pentest to start. It's a database option that takes two minutes to remove and it closes the channel used in these attacks. After that, calmly review users by capability and the rest of the list.

Worried person in front of a laptop with a dark screen in a kitchen Most of these incidents aren't caught by an antivirus: they're caught by someone reading the log in time.

What this case says about the plugin ecosystem

It would be convenient to treat this as an anecdote about one vendor. It isn't. Patchstack's State of WordPress Security 2026 report counted 11,334 new vulnerabilities in the WordPress ecosystem during 2025, 42% more than the previous year. Of those, 91% were in plugins, not the core. And 46% had no fix available when they were publicly disclosed.

The figure that should keep any store owner awake is another one: the median time for the most targeted vulnerabilities to be mass exploited is five hours. Not five days. Five hours. A plugin left outdated over a weekend isn't a minor oversight; it's an open window with a sign on it.

This very week, the UK retail sector received an explicit warning: review the exposure of WordPress sites. The argument from the agency issuing it was uncomfortable and correct: in a self-hosted store, responsibility for updates, patching and payment security falls on the retailer or its providers. On a PCI DSS Level 1 certified platform such as Shopify, that part of the problem sits with the platform. It's not an opinion about which CMS is better: it's a decision about who carries the risk.

And there's a third reading, the one that comes up most when reviewing small sites: the number of plugins is the number of doors. Every plugin added is one more vendor that can be compromised, one more update that can break something and one more dependency nobody audits. The useful question isn't "is this plugin up to date?" but "who updates this, with what criteria, and what happens if one day it fails?".

How we handle it at TakeYourDesign

An incident like this isn't solved with a one-off cleanup. It's solved with three things you can put in writing:

  • An access and dependency audit. Which remote keys are active, which users have too many permissions, which plugins are installed and which are unused. Delivered with the list and a recommendation for each one.
  • Cleanup and rotation. Backdoor removal, key and account deletion, credential rotation and restoration from a pre-incident backup when needed.
  • Maintenance with monitoring. Updates tested in a staging environment before production, backups with a verified restore, uptime monitoring and a monthly report of what was done. That's exactly what we cover in how much website maintenance costs.

If your site runs on WordPress, the sensible starting point is a security and access review: cybersecurity for the diagnosis and WordPress development to leave the installation in a maintainable state. And if you're still deciding how many plugins your site needs, start with the most common security mistakes and with a backup strategy you can actually restore (the 3-2-1 rule).

The lesson worth repeating in a meeting is this: a site doesn't only get hacked through a weak password; it also gets hacked through misplaced trust. And trust, unlike a password, doesn't get changed on Monday morning.

Frequently asked questions

Is this a vulnerability in UpdraftPlus?

No. It's a theft of UpdraftCentral keys: commands arrive signed with legitimate keys and the plugin executes them. That's why updating doesn't fix it; you need to delete the keys.

I've never used UpdraftCentral. Am I affected?

You may be. When you connect a TeamUpdraft.com account the UpdraftCentral checkbox comes pre-ticked, so the key is created without asking. Check with wp option get updraft_central_localkeys.

Is updating or deleting the plugin enough?

No. The key stays alive and the attacker can push another plugin. Delete the key first, then remove the backdoor.

How do I know if my site has the backdoor?

Look for users with the Editor role and manage_options or install_plugins capabilities, and plugins whose description is 'Small maintenance toolkit: keeps option storage tidy.'. The plugin name isn't reliable.

Can it happen again after I clean the site?

Yes, if the key is still active or if accounts with excess permissions remain. Cleanup is completed with credential rotation, ending sessions and two-factor authentication.

What if my host says everything is fine?

The host looks at the server; this happens inside WordPress with valid credentials. The review happens in the database, the users and the logs. See cybersecurity.