Incidents

cPGuard Supply Chain Attack: Hijacked Update Stole Server Credentials, Admins Must Rotate Passwords and Keys

OPSSHIELD confirms cPGuard's update channel was hijacked to push a data-stealing script to Linux servers. Patching alone won't revoke stolen credentials.

cPGuard Supply Chain Attack: Hijacked Update Stole Server Credentials, Admins Must Rotate Passwords and Keys

On November 3, OPSSHIELD disclosed that attackers had compromised the infrastructure used to deliver cPGuard updates. Some servers got a script that harvested sensitive files instead of a security software update. Administrators should update the software and rotate any credentials the attacker may have obtained.

What the vendor found

According to OPSSHIELD’s latest notice, the attacker got into the company’s billing and licensing infrastructure and used a stolen key to publish a fake update. The malicious code reached customer servers on November 2. The incident was disclosed publicly the next day.

The script ran with root privileges. Among other things, it copied password hashes for local accounts, the root user’s SSH files, MySQL credentials and command history. Command history matters because it may contain passwords and tokens the administrator typed in earlier. The vendor also confirmed that its own billing system had been breached.

The updated notice adds to the earlier findings. It names version 5.88.26 as the clean release and gives detailed guidance on removing leftover artifacts. Use the vendor’s current instructions when assessing a server, because the described scope of the incident changed as the investigation went on.

What to do now

Recommended steps for administrators:

  • Install the latest version of cPGuard and check for the indicators of compromise listed by OPSSHIELD.
  • Change the passwords for root, local accounts and any databases reachable from the server.
  • Generate new SSH keys and revoke the old ones on every other machine that accepted them.
  • Replace any tokens and keys found in command history or configuration files.
  • Reset your password for the OPSSHIELD billing portal and turn on two-factor authentication.

Before you clean anything up, preserve logs and copies of suspicious files for analysis. Updating the software does not take back the credentials the attacker has already copied. You also need to check every machine the compromised SSH keys could reach.

SecurHUB’s take

When a security vendor is breached, you have to check the affected server and also every system it connects to. Incident response can cover forensic analysis of the intrusion, scoping the breach and organizing credential rotation.

Sources: OPSSHIELD, BleepingComputer

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk