NEWS

BO Team Exploits Log4Shell in VMware vCenter to Compromise a Russian Developer's Code-Signing Server

Kaspersky ICS CERT details a months-long BO Team intrusion at a Russian software developer, via Log4Shell on vCenter 7.0.3, aimed at its signing server.

Dylan H.

News Desk

November 16, 2026
3 min read
BO Team Exploits Log4Shell in VMware vCenter to Compromise a Russian Developer's Code-Signing Server

Summary

Kaspersky's ICS CERT published a report on November 5, 2026 describing a months-long compromise of an unnamed Russian software developer's network, including its CI/CD infrastructure and the server used to sign commercial software builds. The developer contacted Kaspersky in June 2025. The activity is attributed to BO Team (also tracked as Black Owl, Hoody Hyena and Lifting Zmiy), a group active since at least 2023 that focuses on espionage and hacktivism and is assessed to be of Ukrainian origin. Orange Cyberdefense contributed additional analysis.

Kaspersky believes the goal was a supply chain attack, possibly by stealing the code-signing certificate.

Attack Chain

  1. Initial access: an exposed SSH service on a Linux terminal server, used for internal reconnaissance.
  2. Log4Shell: a VMware vCenter 7.0.3 server was exploited through CVE-2021-44228, giving root command-line access.
  3. Persistence: an hourly cron backdoor named pgcache in /etc/cron.hourly/, disguised as a PostgreSQL component. It fetched scripts from nofrillsdns[.]com domains and used GSocket for remote control. The DNS record pointed at 127.0.0.1 until activation. A second virtualization cluster was backdoored using the compromised hypervisor's certificate.
  4. Lateral movement: the attackers reached the GitLab VM, source repositories and a private key, then the Ansible orchestration system.
  5. Credential theft: lsass.exe dumped with comsvcs.dll and Nanodump, ntds.dit extracted via the registry, and /usr/bin/nxnode-login modified to capture credentials. Reused administrator passwords across domains enabled domain-wide compromise, and one terminal server password fell after about 2,500 failed attempts.

Nearly all IT infrastructure was affected: Windows and Linux servers, hypervisors, backup servers, security management servers and network equipment.

After access was lost, the group ran a phishing campaign in late July that bypassed SPF and DKIM checks, suggesting it had obtained a mail server private key. It was detected and blocked.

Tooling

Mythic, Cobalt Strike, BrockenDoor, ZeronetKit, Nanodump, GSocket and an SSH-based ELF backdoor, plus living-off-the-land binaries, timestomping and log deletion.

Indicators

  • IPs: 193.3.23[.]236, 80.76.42[.]139 (Ukrainian provider)
  • Domains: nofrillsdns[.]com
  • File: /etc/cron.hourly/pgcache

Recommendations

Kaspersky's write-up as reported does not list formal remediation, but the lessons are clear:

  • Patch or remove Log4j from management software, including vCenter, and treat unsupported vCenter builds as urgent.
  • Do not expose SSH to the internet; restrict and monitor it.
  • Never reuse administrator passwords across domains.
  • Isolate code-signing servers and keys, and protect secrets stored on VMs and in CI/CD.
  • Hunt for unexpected cron entries, DNS records resolving to loopback, GSocket artifacts and credential-dumping activity.

Sources