---
id: "CMP-202611-osqbmj"
page: "https://infrastack.ai/live/CMP-202611-osqbmj"
kind: "campaign"
aliases: []
title: "BO Team hackers break into a Russian software developer through Log4Shell in an old VMware vCenter, backdoor the hypervisors and reach GitLab, Ansible and the code-signing server (Kaspersky)"
severity: "high"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "VMware vCenter Server", "fixed": [], "affected": "7.0.3 without Log4Shell fix", "ecosystem": "vendor"}, {"name": "VMware ESXi", "fixed": [], "affected": "", "ecosystem": "vendor"}, {"name": "GitLab", "fixed": [], "affected": "", "ecosystem": "vendor"}, {"name": "Ansible", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: []
tags: ["campaign", "early-warning"]
not_affected_if: []
published_at: null
first_seen_at: "2026-11-16T07:13:34+00:00"
updated_at: "2026-11-16T07:15:12+00:00"
sources: [{"source": "analyst", "url": "https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html", "first_seen_at": "2026-11-16T07:13:34+00:00", "cites": ["https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html"]}]
exploit_sources: []
---

# BO Team hackers break into a Russian software developer through Log4Shell in an old VMware vCenter, backdoor the hypervisors and reach GitLab, Ansible and the code-signing server (Kaspersky)

Link for people: https://infrastack.ai/live/CMP-202611-osqbmj (this .md is for agents)

Kaspersky ICS CERT describes a months-long break-in at an unnamed Russian software developer whose software is used by customers in Russia; the company called Kaspersky in June 2025. BO Team (also called Black Owl, Hoody Hyena, Lifting Zmiy; active since 2023, believed to be Ukrainian, targets Russian organisations) got in through an SSH service left open on a Linux terminal server. It then used Log4Shell (CVE-2021-44228) in VMware vCenter 7.0.3 to get root and SSH into the ESXi hypervisors. On the hypervisors it planted an hourly cron script named 'pgcache' that downloads GSocket remote access once the attacker changes a DNS record. From there it got into the GitLab VM and source code, the Ansible system, the domain controller (all domain passwords) and the server that signs the company's software builds, which points to a planned supply-chain attack or theft of the signing key. Kaspersky does not say any malicious signed build was shipped. After being thrown out, the attackers sent staff phishing emails at the end of July from the company's own mail server key, so the emails passed SPF and DKIM. Whether other companies were hit is unknown. The report is from 16 Nov 2026 and covers an intrusion in 2025.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:VMware vCenter Server affected 7.0.3 without Log4Shell fix fixed no fixed version listed
- vendor:VMware ESXi affected range not listed fixed no fixed version listed
- vendor:GitLab affected range not listed fixed no fixed version listed
- vendor:Ansible affected range not listed fixed no fixed version listed

## Cause

How the attacker got in: an internal system reachable from the internet (internal-exposed). BO Team got in through an SSH service left open on a Linux terminal server, and the later staff phishing emails were sent from the company's own mail server key, so they passed SPF and DKIM.

How it reached others: their users got messages abusing it (phishing).

So it does not happen to you: List internal apps with a public hostname and check none still accepts a development or default credential; make sure test environments cannot reach production.

Last month's incidents with the same cause, and the full checklist: https://infrastack.ai/live/breaches.md#phishing

## How to check

On ESXi/vCenter and Linux hosts: look for a file named 'pgcache' in /etc/cron.hourly/; DNS lookups or connections to *.nofrillsdns[.]com, in particular lo1yaizaeghaevarooD1ahtaichootae.nofrillsdns[.]com and lo1yaizaeghaevarood1ahtaichootaz.nofrillsdns[.]com; GSocket (gs-netcat) processes; a changed /usr/bin/nxnode-login (NoMachine) and the file /dev/shm/pulse-shm-3088612174. On Windows: lsass dumps made with comsvcs.dll, registry or ntds.dit dumps, cleared event logs. Email: phishing with subject 'Account disconnected from the mail server' that passes SPF/DKIM. Check whether any vCenter is still on 7.0.3 without the Log4Shell fix.

## Fix

Patch or retire vCenter builds still affected by Log4Shell (CVE-2021-44228) and keep vCenter and ESXi off networks users and jump hosts can reach. Do not expose SSH on terminal servers to the internet. If you find the indicators: treat the hypervisors, GitLab, Ansible and domain as compromised; rotate domain, admin and SSH keys, the mail server DKIM key and the code-signing key, and check recent signed builds against source. Use different admin passwords in each domain.

## Timeline

- 2026-11-16T07:13:34+00:00 analyst https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html

## Documents

- [describes] @TheHackersNews: 🚨 Hackers exploited Log4Shell in VMware vCenter to breach a Russian software dev https://x.com/TheHackersNews/status/2122221831893794898
- [describes] @TheHackersNews: The backdoor could be activated by changing a DNS record.

BO Team planted a scr https://x.com/TheHackersNews/status/2122222467175588003
- [describes] @TheHackersNews: One compromised hypervisor helped attackers reach source code repositories and t https://x.com/TheHackersNews/status/2122222434732609583
- [describes] BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html
- [discussion] @campuscodi.risky.biz: Russian security firm Kaspersky claims it spotted Ukrainian hacking group the BO https://bsky.app/profile/campuscodi.risky.biz/post/3mzsbsflqic2e

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
