---
title: Hunt: BO Team got from an SSH-exposed terminal server through Log4Shell on vCenter 7.0.3 to a developer's GitLab and code-signing server; check for an hourly 'pgcache' cron backdoor and nofrillsdns C2 | ctxsec
url: https://ctxsec.com/items/hunt-bo-team-black-owl-log4shell-vcenter-pgcache-cron-backdoor-code-signing-server-kaspersky
description: "Kaspersky ICS CERT describes a months-long intrusion it attributes to BO Team (Black Owl) at a software developer with Russian customers, found in June 2025. The attackers logged into a Linux terminal server over internet-exposed SSH, then exploited Log4Shell (CVE-2021-44228) on an unpatched VMware vCenter 7.0.3 for root, planted an hourly cron backdoor on hypervisors, and moved to GitLab, Ansible, the domain controller and the build-signing server. Kaspersky believes the aim was a supply-chain attack on the developer's customers; it says the attack was stopped and found no evidence that tampered software was released. After eviction, the attackers sent phishing that passed SPF and DKIM, suggesting they held the mail server's signing key."
status: "research (Kaspersky ICS CERT incident report, Nov 5, 2026); attribution is Kaspersky's; incident detected June 2025; hunt checks are ours"
published: 2026-11-16
---

> Kaspersky ICS CERT describes a months-long intrusion it attributes to BO Team (Black Owl) at a software developer with Russian customers, found in June 2025. The attackers logged into a Linux terminal server over internet-exposed SSH, then exploited Log4Shell (CVE-2021-44228) on an unpatched VMware vCenter 7.0.3 for root, planted an hourly cron backdoor on hypervisors, and moved to GitLab, Ansible, the domain controller and the build-signing server. Kaspersky believes the aim was a supply-chain attack on the developer's customers; it says the attack was stopped and found no evidence that tampered software was released. After eviction, the attackers sent phishing that passed SPF and DKIM, suggesting they held the mail server's signing key.

[← Threat Hunting](/hunting) · [markdown](/items/hunt-bo-team-black-owl-log4shell-vcenter-pgcache-cron-backdoor-code-signing-server-kaspersky.md)

research (Kaspersky ICS CERT incident report, Nov 5, 2026); attribution is Kaspersky's; incident detected June 2025; hunt checks are ours

2026-11-16 7:34 AM ET

### Hunt: BO Team got from an SSH-exposed terminal server through Log4Shell on vCenter 7.0.3 to a developer's GitLab and code-signing server; check for an hourly 'pgcache' cron backdoor and nofrillsdns C2

- **Patch debt:** confirm no vCenter still loads a Log4j vulnerable to CVE-2021-44228; Kaspersky reproduced the exploit on the same vCenter build.
- **Hypervisor persistence:** look for `/etc/cron.hourly/pgcache` or other cron.hourly scripts that curl and run remote content; Kaspersky's sample (MD5 `346b04985ec6c5d107ba0ddf32fe7691`) was timestomped to look like it dated from 2021.
- **Dormant C2:** DNS lookups for `*.nofrillsdns.com`, including hostnames that resolve to 127.0.0.1 until the operators switch them on. Also Global Socket (gsocket) use and ReverseSSH binaries.
- **Credential theft:** lsass dumps via `comsvcs.dll`, registry exports used to decrypt ntds.dit, a modified `/usr/bin/nxnode-login`, or files under `/dev/shm/pulse-shm-*`.
- **Infrastructure (per Kaspersky):** VPN logins from 193.3.23[.]236 and 80.76.42[.]139.
- **Build integrity:** limit and log who can reach the signing server, require approvals for signing, and rotate DKIM and signing keys after any domain-wide compromise.

Sources: [Kaspersky ICS CERT: Supply chain attack: BO Team in a software developer's infrastructure (Nov 5, 2026)](https://ics-cert.kaspersky.com/publications/reports/2026/11/05/supply-chain-attack-bo-team-in-a-software-developers-infrastructure/) · [The Hacker News: BO Team exploits Log4Shell in VMware vCenter (Nov 16, 2026)](https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html)
