cPGuard update channel hijacked: a fake update ran as root on about 2,950 servers
OPSSHIELD, which makes security software for web hosting servers, said in a security advisory that the cPGuard update distribution channel was compromised on November 2, 2026 and a malicious script was pushed out as an update. Security press reports say the fake updates were served for about 70 minutes and ran as root on about 2,950 servers. The company advises moving to 5.88.25 or later; Help Net Security and CSO Online give 5.88.26.
A security product's own update channel became the attacker's delivery route
In its advisory, OPSSHIELD wrote that at 02:06 UTC on November 2 an attacker reached the update distribution CDN with compromised credentials and pushed a malicious script out as an update. Affected cPGuard versions run from 5.88.12 to 5.88.19. The company says it detected the incident within 12 hours.
According to SecurityWeek, Help Net Security and CSO Online, all dated November 4, the fake updates were served for about 70 minutes and about 2,950 servers installed the script and ran it as root. SecurityWeek presents that figure as an OPSSHIELD estimate, but it does not appear on the company's advisory page. The sources do not name the attacker.
Timeline, what was collected and what was done about it
Help Net Security reports that on November 1 the attacker registered under a false identity, ordered a free trial and studied the licensing communication. About an hour and a half later, crafted requests to billing portal callback pages gave command execution on the billing and licensing server. That step is not in the company advisory. Help Net Security says the fake updates were uploaded between 02:04 and 02:09 UTC on November 2 using a stolen update storage key, while the company speaks of compromised credentials. The entry point and how the key was obtained are still under investigation, so we go no further on cause.
The script collected password hashes (/etc/shadow), the user list, the MySQL root configuration, root shell history, and root SSH authorized_keys and known_hosts files. Help Net Security adds cloud storage keys. A hidden root shell was left at /var/tmp/.cpg91511_sh. By the company's preliminary estimate, the attacker retrieved 32 collected files, each corresponding to one customer server. The company says this is preliminary and not a count of all potentially affected servers.
Press reports say about 7,900 customer records (name, company, address, email, hashed password; Help Net Security says the hashes are bcrypt) were copied from the billing server, along with three OPSSHIELD cloud servers. The company advisory does not give those two figures.
For the fix, the company and SecurityWeek give 5.88.25 or later; Help Net Security and CSO Online name 5.88.26 as the release that removes the hidden root shell. Those two reports also describe a follow-up update that removes the scheduled task the attacker left (i93677 in Help Net Security). Per press reports, OPSSHIELD began re-issuing all cPGuard license key pairs, rotated related API keys and is rebuilding its billing and licensing servers. Customers are advised to rotate root and local passwords, SSH keys, database, S3 and DigitalOcean keys, and any secrets in shell history.
A trusted update channel can be an attacker's shortest path
Here the attack arrived as a normal-looking update from the security software already installed on the target servers. Because it ran as root, the most sensitive files on each server were in scope. Expert comments quoted by CSO Online also point to the fact that vendor agents run as root.
Two distinctions on scope. The 2,950 and 7,900 figures come from press reports and are not on the company's advisory page. And the entry point and how the key was taken remain open questions. Figures and details may change as the investigation moves on.
The sources do not mention Türkiye, so this section is commentary
None of the four sources mentions servers, hosting companies or businesses in Türkiye. This section is therefore not a fact; it is UNALSOFT commentary.
Our view: if your website runs on a hosting company's shared or managed server, you do not need to know whether cPGuard is installed there, but you can ask your hosting provider. The affected version range and the fixed version are in the advisory; how many servers in Türkiye were affected is something the sources do not tell us.
The UNALSOFT view
We design and build websites; auditing server security is outside this article and outside our scope here. The incident does have a plain lesson, though: keep a written record of which hosting your site runs on, who manages it, and who will tell you when a security notice arrives. In our web design and development projects we recommend keeping that information in the handover notes. This article is not an incident response guide; if you think you may be affected, rely on the OPSSHIELD advisory and your hosting provider.
Is your website's hosting and maintenance setup written down?
A short conversation is enough to review your hosting, maintenance and security-notice flow together.