← Voltar ao feed

cPGuard supply-chain attack backdoored about 2,950 Linux servers and exposed 7,900 OPSSHIELD customer records

4 fonte(s) · 4 atualização(ões) · publicado 03/11/2026 12:16 · coletado há 16 horas

Matéria consolidada. Reúne 5 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 4 fontes trouxeram em 05/11/2026 00:01; os links antigos trazem para cá.

Fontes: helpnetsecurity.com ↗ securityweek.com ↗ bleepingcomputer.com ↗ thehackernews.com ↗

Attackers compromised the billing, licensing and update infrastructure of cPGuard, a Linux server security suite made by OPSSHIELD (also written OpsShield, an Indian IT security firm), and on November 2, 2026 (02:06 UTC per thehackernews.com, bleepingcomputer.com) pushed a malicious script to customers running versions 5.88.12 through 5.88.19. The script ran as root, installed a hidden root shell and exfiltrated sensitive files to a compromised account on OPSSHIELD's licensing server. OpsShield told BleepingComputer that 2,946 servers were affected (bleepingcomputer.com); SecurityWeek and Help Net Security round this to about 2,950 (securityweek.com, helpnetsecurity.com). The same intrusion exposed roughly 7,900 customer account records (names, company, addresses, emails and hashed passwords) from the billing database, and the attacker cloned three of OPSSHIELD's cloud servers (securityweek.com, helpnetsecurity.com). The malicious updates were served for roughly 70 minutes, and the vendor detected the attack and halted distribution within 12 hours. OPSSHIELD revoked infrastructure credentials, secured the licensing account, reissued all cPGuard license key pairs and released a clean update (5.88.25 per most sources, 5.88.26 or later per helpnetsecurity.com). OPSSHIELD says the attack went from reconnaissance to full compromise in about ten hours and attributes that speed to the attacker's use of AI tooling (helpnetsecurity.com). The exact initial access vector into the billing/licensing server is still undetermined, and the attacker is unidentified. Stolen credentials remain valid until rotated.

Entenda a falha

A vulnerabilidade

No CVE is assigned. The attacker got remote command execution on OPSSHIELD's billing and licensing server through crafted requests to the billing portal's callback pages. The articles do not name the exact flaw or say whether it needs authentication, but the attacker had registered a free trial account beforehand. They then obtained an update-storage access key and uploaded fake cPGuard updates, versions 5.88.12 to 5.88.19, which ran as root on about 2,950 customer servers. The clean versions are 5.88.25 or later per most sources, or 5.88.26 or later per Help Net Security.

Como funciona

The attacker first installed a free cPGuard trial to study how the agent talks to the licensing system. About an hour and a half later, crafted requests hit the billing portal's callback pages, and minutes later they could run commands on the billing and licensing server and copy customer records. With an update-storage key they uploaded fake updates. Because cPGuard agents check for updates at intervals, each agent that polled during the window of roughly 70 minutes downloaded the fake update and ran it as root. The short script collected sensitive files, sent them to OPSSHIELD's own compromised licensing server under a compromised account, and left a hidden root shell.

Por que é vulnerável

The articles give no root cause for the billing server flaw. OPSSHIELD says its logs do not record the request that gave access, so it is reviewing the code and has patched two possible entry points. How the attacker obtained the update-storage key is also undetermined. The supply-chain impact came from agents running whatever was in update storage as root, so anyone holding the upload key could push code to all customers. The articles do not describe signature checks on updates. OPSSHIELD is hardening its update and signing process and rebuilding servers with tighter PHP and web firewall settings and full request logging.

Onde está

The articles point only to the billing portal's callback pages; no file, function or commit is named for the flaw.

Como foi descoberta

The articles do not say how the compromise was first detected, only that OPSSHIELD detected it and halted distribution within 12 hours. The fake updates were uploaded on November 2, 2026, between 02:04 and 02:09 UTC. OPSSHIELD published an incident notice and updated reports, which are the source of the timeline. It attributes the roughly ten-hour path from first probe to fake update to the attacker's use of AI tools. The investigation continues, the initial vector is undetermined, and IOCs have been published.

Explicação gerada por IA a partir da matéria e dos artigos, em 05/11/2026 00:17.

