العربية
🚨 BreakingSonicWall Gen 6 Firewalls Reach End of Security Patches

BO Team Exploits Log4Shell in vCenter to Reach Code-Signing Server

فريق السايبر العربياقرأ بالعربية

Kaspersky ICS CERT says BO Team spent months inside a Russian software developer, using Log4Shell on an old vCenter to reach CI/CD and the code-signing server, likely staging a supply chain attack.

Source image for: BO Team Exploits Log4Shell in vCenter to Reach Code-Signing Server
Image: The Hacker News

⚡ Why it matters

Access to CI/CD and a code-signing server lets attackers ship signed malicious updates, and a five-year-old bug was enough to get in.

Kaspersky's ICS CERT team has published findings from an investigation into a Russian software developer whose development infrastructure and code-signing server were compromised over several months. The unnamed company contacted Kaspersky in June 2025.

Who is BO Team

Kaspersky attributes the intrusion to BO Team, also tracked as Black Owl, Hoody Hyena and Lifting Zmiy. As The Hacker News notes, the group has been active since at least 2023 in espionage and hacktivism against Russian targets and is assessed to be of Ukrainian origin. It uses Mythic and Cobalt Strike alongside its own BrockenDoor and ZeronetKit malware.

Unlike its earlier operations, this one involved no data destruction or public claims. The attackers focused on persistence and backup access, and Kaspersky says the compromise of CI/CD and code signing suggests a likely supply chain follow-up.

Attack chain

  • Initial access came through an exposed SSH service on a Linux terminal server, which was then used to scan the internal network.
  • Logins to the VMware vCenter web interface failed, but the attackers exploited Log4Shell (CVE-2021-44228) on a vCenter 7.0.3 server and obtained a root shell.
  • They reached the hypervisor over SSH and planted an hourly cron script named pgcache, disguised as a PostgreSQL component.
  • The script fetches the Global Socket (GSocket) tool for remote control and relies on a free DNS service, so flipping a DNS record activates the backdoor.

The operation ended with confidential data stolen and nearly every part of the IT estate compromised, including Windows and Linux servers, workstations, hypervisors, backup servers and network gear.

Recommendations

  • Move to a supported VMware vCenter release that fixes CVE-2021-44228, and audit for any remaining systems vulnerable to Log4Shell.
  • Do not expose SSH to the internet without restrictions; use key-based authentication plus MFA.
  • Isolate code-signing servers and CI/CD from the rest of the network and keep signing keys in an HSM.
  • Monitor cron jobs on hypervisors and servers, and watch DNS lookups to free dynamic DNS domains.

🔗 Sources

This article is original reporting by the Security World editorial team based on the sources listed above; direct quotes are kept short and marked with quotation marks. Corrections and feedback: info [at] securitywd.net.

Related stories