AEGLIX News
OpsShield detected and stopped a supply-chain compromise of its cPGuard security plugin within 12 hours after attackers pushed malicious versions 5.88.12 through 5.88.19 starting November 2 at 02:06 UTC. The company said the attacker used legitimate credentials to gain initial access to its build or distribution pipeline, though how those credentials were obtained remains unclear. OpsShield identified 2,946 affected servers and confirmed its billing system database was also copied during the intrusion.
The compromised cPGuard releases were distributed through the legitimate autoupdate mechanism, meaning servers that checked for updates during the window automatically pulled the tainted packages. OpsShield noted that not every server necessarily executed the malicious payload because update checks run at specific intervals. The incident affected a range of versions rather than a single release, indicating the attacker maintained access to the publishing process across multiple builds.
Analysis of the malicious script shows it targeted Linux password hashes, root database configuration files for MariaDB and MySQL, root shell history, and root SSH authorization and known-hosts files. Stolen data was uploaded to OpsShield's own licensing server through a compromised account, which the threat actor then used to retrieve the collected files. While OpsShield has not determined exactly what data was taken from each individual server, investigative evidence indicates the attacker retrieved 32 files from every customer environment.
OpsShield urges administrators to update all cPGuard installations to version 5.88.25 or later, which removes the backdoor and any staged files. Because credentials were exfiltrated, the company advises immediately resetting passwords, rotating database credentials, cloud secrets, and SSH keys. As an additional precaution, OpsShield will release an update to remove previously installed OpsShield support-access keys. The company emphasizes that updating alone does not invalidate stolen credentials, which must be revoked separately.
Report prepared 2026-11-05 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)