Detalhes técnicos

  • Attack chain reported by OPSSHIELD: the attacker registered a free cPGuard trial account to study the agent-to-licensing communication protocol, then sent crafted requests to the billing portal's callback pages to gain remote command execution on the billing/licensing server and copy customer records (securityweek.com, helpnetsecurity.com). They then obtained an update-storage access key and uploaded fake cPGuard updates that ran as root on any server polling the update infrastructure (securityweek.com, helpnetsecurity.com).
  • OPSSHIELD has ruled out SSH, control panel, FTP and API tokens as entry points, but the exact initial access vector into the billing/licensing server remains undetermined (helpnetsecurity.com). An earlier report described compromised credentials of unknown origin used on the update distribution CDN to disguise the payload as a legitimate update (bleepingcomputer.com).
  • cPGuard is used alongside cPanel, DirectAdmin and Plesk and is offered by hosts such as Namecheap (bleepingcomputer.com).
  • The malicious script was cpguard-v58812-i91511.sh. It dropped a backdoor shell at /var/tmp/.cpg91511_sh and staged loot in /var/tmp/.cpg91511/loot.tgz before uploading it to the licensing server (thehackernews.com). Help Net Security reports the hidden root shell at /var/tmp/.cpg91511_sh with supporting files in /var/tmp/.i93677/ (helpnetsecurity.com).
  • Targeted data: /etc/shadow, /etc/passwd, MariaDB/MySQL configuration files and root passwords, root's shell history, SSH authorization and known-hosts files, root SSH keys, and cloud storage keys (thehackernews.com, bleepingcomputer.com, helpnetsecurity.com). About 32 files were pulled from compromised customer servers (securityweek.com).
  • The stolen customer records from the billing database comprise names, company, addresses and emails, plus hashed passwords (bcrypt-hashed per helpnetsecurity.com), for about 7,900 customers (securityweek.com, helpnetsecurity.com). Three OPSSHIELD cloud servers were cloned (securityweek.com, helpnetsecurity.com).
  • The attackers then accessed the licensing server to retrieve the exfiltrated files (bleepingcomputer.com).
  • Some servers may have escaped infection because of update-check timing intervals (bleepingcomputer.com).
  • To check exposure, run grep 'Successfully updated' /opt/cpguard/logs/install_log. A clean log does not prove the script did not run, and updating removes the backdoor files but not evidence of earlier execution (thehackernews.com).

Remediação

  • Run cpgcli update --start and confirm cpgcli --version reports 5.88.25 or later (thehackernews.com, bleepingcomputer.com). Help Net Security advises v5.88.26 or later and verifying removal of the malicious scheduled task and the hidden root shell (helpnetsecurity.com).
  • On servers that ran or may have run the script, treat all password hashes, root SSH keys, MySQL root passwords and shell history as compromised (securityweek.com). Reset root and local account passwords from a trusted recovery environment (thehackernews.com, helpnetsecurity.com).
  • Rotate database passwords, S3 keys, DigitalOcean tokens and any secrets in shell history or /root/.s3cfg (thehackernews.com, helpnetsecurity.com). Rotate cloud secrets and SSH keys generally (bleepingcomputer.com).
  • Replace SSH private keys under /root/.ssh and remove the corresponding public keys elsewhere (thehackernews.com, helpnetsecurity.com).
  • Reset the OPSSHIELD billing portal password and enable two-factor authentication. This applies even to customers whose servers were offline during the attack window (securityweek.com, helpnetsecurity.com).
  • Customers confirmed to have had attacker interactive access should rebuild from a clean backup predating November 1 (helpnetsecurity.com). For other cases the vendor recommends contacting its support team for case-by-case review rather than a blanket OS rebuild (thehackernews.com).
  • OPSSHIELD is issuing a separate update to strip its support-access SSH keys from customer servers as a precaution (thehackernews.com, bleepingcomputer.com).
  • Vendor-side actions: attackers evicted, secrets rotated, attacker SSH keys and cloned cloud assets removed, all cPGuard license key pairs reissued, billing portal sessions and API keys reset, and billing, licensing and internal management servers being rebuilt. IOCs have been published (securityweek.com, helpnetsecurity.com).

