← BACK TO ALL INCIDENTS
CRITICAL

INCIDENT REPORT #001

Rank Math SEO PRO Supply-Chain Compromise: Malware Distributed in October 2026

A confirmed supply-chain compromise affected certain Rank Math SEO PRO 3.0.123 downloads distributed between 15 and 16 October 2026. Malicious plugin packages could establish persistent WordPress backdoors and expose sensitive credentials. A clean release is available, but previously compromised websites may require full incident recovery.

PUBLISHED
SEVERITY
CRITICAL
INCIDENT CLASS
CONFIRMED SUPPLY-CHAIN COMPROMISE / BACKDOOR DISTRIBUTION
STATUS
PUBLISHED

01 / OVERVIEW

Overview

A confirmed supply-chain compromise affected certain Rank Math SEO PRO 3.0.123 downloads distributed between 15 and 16 October 2026. Malicious plugin packages could establish persistent WordPress backdoors and expose sensitive credentials. A clean release is available, but previously compromised websites may require full incident recovery.

ENVIRONMENT
WordPress websites using Rank Math SEO PRO 3.0.123 downloaded or updated between 15–16 October 2026 (UTC).
INCIDENT CLASS
CONFIRMED SUPPLY-CHAIN COMPROMISE / BACKDOOR DISTRIBUTION
PROVENANCE
PUBLIC-SOURCE TECHNICAL ANALYSIS

02 / SITUATION

Situation

SITUATION

Between 15 October 2026 at 20:02 UTC and 16 October 2026 at 07:12 UTC, a subset of Rank Math SEO PRO version 3.0.123 packages distributed through the vendor's official infrastructure contained malicious code.

Rank Math publicly acknowledged the incident and confirmed that affected plugin packages could compromise WordPress websites if activated.

The incident represents a software supply-chain compromise rather than a conventional vulnerability exploited through an exposed WordPress endpoint.

Website owners who downloaded or updated Rank Math SEO PRO during the affected distribution window may have received a malicious package from a source they ordinarily trusted.

The compromised plugin code could establish persistent unauthorised access, create additional backdoors and expose sensitive credentials accessible to the WordPress environment.

Rank Math released a clean replacement, version 3.0.124, on 16 October 2026.

However, replacing the affected plugin does not automatically remove malicious files, administrator accounts or scheduled tasks previously introduced into the website or hosting environment.

The confirmed affected distribution window applies specifically to Rank Math SEO PRO. Rank Math states that the free Rank Math SEO plugin distributed through WordPress.org was not affected.

This report presents a public-source technical analysis of the disclosed incident. It does not represent a SecureMyWP customer investigation, a forensic examination of an affected website or an independently reproduced malware infection.

03 / WHAT WE FOUND

Findings

INCIDENT IDENTIFICATION

Product: Rank Math SEO PRO
Component: WordPress SEO plugin
Incident type: Software supply-chain compromise
Threat category: Embedded malicious code / persistent backdoor
CVE identifier: CVE-2026-111862
CVSS v3.1 severity: 9.8 — Critical
Affected release: Selected version 3.0.123 packages
Affected distribution period: 15 October 2026, 20:02 UTC, through 16 October 2026, 07:12 UTC
First clean replacement: Version 3.0.124

The version number alone does not establish compromise. Only packages obtained during the vendor-confirmed affected distribution window are implicated.

INITIAL COMPROMISE MECHANISM

The incident involved malicious code introduced into software distributed through the Rank Math PRO delivery infrastructure.

A website receiving and activating an affected package could execute malicious code within its WordPress environment.

Unlike an ordinary plugin vulnerability that requires attackers to exploit a particular HTTP endpoint, this incident relied on the installation or activation of a contaminated software package.

The available evidence confirms malicious distribution but does not establish every step by which the attacker gained access to the vendor's distribution environment.

MALWARE CAPABILITIES

According to the vendor's security advisory and corroborating security research, the malicious code could:

Establish persistent unauthorised access.

Create hidden PHP backdoors.

Recreate malicious backdoor components when the website receives visits.

Create unauthorised administrator accounts.

Modify files belonging to WordPress plugins or themes.

Introduce files masquerading as legitimate WordPress components.

Modify web server configuration to permit unexpected PHP execution.

Establish malicious scheduled tasks.

Access sensitive credentials and application secrets available to the compromised environment.

