Dear cPGuard customers and partners,
An unidentified attacker targeted OPSSHIELD, gained unauthorized access to our licensing and update systems, and distributed a malicious script through the cPGuard update channel. **We have stopped further distribution of the script and released cPGuard 5.88.25 to remove the known backdoor and files left by the script.**
The script sent data to an endpoint on our licensing server under a compromised account. We secured that account as soon as we identified the breach and cleared our infrastructure credentials. We are investigating how the attacker gained access, which customer servers ran the script, and what data the attacker accessed.
**Please take the following actions immediately.**
1. **Update every cPGuard server.** Run `cpgcli update --start`. The corrective update removes the backdoor shell at `/var/tmp/.cpg91511_sh` and the collection directory `/var/tmp/.cpg91511`, including the password hashes and credential archive (`loot.tgz`) staged there.
2. **Verify the installed version.** After the update completes, run `cpgcli --version` on each server and confirm it reports **5.88.25**. If the update fails or the server still reports an older version (between 5.88.12 and 5.88.19), contact OPSSHIELD Support immediately.
3. **If you know or suspect the malicious script ran, reset passwords and revoke exposed credentials.** The script targeted `/etc/shadow`. Reset passwords for root and all other password-enabled local accounts from a trusted recovery environment. From a trusted device, change any passwords reused elsewhere and rotate affected database passwords, S3 access keys, DigitalOcean tokens, and secrets recorded in root's shell history. Replace SSH private keys stored under `/root/.ssh` and remove the corresponding old public keys from every system that trusts them. Complete this step even if the update succeeds, because credentials copied before cleanup may still be usable.
We are sorry that this breach put your systems at risk. If you need help assessing a server, please contact OPSSHIELD Support through your usual support channel. We will share further findings as we verify them.
The OPSSHIELD Team
An unidentified attacker targeted OPSSHIELD, gained unauthorized access to our licensing and update systems, and distributed a malicious script through the cPGuard update channel. **We have stopped further distribution of the script and released cPGuard 5.88.25 to remove the known backdoor and files left by the script.**
The script sent data to an endpoint on our licensing server under a compromised account. We secured that account as soon as we identified the breach and cleared our infrastructure credentials. We are investigating how the attacker gained access, which customer servers ran the script, and what data the attacker accessed.
**Please take the following actions immediately.**
1. **Update every cPGuard server.** Run `cpgcli update --start`. The corrective update removes the backdoor shell at `/var/tmp/.cpg91511_sh` and the collection directory `/var/tmp/.cpg91511`, including the password hashes and credential archive (`loot.tgz`) staged there.
2. **Verify the installed version.** After the update completes, run `cpgcli --version` on each server and confirm it reports **5.88.25**. If the update fails or the server still reports an older version (between 5.88.12 and 5.88.19), contact OPSSHIELD Support immediately.
3. **If you know or suspect the malicious script ran, reset passwords and revoke exposed credentials.** The script targeted `/etc/shadow`. Reset passwords for root and all other password-enabled local accounts from a trusted recovery environment. From a trusted device, change any passwords reused elsewhere and rotate affected database passwords, S3 access keys, DigitalOcean tokens, and secrets recorded in root's shell history. Replace SSH private keys stored under `/root/.ssh` and remove the corresponding old public keys from every system that trusts them. Complete this step even if the update succeeds, because credentials copied before cleanup may still be usable.
We are sorry that this breach put your systems at risk. If you need help assessing a server, please contact OPSSHIELD Support through your usual support channel. We will share further findings as we verify them.
The OPSSHIELD Team
