Advisory · Supply chain · CVE-2026-111862

Rank Math SEO PRO 3.0.123 malware: how to check and clean a site

For eleven hours on 15 and 16 October 2026, Rank Math’s own download channel served copies of Rank Math SEO PRO 3.0.123 that contained malware. The version number alone proves nothing: a package obtained before or after the window is clean. A site where an affected copy was installed and activated has to be treated as compromised, because the loader rebuilds its backdoors on every visit and 3.0.124 does not remove them.

First published in the weekly briefing of 19 October 2026 and moved here unchanged, so the indicators and the cleanup order have a page of their own.

Affected
Rank Math SEO PRO 3.0.123 downloaded between 20:02 UTC on 15 October and 07:12 UTC on 16 October 2026
Fixed in
3.0.124, which stops the plugin carrying the loader and removes nothing already planted
Leaves behind
Hidden PHP backdoors, administrator accounts, a fake Core file, a system cron entry and .htaccess rules
Preferred fix
Restore from before 20:02 UTC on 15 October, per Rank Math; otherwise the ordered manual cleanup

Supply chain · CVE-2026-111862

Rank Math SEO PRO 3.0.123: a vendor update that carried malware

Rank Math’s advisory says that “a limited number of users” who downloaded Rank Math SEO PRO 3.0.123 between 20:02 UTC on 15 October and 07:12 UTC on 16 October received plugin files containing malware. That is the vendor’s own distribution channel, so the affected copies arrived through ordinary downloads and automatic updates. Rank Math removed the files and published 3.0.124 as the clean release. Wordfence assigned the incident CVE-2026-111862 and scored it 9.8. Rank Math has not said how many sites were affected, who was behind it, or how the malicious build entered distribution. The free Rank Math SEO plugin on WordPress.org is not part of the advisory.

The version number alone proves nothing. A 3.0.123 package obtained before the window is clean, and so is one obtained after it. Rank Math sorts sites into three groups. A site where an affected copy was installed and activated must be treated as compromised. A site where it was installed but never activated should delete the plugin files, install 3.0.124 from the Rank Math account and run a scan as a precaution. A site that only downloaded the package, without installing or activating it, has no indication of compromise from this incident alone. If Rank Math has contacted you directly, follow its instructions whatever version the site runs now.

What the malware does, according to Rank Math and Wordfence: it establishes persistent access and contacts the domain rank1cdn.com; it recreates hidden PHP backdoors whenever the site is visited, so removing a file while the loader remains brings the file back; it creates administrator accounts; it drops a fake Core file in wp-includes; it adds .htaccess rules that let .cache files run as PHP; it adds cron entries at system level, outside WordPress; and it exposes everything the web server can read, which includes the database credentials and salts in wp-config.php, API keys, and payment and mail credentials. The PHP it writes uses base64_decode with XOR loops, proc_open, and PHP-FPM socket code.

Figure 1 · At a glance

The version number proves nothing. The download window does.

QuestionAnswer
Affected copies3.0.123 downloaded 20:02 UTC 15 October to 07:12 UTC 16 October 2026
Installed and activatedTreat the site as compromised
3.0.124Stops the plugin carrying the loader; removes nothing already planted
Look forrank1cdn.com, wpsupport_ administrators, wp-includes/class-wp-cache-util.php, cron marker #ms6v46
Preferred fixA restore from before 20:02 UTC on 15 October
The points that decide what to do about the malicious Rank Math SEO PRO 3.0.123 package, as stated in the sections below.

Supply chain · what to check

How to tell whether a site ran the malicious package

Run these checks on every site that had Rank Math SEO PRO 3.0.123 installed, including sites already on 3.0.124, unless you can prove the package was obtained outside the window. The indicators come from Rank Math’s advisory and Wordfence’s analysis. Preserve anything you find before removing it.