These capabilities create a risk of continuing compromise even after the affected plugin package has been replaced.

INDICATORS OF COMPROMISE

Network indicator:

rank1cdn[.]com

This domain was identified in the vendor's security guidance as associated with malicious communications.

WordPress database indicators:

Suspicious option_name values in the WordPress options table:

_uf6qdn2hmm

t8krdk990phb

_np5pvf754c

Administrator account indicators:

Unexpected administrator usernames beginning with:

wpsupport_

Suspicious administrator email addresses ending with:

@wp-mail[.]net

File-system indicators:

wp-includes/class-wp-cache-util.php

The vendor identifies this file as an illegitimate WordPress core component.

Additional suspicious PHP files may appear within:

wp-content/mu-plugins/

Other plugin directories

Non-default theme directories

Unexpected locations within the WordPress installation

Code-level indicators include suspicious combinations of:

base64_decode

XOR-based obfuscation

xmmqhn

proc_open

PHP-FPM socket interaction

Server configuration indicators:

Unexpected .htaccess directives permitting files with .cache extensions to execute as PHP.

Suspicious .cache files containing executable PHP code.

Scheduled task indicators:

System cron entries containing:

#ms6v46

Investigators should also examine unexpected SSH authorised keys, modified crontabs, suspicious processes and unusual files outside the WordPress document root.

These indicators should be evaluated in context. Individual function names are not proof of compromise, and the absence of known indicators does not establish that a website is clean.

POTENTIAL SECURITY IMPACT

A successfully compromised website may expose:

WordPress administrator credentials.

Database credentials.

Application configuration secrets.

API keys.

SMTP credentials.

Payment integration credentials.

Hosting or infrastructure access secrets.

Sensitive information accessible to the web server process.

The potential consequences include unauthorised administrative access, persistent malware infections, website manipulation, malicious redirects, data exposure and further compromise of connected systems.

These are potential consequences of the disclosed capabilities, not confirmation that every affected website experienced every outcome.

EVIDENCE ASSESSMENT

Rank Math directly confirmed the affected distribution period, acknowledged the presence of malware and published recovery instructions.

Wordfence independently documented the incident and associated indicators.

Patchstack registered the supply-chain compromise as CVE-2026-111862, classified the issue as a backdoor and recorded a CVSS severity score of 9.8.

The evidence supports high confidence that malicious plugin packages were distributed.

The reviewed public evidence does not establish a verified total number of compromised WordPress installations.

It also does not establish that widespread exploitation remains active as of this report's preparation.

The confirmed malicious distribution should therefore not be described as an ongoing mass-exploitation campaign without further evidence.

04 / WHAT WE DID

Actions taken

The following distinguishes confirmed vendor actions from recommended website recovery procedures. SecureMyWP has not performed customer remediation as part of this public-source report.

CONFIRMED VENDOR RESPONSE

Rank Math acknowledged the compromised plugin distribution.

The vendor removed the affected packages from distribution and released a clean replacement, Rank Math SEO PRO 3.0.124, on 16 October 2026.

Rank Math published instructions for affected customers, including website restoration, manual malware removal, credential rotation and subsequent security verification.

RECOMMENDED RESPONSE FOR POTENTIALLY AFFECTED WEBSITES

Establish the installation history.

Determine whether Rank Math SEO PRO 3.0.123 was downloaded, updated or activated during the confirmed affected distribution window.

Review plugin update records, backup records, hosting logs and any notification received from Rank Math.

Assess the potential exposure.

If a confirmed affected package was activated, follow the vendor's recommendation to treat the website as compromised.

If an affected package was installed but never activated, remove the affected files, install a clean release and perform precautionary scanning.

Downloading a package without installing or activating it does not, by itself, establish website compromise.

Preserve relevant evidence.

Before destructive cleanup, preserve available security logs, installation records, file metadata and other relevant evidence where practical.

Record suspected unauthorised administrator accounts, unexpected files and suspicious network activity.

Restore from a verified clean backup where available.

For websites that activated an affected package, Rank Math recommends restoring the website files and database from a backup created before 15 October 2026 at 20:02 UTC.

Verify that the selected backup is trustworthy and does not contain unrelated malicious changes.

Perform manual remediation where restoration is unavailable.

First disable the malware's persistence mechanism by removing the affected Rank Math PRO plugin directory, removing the malicious database options identified in the vendor advisory and blocking outgoing communication with rank1cdn[.]com where possible.

