Skip to main content
web60

Industry News

Rank Math PRO Malware and Stolen UpdraftCentral Keys: The Doors Nobody Was Watching

Ian O'Reilly··10 min read
Flat illustration of two open doorways on stone steps with a large deep navy key leaning against the nearer step, a teal diagonal band behind them on an off-white background

The owner of a model-railway and hobby shop in Carlow does everything the security guides ask. Updates switched on. A strong password. Two-factor login on every account. Treat this shop as a composite, assembled from the pattern October's advisories describe rather than from any one business, but every piece of it is ordinary. On Sunday 18 October, with the first Christmas train-set orders coming in, someone installs a plugin on that shop's website without logging in at all.

Nobody in the shop sees it happen. The plugin creates a hidden account, that account survives the plugin being removed, and on Monday the site quietly updates its backup plugin to a fixed version. The owner reads a headline about it, sees the update has already run, and gets back to packing orders.

That last step is the one I want to talk about. Not the attack. The moving on.

Two Trusted Channels in One Week

October produced two WordPress incidents that had nothing to do with weak passwords or a plugin left unpatched for years.

The first was Rank Math PRO, the paid edition of a widely used SEO plugin. Rank Math's own security notice says copies of PRO version 3.0.123 downloaded from rankmath.com, or received as updates, between 20:02 UTC on 15 October and 07:12 UTC on 16 October contained malicious code [1]. On Irish clocks, that ran from just after 9pm on the Thursday to a little after 8am on Friday. The free version on WordPress.org was not affected.

The second came days later. TeamUpdraft, the company behind the UpdraftPlus backup plugin, disclosed that its customer database was accessed over the weekend of 17 and 18 October, and that the exposed data included connection keys for UpdraftCentral, its remote management service [2]. Patchstack's researchers then recorded attackers using those keys to install backdoor plugins on connected sites, from Sunday afternoon into Monday morning [3].

Different vendors, different methods, one shared lesson: both arrived through a channel the site was built to trust.

Flat illustration of a teal house shape fed by a diagonal line of rounded teal blocks, with one deep navy block hidden among them, on an off-white background
Both October incidents arrived through channels a site is built to trust.

Door One: The Update That Came From the Right Place

Every guide tells you to install updates from the official source. Rank Math PRO users did exactly that. For roughly eleven hours, the official source was the problem.

According to Rank Math's notice, the affected files could recreate a hidden backdoor whenever someone visited the website, could expose credentials and secrets the site had access to, and may have left behind extra files, administrator accounts or server-level changes [1]. The vendor's advice is blunt. If you activated 3.0.123 during that window, assume the site is compromised. Deactivating the plugin is not enough. The whole folder has to go.

So what does that mean for someone selling train sets? It means the habit that protects a site most of the time, automatic updates, was the delivery route on this occasion.

I am not telling anyone to switch updates off. Out-of-date plugins remain the everyday risk, and turning updates off to dodge a rare event swaps an occasional danger for a constant one. What it does mean is that a site which takes updates automatically also needs a reliable rollback: a restore point from before the update, kept somewhere the update cannot reach.

Door Two: A Connection Someone Else Made Years Ago

This is the door our Carlow shop actually had open.

UpdraftCentral is a remote control dashboard. Its listing on WordPress.org's UpdraftPlus plugin page describes managing backups, updates, users, pages, plugins and themes across many sites from one place, and UpdraftPlus itself runs on more than four million sites [4]. Patchstack's analysis explains that the UpdraftCentral client ships inside every copy of UpdraftPlus, free and premium, and sits dormant until the site is given a key. Once it has one, the site runs any command signed by the dashboard, nobody confirms individual commands, and the keys do not expire [3].

Now think about who creates those keys. Usually it is whoever built or looked after the site. A web designer connects a client's site to their dashboard in 2022 so they can run updates in bulk. Later the relationship ends, yet the key stays on the site. Nobody tells the owner it exists, because it never appears as a user, a login or anything on the screens they look at.

TeamUpdraft's advisory tells UpdraftCentral users to check every site ever connected, even ones since disconnected or showing no problems [2]. Read that from the owner's side. If someone else connected your site, you may not know you are on that list.

