Skip to content
feed: live
0dayNews
supply chain
● Breaking

BO Team Used Log4Shell to Breach a Russian Developer

Kaspersky ICS CERT says BO Team compromised a Russian software developer's CI/CD and code-signing server via an unpatched vCenter 7.0.3 and Log4Shell.

BO Team Used Log4Shell to Breach a Russian Developer
Photo: Zulfugar Karimov / Pexels · Pexels License
airgapMorgan "airgap" Reyes·Published ·2 min read

Confirmed: a months-long intrusion at a Russian software developer reached its CI/CD infrastructure and its code-signing server. Kaspersky’s ICS CERT documented the case, per The Hacker News report of November 16, 2026. The initial pivot into the hypervisor layer used Log4Shell (CVE-2021-44228) against a VMware vCenter server running version 7.0.3.

What was observed

  • The affected developer contacted Kaspersky in June 2025. The company is unnamed. It operates in Russia and has customers there.
  • Kaspersky attributes the activity to BO Team, also tracked as Black Owl, Hoody Hyena and Lifting Zmiy. Active since at least 2023. Assessed to be of Ukrainian origin.
  • Reported scope: Windows and Linux servers, workstations, hypervisors, backup servers, security management servers and network equipment.
  • Initial foothold: an exposed SSH service on a Linux terminal server, used for internal reconnaissance.
  • Logins to the vCenter web interface failed. A vCenter server vulnerable to Log4Shell gave the actor a root command line, then SSH access to the hypervisor.
  • Persistence: a script named “pgcache” placed in the hourly cron directory, styled to look like a PostgreSQL component. It fetched a second-stage script, which pulled the Global Socket (GSocket) utility for remote control.
  • Tooling attributed to the group generally: Mythic, Cobalt Strike, and its own malware BrockenDoor and ZeronetKit.

What was not observed

No data destruction. No public claim of responsibility, though the group usually posts on a dedicated Telegram channel and is known to deploy ransomware. Kaspersky says the actor focused on entrenching itself with backdoors and command channels.

Kaspersky assessed that access to the CI/CD and code-signing systems indicated the attack would likely develop into a supply chain scenario. No downstream compromise of the developer’s customers is reported. Confidence on that point: unconfirmed, and the source does not claim it.

Context

Log4Shell is a remote code execution flaw in Apache Log4j, disclosed in December 2021. See our Log4Shell explainer for the background. Exploitation against an unpatched vCenter here is a reminder that old, internet-reachable flaws in management infrastructure still convert to root.

Analysis: code-signing servers are valuable because trust attaches to what they sign. The source describes access to that server and a likely supply chain direction, not abuse of it. Treat any claim beyond that as unconfirmed.

Related coverage: DPRK npm Rollup polyfill supply chain campaign. More in the supply chain hub.

Primary source: The Hacker News, summarizing Kaspersky ICS CERT research and Orange Cyberdefense analysis of the group.

Related CVEs
  • [ CRITICAL ]CVE-2021-44228Log4Shell — Apache Log4j2 Remote Code Execution

More coverage: Apache

Found this useful? Share it.