IPS Signature Nov 20, 2026

GajShield Threat Advisory — BO Team Supply-Chain Intrusion via Log4Shell in VMware vCenter (pgcache, GSocket and ReverseSSH Backdoors)

Severity: High | Priority: 1

The attackers got in through an exposed SSH service. They then exploited the Log4Shell vulnerability (CVE-2021-44228) in an unpatched VMware vCenter server to gain root. From there they spread through the environment, compromising hypervisors, domain controllers, GitLab, Ansible and the server used to sign the company’s software. Kaspersky assesses that the goal was a supply-chain attack on the developer’s customers. The intrusion was stopped before any malicious release was confirmed.

The attackers relied on persistence that looks like routine system maintenance. They placed an hourly cron script named pgcache, disguised as a PostgreSQL component, on the hypervisor. It stays dormant until the attackers change a DNS record, then downloads and runs further scripts. Those scripts installed the GSocket remote-access tool with a preset key. A second cron script posing as a VMware time-sync job decrypts and runs a ReverseSSH backdoor entirely in memory, connecting out over port 443. The attackers also backdated file timestamps and deleted log entries to hide their activity.

Patch or retire any system in your network still vulnerable to Log4Shell, VMware vCenter in particular. Don’t expose SSH or management interfaces to the internet. Check Linux servers and hypervisors for unexpected scripts in /etc/cron.hourly, especially files named pgcache or 1vmware-timesync. Also look for /usr/bin/vmware-toolbox-setdate and unexpected files under /dev/shm. If you find signs of compromise, treat CI/CD, source repositories and code-signing systems as exposed. Rotate signing keys and administrator credentials, and check recent software builds before releasing them to customers.

See the latest threat intelligence