This is a cost of the old hand-it-to-someone model that rarely gets mentioned. Paying a third party to manage a site often means granting them standing access through tools the owner cannot see. When you build and run your own site, you at least have the chance to know what is plugged into it. The same remote feature had a forged-command flaw patched back in June, which we covered when explaining why a backup plugin can be a security risk rather than a safety net.

Installing the Fix Is Not Cleaning Up

Back to Monday in Carlow. The fixed UpdraftPlus versions, 1.26.13 (free) and 2.26.13 (Premium), revoke the affected keys, and TeamUpdraft says WordPress.org pushed the update to sites automatically [2]. Good. The door is shut.

Whoever walked through it on Sunday is still inside.

Patchstack found that the backdoor plugin creates a hidden account with Editor rights plus the power to change settings and install plugins. It logs in by setting a cookie rather than going through the login form, which walks it straight past two-factor authentication and login protection plugins, and the account remains after the plugin is removed [3]. TeamUpdraft's own clean-up guidance adds a detail that catches people out: do not delete suspicious plugins through the WordPress dashboard. Deactivate them, then remove the folder directly through file access [2].

That is the gap. A fix closes the route in. It does nothing about what was already delivered. If an owner treats "updated" as "resolved", the hidden account sits there into December, and what happens next is the attacker's choice: a spam page, a redirect for mobile visitors, something quieter on the checkout. By the time anyone notices, it could be the busiest weekend of the year.

Both vendors point at the same clean route out, which is restoring a backup taken before the incident. Rank Math specifies before 20:02 UTC on 15 October [1]. TeamUpdraft says before 17 October [2].

The Trade-off Nobody Enjoys

A restore is not free. Roll the Carlow shop back to mid-October and every order, product edit and customer account created since goes with it, unless someone exports them first and puts them back by hand. On a quiet site that is an afternoon's work. With Christmas trading under way, it is a serious decision. That is the honest cost of the cleanest fix, and it is why a backup has to be older than the incident, and the restore has to be a choice made with eyes open rather than a panic button.

Flat illustration of a diagonal row of rounded teal blocks stepping back into the distance, each casting a deep navy shadow on an off-white background
A clean restore point has to reach back further than the incident itself.

What a Proper Setup Looks Like After October

Strip away the vendor names and the standard for a small business site is fairly clear.

  • Backups that live outside WordPress. If the backup tool is itself a plugin holding a remote key, it shares the risk it is meant to protect you from. A restore point should be taken at server level, kept away from the site, and stretch back past an incident you only hear about days later.
  • A snapshot before every update. Automatic updates stay on, and each one gets a rollback point, so a bad release costs minutes rather than a rebuild.
  • As few standing remote connections as possible. Every dashboard key is a door that never shows up as a user. If nobody needs one, it should not exist.
  • Somebody whose job it is to look. Scanning and hardening at server level, plus a human you can ring who knows what a hidden admin account looks like.

Web60 was built around that list. Nightly backups run automatically with one-click restore, safety snapshots are taken automatically before updates and restores, and the servers carry their own hardening, fail2ban intrusion prevention and automatic malware scanning, which together make up the backups and security that run beneath WordPress on Irish infrastructure. Because backups are part of the platform, a Web60 site does not need a backup plugin holding a remote key just to be recoverable. When something looks wrong, the support team is Irish-based and made up of real people.

Two limits, stated plainly. A malware scanner recognises what has already been identified, so a poisoned release in its first hours can slip past any signature-based scanner, ours included. And a nightly backup means the worst case is losing the changes made since the last run. Far better than losing everything. Still a cost worth knowing about.

There is also a real case where a different setup fits better. If you run dozens of sites with an in-house technical team that needs centralised management, audit trails and its own incident response, enterprise managed hosts with that tooling built in genuinely suit the workload. That is not the shop selling train sets, and it is not most businesses reading this.

Three Things to Verify Before December