Relatos divergentes

  • Scale and file count: thehackernews.com (earlier) says OPSSHIELD estimates 32 files were exfiltrated from affected customer servers and that the figure may still change. bleepingcomputer.com says 32 files were stolen per customer on average and gives a total of 2,946 affected servers. securityweek.com and helpnetsecurity.com (latest) say about 2,950 servers, which is consistent with the BleepingComputer figure as a rounding. The exact BleepingComputer number, which cites the vendor directly, is the more specific one. The total number of files is not stated.
  • Compromised component and initial access: thehackernews.com describes the update infrastructure and credentials generally. bleepingcomputer.com specifies stolen legitimate credentials used on the update distribution CDN. The more recent securityweek.com and helpnetsecurity.com, relaying OPSSHIELD's findings, describe remote command execution on the billing/licensing server via billing portal callback pages, followed by theft of an update-storage access key. helpnetsecurity.com adds that the exact initial vector remains undetermined. The later accounts are more detailed and likely more authoritative.
  • Fixed version: thehackernews.com and bleepingcomputer.com give 5.88.25 as the clean version. helpnetsecurity.com (more recent) says to update to 5.88.26 or later. Updating to the latest available release satisfies both.
  • Artifact paths: thehackernews.com reports staging in /var/tmp/.cpg91511/loot.tgz. helpnetsecurity.com reports supporting files in /var/tmp/.i93677/. Both sources agree on the hidden shell at /var/tmp/.cpg91511_sh. Check for both directories.
  • Billing database: bleepingcomputer.com reported that OpsShield's billing database was copied, and thehackernews.com does not mention it. securityweek.com and helpnetsecurity.com (more recent) confirm the theft of about 7,900 customer records.

