“Turn on auto-updates” is the first line of nearly every WordPress hardening guide, and it is good advice. Last week, though, the Rank Math PRO supply chain attack showed why that advice needs a second sentence. A WordPress backdoor arrived inside the official package itself. For about eleven hours, some copies of a paid SEO plugin came from the vendor’s own downloads carrying malware. Keeping everything patched only helps if you also check what the patch actually installed.
What Rank Math Says Happened
In its security incident notice, Rank Math says it identified “a security issue affecting a limited number of users who downloaded Rank Math PRO v3.0.123 between October 15, 2026, at 20:02 UTC and October 16, 2026, at 07:12 UTC.” For readers in Eastern time, the notice says that window opened at 16:02 EDT on October 15. The company says, “The affected plugin files contained malware that could compromise your website if the plugin was activated,” and adds, “We immediately removed the affected files and released a clean version, Rank Math PRO v3.0.124.”
So, to be specific:
- Edition: Rank Math PRO, the paid plugin.
- Version: 3.0.123, and only copies obtained during that window. The vendor says “a limited number” of users and gives no count.
- Fixed version: 3.0.124.
- The free plugin: not affected. Rank Math says, “This issue affects Rank Math PRO users only. If you use the free version of Rank Math SEO available on WordPress.org, your website is not affected, and no action is needed.”
The vendor addresses users who “downloaded or updated to the affected version,” so both manual downloads and updates are in scope. BleepingComputer reports that the bad copies came “from the vendor’s official website.”
What Nobody Has Said Yet: How It Got In
The headline I was handed said the plugin was “hijacked.” I have not found a source that explains the mechanism. Rank Math’s notice does not say whether its build system, its download servers, or a developer or staff account was compromised. BleepingComputer says it “contacted Rank Math for details on the number of potentially affected sites and the initial attack vector but had received no response by the time of publication.” SecurityWeek calls it a supply chain attack and says “hackers injected malware” into the 3.0.123 packages, but gives no root cause. Until Rank Math publishes one, “hijacked update channel” and “stolen developer account” are both guesses, and I am not going to pick one.
Does the Backdoor Really Restore Itself?
According to the vendor, yes. Rank Math warns: “The malware can recreate its hidden backdoor whenever someone visits the website. Removing suspicious files before disabling the mechanism that recreates them may not resolve the issue.” Its manual cleanup section begins with a step titled “Stop the malware from rebuilding itself.” That step means deleting the whole rank-math-pro folder (“Deactivating the plugin alone is not sufficient”), removing a malicious entry from the wp_options table, and blocking outbound connections to rank1cdn.com.
SecurityWeek’s summary matches: the malware “may recreate a hidden backdoor upon each page visit,” and its persistence “could make manual cleanup a difficult task.” Note the “may.” Both sources describe what the malware can do, not a count of sites where it did.
Rank Math’s list of indicators to check includes:
- Administrator accounts with usernames starting “wpsupport_” or email addresses ending in “@wp-mail[.]net.”
- A fake core file, wp-includes/class-wp-cache-util.php, which Rank Math says “is not a legitimate WordPress core file.”
- .htaccess rules that let .cache files run as PHP, and .cache files containing PHP.
- Crontab entries tagged “#ms6v46” for the web server user.
- Suspicious PHP files in mu-plugins, other plugins, theme folders, and uploads.
It also says the attacker “may have made changes outside your WordPress installation,” and points to SSH authorized_keys files, other users’ crontabs, and running processes. BleepingComputer adds one finding of its own. It found a PHP sample on VirusTotal that carries the same indicators and includes code to steal cloud credentials and SSH keys. BleepingComputer is careful to say it “could not confirm whether it was distributed through the compromised plugin,” and I will leave it at that.
If You Run Rank Math PRO
This part is the vendor’s guidance, condensed. If you installed and activated 3.0.123 during the window, Rank Math says to “Treat your website as compromised.” Its preferred fix is to restore files and database from a backup made before the window, scan, rotate every credential, and then install 3.0.124. It says rotating credentials is “essential, even if you restore your website from a backup.” If you installed but never activated it, delete it, install 3.0.124, and scan. Simply updating to 3.0.124 does not clean an infected site, because the malware’s other files live outside the plugin folder.
My Recommendations for Vetting and Watching Plugins
Everything in this section is my own recommendation, not Rank Math’s or anyone else’s.
- Stage premium plugin updates. Auto-updates for plugins from WordPress.org are still worth it for most sites. For paid plugins that update from a vendor’s own servers, I would let a staging site take each update first and hold production back by a day. An eleven-hour bad window is exactly what a short delay protects against. The trade-off is that you also delay real security fixes, so keep the delay short.
- Keep your own known-good copies. Rank Math notes that checksum verification “may not be available for every plugin, particularly premium plugins.” Save the zip of every premium version you deploy, with a hash. Then you have something to compare against later.
- Watch file changes outside update windows. A file-integrity monitor that alerts on new PHP files in uploads, mu-plugins, or wp-includes would have caught several of the indicators above. Run wp core verify-checksums on a schedule, not just after an incident.
- Alert on new administrators. New admin accounts on a small site should be rare. Make each one page someone.
- Restrict outbound traffic from the web server. Most WordPress sites need to reach only a short list of hosts. An allowlist turns a callback domain into a blocked connection and a log line.
- Test your restores. Rank Math’s best recovery path depends on a backup from before October 15. If you have never restored one, you do not really know you have one.
Here is a hypothetical to show why order matters. An admin finds the fake core file, deletes it, and goes to lunch. The next visitor’s page load rebuilds it. That is the scenario Rank Math’s step order is meant to prevent. It is my illustration, not a reported case.
The Bottom Line
What is confirmed: Rank Math PRO 3.0.123, downloaded or updated during an eleven-hour window on October 15 and 16, could carry a backdoor that rebuilds itself. The fix is 3.0.124 plus a real cleanup. The free plugin was not affected. What is not known: how the attackers got in and how many sites were hit. Updates are still the right default. They just are not a substitute for watching what lands on your server.