If your site runs WordPress, and with W3Techs putting WordPress behind 38.5% of all websites there is a fair chance it does [5], these are worth a quarter of an hour this week. Whoever looks after your hosting can do them alongside you.

  1. Verify which plugins are installed. If Rank Math PRO is one of them, confirm with whoever handles updates what version the site was running on 15 and 16 October. The free version is not affected.
  2. Verify whether UpdraftPlus holds any UpdraftCentral keys. TeamUpdraft's guidance is to update, then delete any remaining keys under the plugin's Advanced Tools settings, even if you never knowingly used the remote dashboard [2].
  3. Verify every administrator and editor account. Any account you cannot put a name to is a question, and according to Patchstack an Editor with unusual extra powers is exactly the pattern to look for [3].

If any of those turns something up, treat the site as compromised and talk to your host before touching anything else. Our complete guide to WordPress security and backups covers what a full recovery involves.

The Lesson From October

More owners now build and run their own WordPress sites, and that is the right direction. AI builders have turned a months-long agency project into something you can describe in a sentence and deploy in a minute. What October showed is that owning the site also means knowing its doors, including the ones that never appear as a login. Updates are one. Remote connections are another. The way back is the backup, and it only works if it is older than the problem.

If you would rather start on a platform where backups, snapshots and scanning sit beneath WordPress instead of inside it, Web60 builds a WordPress site from a description of your business in about a minute, with everything included for €60 a year. Whichever platform you are on, the useful thing to ask your host this week is simple: if something got in on 18 October, how far back could you go?

Frequently Asked Questions

Is the free version of Rank Math affected by the October 2026 malware?

No. Rank Math's security notice says the problem affected only Rank Math PRO 3.0.123, downloaded from rankmath.com or received as an update between 20:02 UTC on 15 October and 07:12 UTC on 16 October 2026. The free plugin on WordPress.org was not affected. PRO users should be on 3.0.124 or later, downloaded by logging in directly at rankmath.com rather than through any emailed link.

If UpdraftPlus has updated on my site, is it safe?

Not necessarily. UpdraftPlus 1.26.13 (free) and 2.26.13 (Premium) revoke the affected UpdraftCentral keys, which closes the route in. They do not remove anything an attacker installed before the update. Look for plugins you do not recognise and for administrator or editor accounts nobody can explain, and delete any remaining UpdraftCentral keys in the plugin's Advanced Tools settings.

I never used UpdraftCentral. Do I still need to check?

Yes, if UpdraftPlus is installed. Patchstack's analysis notes that the UpdraftCentral client ships inside every copy of the plugin and stays dormant until the site is given a key, which can happen when a site is connected to a dashboard or a TeamUpdraft.com account. A previous web designer or maintenance provider may have connected your site without you ever seeing it.

Why should I not delete a suspicious plugin from the WordPress dashboard?

TeamUpdraft's clean-up guidance says to deactivate a suspicious plugin and then remove its folder directly, using SFTP, SSH or your host's file manager. Deleting a plugin from the dashboard can run that plugin's own uninstall code, and you should not let a malicious plugin run anything else on its way out. If you are unsure, ask your host to do it with you.

Should I turn off automatic plugin updates after this?

For most small business sites, no. Out-of-date plugins remain the everyday risk, while a poisoned official update is the rare one, and switching updates off swaps a rare risk for a constant one. Keep updates on and pair them with a snapshot before each update and nightly backups stored away from the site, so a bad release can be rolled back.

How far back should my website backups go?

Far enough to reach before an incident you might only hear about days later. In October, the clean restore points the vendors pointed to were from before 15 October for Rank Math PRO and before 17 October for UpdraftCentral. Ask your host how many days of backups are kept and where they are stored, and confirm the backups do not depend on a plugin inside the site itself.

Sources

IO
Ian O'ReillyOperations Director, Web60

Ian oversees Web60's hosting infrastructure and operations. Responsible for the uptime, security, and performance of every site on the platform, he writes about the operational reality of keeping Irish business websites fast, secure, and online around the clock.

More by Ian O'Reilly →

Ready to get your business online?

Describe your business. AI builds your website in 60 seconds.

Build My Website Free →
Buy NowTry Free
Rank Math PRO Malware and Stolen UpdraftCentral Keys | Web60