IndicatorWhere to lookWhat it means
Outbound connections to rank1cdn.comFirewall and proxy logs, outbound connection monitoring on the hostThe loader is calling its command server; a strong sign the site is live-infected
Options _uf6qdn2hmm, t8krdk990phb and _np5pvf754cThe wp_options table, queried directlyThe malware’s state; it uses these to rebuild its backdoors
Administrators named wpsupport_ followed by random characters, or any account with an @wp-mail.net addresswp user list --role=administrator, and the wp_users tableAn account the malware created
wp-includes/class-wp-cache-util.phpThe WordPress Core directory; wp core verify-checksums flags itA fake Core file; WordPress ships no file of this name
PHP files in wp-content/mu-plugins, in wp-content/uploads, in other plugins’ folders, in the inc, includes or lib folders of non-default themes, or in Rank Math’s own includes folderThe file system, by content rather than by dateDropped backdoors; the loader recreates them, so finding one is not the end of the search
Code containing the string xmmqhn, proc_open, XOR loops over base64_decode output, or PHP-FPM socket codeAny PHP file on the siteThe malware’s own code patterns
.htaccess rules that treat .cache files as PHP, and .cache files that contain PHPThe site root and every subdirectoryA way to run backdoors through a file extension scanners skip
A cron entry carrying the marker #ms6v46The system crontab of the web server or account user, not the WordPress cronPersistence outside WordPress; survives a plugin reinstall and a database restore
Unexpected entries in ~/.ssh/authorized_keys, unknown processes, writable paths outside the document rootThe hosting account and the serverServer-level persistence; at this point the question is wider than one site

Supply chain · cleanup

Cleaning a site that activated the malicious package

Rank Math’s recommended order, condensed. The order matters because the loader rebuilds whatever is removed while it still runs. Isolate the site and keep a snapshot before any of this.

  1. 01

    Restore from before the window if you can

    A full restore of files and database from a backup taken before 20:02 UTC on 15 October is Rank Math’s preferred route. Then scan, rotate credentials as in step five, and install 3.0.124 downloaded by logging in at rankmath.com. Rank Math says it never sends login or download links by email.

  2. 02

    Otherwise, disable the rebuild mechanism first

    Delete the whole rank-math-pro folder; deactivating is not enough. Delete the three options from wp_options. Block outbound connections to rank1cdn.com at the host or firewall if you can. Do not start removing backdoors until all three are done, or they come back.

  3. 03

    Then remove what it left

    Search for the indicators above. Remove unknown administrators, the fake Core file, the .htaccess rules and .cache files, the system cron entry, and PHP in uploads and mu-plugins. Reinstall WordPress Core, plugins and themes from official sources rather than deleting files one by one.

  4. 04

    Look beyond the site

    Review authorized_keys for SSH, the crontabs of other system users, running processes, and writable locations outside the document root. The malware ran as the site’s user and could reach anything that user could.

  5. 05

    Rotate every credential the site could read

    WordPress passwords, the database password in wp-config.php, the authentication keys and salts, API keys, payment gateway and SMTP credentials, and the cPanel, FTP, SFTP and SSH logins. Rank Math calls this essential even after a restore. Re-check two-factor authentication on administrator accounts.

  6. 06

    Verify, then keep watching

    Verify Core and every plugin that has public checksums, and review the scheduled events:

    WP-CLI
    wp core verify-checksums
    wp plugin verify-checksums --all
    wp cron event list

    Compare premium plugins, which have no public checksums, against a fresh download from the vendor. Watch outbound connections for several days; if a removed file reappears, the cleanup missed a layer.

Common questions

Common questions about the Rank Math SEO PRO incident

My site runs Rank Math SEO PRO 3.0.123. Is it infected?

Not necessarily. Only some packages served between 20:02 UTC on 15 October and 07:12 UTC on 16 October carried the malware. If the plugin was downloaded or auto-updated in that window and then activated, treat the site as compromised. If it was obtained outside the window, or installed but never activated, delete the plugin files, install 3.0.124 from your Rank Math account and scan. If you cannot establish when it arrived, run the indicator checks above.

I already updated to 3.0.124. Am I done?

No, if a malicious copy was ever activated. The update replaces the plugin; it does not remove the backdoors the loader rebuilt on every visit, the administrator it created, the system cron entry, the .htaccess rule, or the secrets it read. Rank Math’s own guidance is a restore from before the window or a cleanup in the order given above, followed by rotating every credential.

Why delete the plugin folder before cleaning anything else?

Because the loader inside it recreates the other backdoors whenever the site is visited. Remove the backdoors first and they come back; remove the plugin folder, the three options and the outbound connection first, and the rest stays removed. Deactivating the plugin leaves its files on disk and is not enough.

Choose the response path

The site ran the malicious Rank Math package: choose the response path.

One site, one worrying result

Get the finding classified and the site restored to a trusted state.

Best when a Rank Math SEO PRO site shows rank1cdn.com traffic, a wpsupport_ administrator or the #ms6v46 cron marker, or an exploited plugin left an account you did not create, and you want every layer removed in one pass rather than one at a time.

The server under the sites

Check what the malware could reach, and what the kernel still exposes.

Best when a compromised site shared a server with others, cron and SSH keys need reviewing across accounts, or you need a clear answer on PwnEscape exposure and ModSecurity state across several hosts.