Linha do tempo

  1. helpnetsecurity.com ↗ · pub. 04/11/2026 08:18 · coletado 04/11 09:00

    Supply-Chain Attack on cPGuard Update Infrastructure Compromises ~2,950 Web Hosting Servers

    ler a análise desta fonte

    OPSShield, maker of the Linux web hosting security suite cPGuard, suffered a supply-chain compromise in which an attacker hijacked its update infrastructure and pushed malicious updates (versions 5.88.12–5.88.19) to roughly 2,950 customer servers as root on November 2, 2026. The attacker also breached OPSShield's billing and licensing server, stealing contact information and bcrypt-hashed passwords for about 7,900 customers, and cloned three of the company's cloud servers. The attack chain moved from initial reconnaissance to full compromise in roughly ten hours, which OPSShield attributes to attacker use of AI tooling to accelerate discovery and exploitation. OPSShield has released clean updates, rotated credentials and keys, and published remediation guidance and IOCs for affected customers.

    Technical Details

    The attacker first registered a fake trial account on OPSShield's billing portal to study agent-to-licensing communication, then exploited the billing portal's callback pages to gain remote command execution on the billing/licensing server, from which they exfiltrated customer records. They subsequently obtained an update-storage access key and uploaded fake cPGuard updates that ran as root on customer servers for over 70 minutes, collecting password hashes, root SSH keys, MySQL root passwords, root shell history, and cloud storage keys, exfiltrating them to OPSShield's own compromised licensing server. The malicious payload left a hidden root shell at /var/tmp/.cpg91511_sh with supporting files in /var/tmp/.i93677/. The exact initial access vector into the billing/licensing server remains undetermined; OPSShield has ruled out SSH, control panel, FTP, and API tokens as entry points.

    Remediation

    Affected customers should update to cPGuard v5.88.26 or later, verify removal of the malicious scheduled task and hidden root shell, reset root and local Linux account passwords from a trusted recovery environment, rotate database passwords, S3/DigitalOcean keys and any credentials found in root's shell history or /root/.s3cfg, replace SSH private keys under /root/.ssh, reset OPSShield billing portal passwords, and enable two-factor authentication. Customers confirmed to have had attacker interactive access should rebuild from a clean backup predating November 1. OPSShield has published IOCs and offered remediation assistance.

  2. securityweek.com ↗ · pub. 04/11/2026 07:54 · coletado 04/11 09:00

    OpsShield Supply Chain Attack Serves Malicious cPGuard Updates to ~2,950 Servers, Exposes 7,900 Customer Records

    ler a análise desta fonte

    OpsShield, an Indian IT security firm behind the cPGuard server protection product for Linux web hosting, suffered a supply chain attack in which attackers compromised its billing/licensing infrastructure and pushed malicious updates through the cPGuard CDN. The malicious code was embedded in cPGuard versions 5.88.12–5.88.19 and distributed for roughly 70 minutes before detection within 12 hours. OpsShield estimates about 2,950 servers executed the fake update, and attackers exfiltrated roughly 7,900 client account records (names, company, addresses, emails, hashed passwords) along with 32 files pulled from compromised customer servers. The attackers also deployed a hidden root shell and additional files on affected customer servers and cloned three of OpsShield's cloud servers.

    Technical Details

    The attackers first used a free cPGuard trial to study the licensing/billing portal's communication protocol, then sent crafted requests to gain command execution on the billing and licensing server. Using a stolen access key, they uploaded a malicious update script that ran as root on any server polling OpsShield's update infrastructure during the compromise window. The script collected data and exfiltrated it back to OpsShield's licensing server via a compromised account, while also installing a hidden root shell and dropping files into the temp folder on infected customer servers.

    Remediation

    OpsShield states that all password hashes, root SSH keys, MySQL root passwords, and shell history on infected servers should be considered compromised and rotated. Customers whose servers were not online during the attack window should still reset their billing portal password. OpsShield evicted attackers from affected systems, rotated secrets, removed attacker SSH keys and cloned cloud assets, replaced SSH keys/passwords, reissued all cPGuard license key pairs, reset billing portal sessions and API keys, and is rebuilding its billing, licensing, and internal management servers. A clean update (version 5.88.25 and later) was released to remove the hidden root shell and dropped files, and IoCs were published.

  3. bleepingcomputer.com ↗ · pub. 03/11/2026 19:18 · coletado 03/11 21:00

    cPGuard Update Infrastructure Hijacked to Push Backdoor, Steal SSH/DB Credentials from ~2,946 Servers

    ler a análise desta fonte

    Attackers compromised OpsShield's update distribution CDN for cPGuard, a Linux web-server security suite used alongside cPanel, DirectAdmin, and Plesk, and widely offered by hosts like Namecheap. Using stolen legitimate credentials, the attacker pushed a malicious script via the cPGuard update channel on November 2, 2026 at 02:06 UTC, affecting versions 5.88.12 through 5.88.19. The script harvested root MariaDB/MySQL configuration and root SSH authorization/known-hosts files, exfiltrating the data through a compromised account on OpsShield's licensing server. OpsShield confirmed to BleepingComputer that 2,946 servers were affected, with 32 files stolen per customer on average, and that its own billing database was also copied.

    Technical Details

    The attacker gained unauthorized access to OpsShield's CDN using compromised credentials (origin unknown) and used it to distribute a backdoor and data-stealing script disguised as a legitimate cPGuard update. The malicious payload targeted root-level database configuration and SSH credentials, uploading stolen data to OpsShield's own licensing server infrastructure, which the attackers then accessed to retrieve the exfiltrated files. OpsShield detected and halted the malicious distribution within 12 hours, though some servers may have avoided infection due to update-check timing intervals.

    Remediation

    OpsShield urges all customers to update cPGuard to version 5.88.25 or later, which removes the backdoor and staged malicious files, and to immediately reset passwords and rotate database credentials, cloud secrets, and SSH keys, since stolen credentials remain valid until invalidated. The vendor also plans to release an additional update removing previously installed OpsShield support-access keys as a further precaution.

  4. thehackernews.com ↗ · pub. 03/11/2026 12:16 · coletado 03/11 14:00 primeiro registro

    cPGuard Update Channel Hijacked to Deploy Backdoor and Steal Password Hashes from Linux Servers

    ler a análise desta fonte

    An unidentified attacker compromised the update infrastructure of cPGuard, a Linux security tool made by OPSSHIELD, and used compromised credentials to push a malicious script to customers via versions 5.88.12 through 5.88.19, released starting November 2, 2026 at 02:06 UTC. The script installed a backdoor and exfiltrated /etc/shadow, /etc/passwd, MariaDB/MySQL configuration files, root's shell history, and SSH authorization/known-hosts files to an OPSSHIELD-run licensing server using a compromised account. OPSSHIELD detected the attack within 12 hours, revoked infrastructure credentials, secured the licensing account, and released version 5.88.25 to remove the backdoor and collected files, though stolen credentials may still be valid. OPSSHIELD estimates 32 files were exfiltrated from affected customer servers, a number that may still change, and is still investigating the initial access vector.

    Technical Details

    The malicious script (cpguard-v58812-i91511.sh) dropped a backdoor shell at /var/tmp/.cpg91511_sh and staged stolen data in /var/tmp/.cpg91511/loot.tgz before uploading it to OPSSHIELD's licensing server. Admins can check exposure by running grep 'Successfully updated' /opt/cpguard/logs/install_log to identify affected versions, though a clean log does not guarantee the script did not run, and removal of the backdoor files by updating does not erase evidence it previously executed.

    Remediation

    OPSSHIELD urges all cPGuard admins to run cpgcli update --start and verify cpgcli --version reports 5.88.25 or later. For servers that ran or may have run the script, admins should reset root and local account passwords from a trusted recovery environment, rotate database passwords, S3 keys, DigitalOcean tokens, and any secrets in shell history, and replace SSH private keys under /root/.ssh while removing corresponding public keys elsewhere. OPSSHIELD is also issuing a separate update to strip its support-access SSH keys from customer servers as a precaution, and recommends contacting its support team for case-by-case review rather than a blanket OS rebuild.