Then investigate and remove confirmed malicious files, unauthorised administrator accounts, malicious scheduled tasks and other attacker-created persistence mechanisms.

Examine changes outside the WordPress installation when the hosting environment permits.

Replace potentially exposed credentials.

Rotate relevant WordPress account passwords, database credentials, application secrets, API keys and service credentials accessible to the compromised environment.

Regenerate WordPress authentication keys and salts.

Review hosting credentials, SSH access and administrator two-factor authentication settings.

Install a clean Rank Math PRO release.

After recovery, install a clean vendor-provided release, version 3.0.124 or later.

Obtain the replacement directly through the official Rank Math account and download process.

Verify recovery.

Run comprehensive malware scans.

Verify WordPress core integrity.

Compare plugin and theme files against trustworthy sources.

Review administrator accounts, scheduled tasks, database entries and server configuration.

Monitor outgoing connections and confirm that removed malicious components do not reappear.

Escalate unresolved compromise.

If malicious files return, unexplained administrator access continues or the website cannot be reliably restored, engage the hosting provider or a qualified WordPress incident-response specialist.

Updating the plugin alone must not be considered evidence of successful incident recovery.

05 / OUTCOME

Outcome

Rank Math confirmed the removal of the affected plugin packages from distribution and released a clean replacement on 16 October 2026.

As of 11 November 2026, the vendor's published changelog also lists Rank Math SEO PRO version 3.0.125, following the initial clean release.

The known malicious distribution event has therefore been addressed at the software-package level.

However, this does not establish that every website that previously activated a contaminated package has been successfully recovered.

Persistent backdoors, unauthorised accounts, malicious scheduled tasks and exposed credentials may require additional investigation and remediation.

The reviewed public evidence does not provide a verified total of successfully compromised websites or establish ongoing mass exploitation.

SecureMyWP assesses the incident as a confirmed, critical supply-chain compromise with potentially persistent consequences for affected WordPress installations.

Website owners who activated a confirmed affected package should follow the vendor's full incident-recovery guidance rather than relying solely on a plugin update.

VERIFIED OUTCOME RECORDED See report text above for the governed outcome statement.

06 / HARDENING

Hardening and prevention

WordPress administrators should maintain a controlled plugin update and software verification process, particularly for premium plugins distributed outside the official WordPress.org repository.

Recommended preventative controls include:

Maintain frequent, independently stored backups of website files and databases.

Regularly test restoration procedures to confirm that backups can support incident recovery.

Keep WordPress core, plugins and themes updated using trusted distribution channels.

Track security advisories and vendor notifications for installed software.

Maintain an accurate inventory of installed plugins, their versions and update history.

Restrict administrator privileges and remove unnecessary privileged accounts.

Enable multi-factor authentication for administrative and hosting accounts wherever supported.

Protect application secrets, database credentials and infrastructure access keys.

Monitor unexpected PHP files, modified WordPress components, suspicious scheduled tasks and newly created administrator accounts.

Where operationally practical, restrict unexpected outbound network connections and prevent PHP execution in directories that should contain only uploaded media.

Use file-integrity monitoring and reputable malware detection tools to identify unauthorised changes.

Maintain an incident-response procedure for situations where a legitimate software update introduces malicious code.

This incident demonstrates that installing software from an ordinarily trusted vendor does not eliminate supply-chain risk.

Preventative controls reduce exposure and improve detection, but no single control guarantees protection against a compromised software distribution process.

07 / REPORT GOVERNANCE

Report governance

This public report is shown only because it satisfies SecureMyWP's governed publication requirements.

PROVENANCE
PUBLIC-SOURCE TECHNICAL ANALYSIS
PUBLISHED
11 NOV 2026
PUBLIC STATUS
PUBLISHED

24/7 EMERGENCY REQUEST INTAKE

Need urgent help? Submit an emergency request 24/7.

Tell us what's happening and we'll review the incident as quickly as operational capacity allows.

GET HELP NOW

SECUREMYWP // SECURITY ASSURANCE

WORDPRESSSPECIALISTS
SECUREACCESS
24/7 EMERGENCYINTAKE
30-DAY RE-CLEANWARRANTY

PROFESSIONAL WORDPRESS INCIDENT RESPONSE & REMEDIATION