Executive Summary
In a months-long intrusion beginning no later than mid-2024 and discovered in June 2025, the Ukrainian-linked threat actor BO Team (also known as Black Owl, Hoody Hyena, and Lifting Zmiy) compromised the entire IT infrastructure of an unnamed Russian software developer. Attackers gained an initial foothold via an exposed SSH service on a Linux terminal server, then pivoted to exploit CVE-2021-44228 (Log4Shell) in VMware vCenter 7.0.3, achieving root-level remote command execution. From there, they systematically breached GitLab repositories, Ansible orchestration systems, Active Directory domain controllers, and critically, a code-signing server used to authenticate commercial software builds—positioning the group for a downstream supply chain attack before rapid response measures severed their access.
This incident underscores a persistent and dangerous convergence of unpatched legacy vulnerabilities, overly flat internal network architectures, and high-value software supply chain targets. With Log4Shell now five years old yet still weaponized in active campaigns, and state-linked actors increasingly targeting development pipelines to reach downstream customers, organizations face compounding risk from both aging CVEs and sophisticated lateral movement tradecraft that deliberately avoids malware in favor of living-off-the-land techniques.
Why This Matters Now
Log4Shell (CVE-2021-44228) was disclosed in December 2021, yet BO Team exploited it in production VMware vCenter infrastructure in 2025—proof that critical vulnerability debt remains widespread and exploitable. Simultaneously, software supply chain attacks are accelerating globally, with regulators under frameworks such as NIST SSDF, EO 14028, and NIS2 demanding verifiable build integrity. Any organization running unpatched virtualization platforms or lacking east-west segmentation between development and production environments is exposed to identical attack chains today.
Attack Path Analysis
BO Team initiated the attack by exploiting an exposed SSH service on a Linux terminal server and subsequently leveraged Log4Shell (CVE-2021-44228) against an unpatched VMware vCenter 7.0.3 instance to obtain root-level remote code execution on the hypervisor. From there, the attackers escalated privileges across the entire Windows and Linux infrastructure by dumping LSASS memory, extracting NTDS.dit credentials, and abusing Kerberos tickets, before moving laterally through GitLab, Ansible, domain controllers, and ultimately the code-signing server. Throughout the campaign, BO Team maintained persistent command-and-control via GSocket backdoors triggered by dynamic DNS records, exfiltrated source code and credentials using SCP and living-off-the-land binaries, and positioned themselves to inject malicious code into signed software builds in a supply chain scenario that was disrupted only by rapid incident response.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
BO Team gained an initial foothold by exploiting an externally exposed SSH service on the organization's Linux terminal server, allowing unauthenticated remote access. The attackers subsequently identified and exploited CVE-2021-44228 (Log4Shell) in VMware vCenter Server 7.0.3, achieving a remote command execution with root privileges on the hypervisor. Reconnaissance of internal services (SMB, Kerberos, SSH, LDAP, WinRM) was conducted from the compromised terminal server. Inline IPS with up-to-date Suricata signatures for Log4Shell exploit patterns, combined with CNSF cloud-native enforcement at the network perimeter, could have detected and blocked the malicious JNDI callback payloads before the exploit chain completed.
Related CVEs
CVE-2021-44228
CVSS 10Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases) contains a remote code execution vulnerability via JNDI lookup features that allows an unauthenticated attacker to execute arbitrary code. Exploited in this incident against VMware vCenter Server 7.0.3 to obtain a remote command line with root privileges.
Affected Products:
Apache Log4j2 – 2.0-beta9 through 2.14.1
VMware vCenter Server – 7.0.3 and earlier affected builds
Exploit Status:
exploited in the wildReferences:
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Valid Accounts
OS Credential Dumping: LSASS Memory
OS Credential Dumping: NTDS
Scheduled Task/Job: Cron
Supply Chain Compromise: Compromise Software Supply Chain
Indicator Removal: Clear Windows Event Logs
Phishing: Spearphishing Link
Remote Services: SSH
Obtain Capabilities: Code Signing Certificates
System Binary Proxy Execution
Unsecured Credentials: Private Keys
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev. 5 – Flaw Remediation and Vulnerability Scanning
Control ID: SI-2 / RA-5
PCI DSS 4.0 – Security Patches and Vulnerability Management
Control ID: Requirement 6.3.3 / 11.3.2
DORA (EU) 2022/2554 – ICT Security and Patch Management / Vulnerability and Threat Management
Control ID: Article 9 / Article 10
NIS2 Directive (EU) 2022/2555 – Cybersecurity Risk Management — Incident Handling, Asset Management, and Supply Chain Security
Control ID: Article 21(2)(a)(b)(e)
CISA Zero Trust Maturity Model 2.0 – Least Privilege Access and Workload Integrity
Control ID: Identity Pillar — Pillar 2: Devices / Pillar 4: Applications & Workloads
ISO/IEC 27001:2022 – Management of Technical Vulnerabilities / Secure Development Lifecycle / Information Security in Supplier Relationships
Control ID: Annex A 8.8 / A 8.25 / A 5.23
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
BO Team's Log4Shell exploit compromised CI/CD pipelines, GitLab repositories, and code-signing servers, enabling supply-chain injection risk targeting downstream software customers via tampered signed builds.
Information Technology/IT
VMware vCenter exploitation, hypervisor backdoors, Active Directory credential dumping, and lateral movement across Windows and Linux infrastructure expose IT operations to full supply-chain and espionage compromise.
Computer/Network Security
Compromise of security solution management servers, timestomping, LotL evasion, and log deletion by BO Team directly undermines security tooling integrity, requiring zero-trust segmentation and east-west traffic controls per NIST.800-53.SC-7.
Defense/Space
BO Team's stated mission to degrade Russia's military-industrial complex makes defense-sector software supply chains critical targets for espionage, code-signing theft, and downstream customer compromise via validated CVE-2021-44228 exploitation.
Sources
- BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverhttps://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.htmlVerified
- Supply Chain Attack: BO Team in a Software Developer's Infrastructure - Kaspersky ICS CERThttps://ics-cert.kaspersky.com/publications/reports/2026/11/05/supply-chain-attack-bo-team-in-a-software-developers-infrastructure/Verified
- NVD - CVE-2021-44228 Detailhttps://nvd.nist.gov/vuln/detail/CVE-2021-44228Verified
- CISA Known Exploited Vulnerabilities Catalog - CVE-2021-44228https://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- VMware Security Advisory VMSA-2021-0028: VMware vCenter Server Log4Shellhttps://www.vmware.com/security/advisories/VMSA-2021-0028.htmlVerified
- Orange Cyberdefense - BO Team Group Intelligence Reporthttps://www.orangecyberdefense.com/fileadmin/global/CyberIntelligenceBureau/Gangs_Investigations/BOTeam/BO_TEAM_Group.pdfVerified
- Log4Shell Still Being Exploited to Hack VMware Horizon Servers - The Hacker Newshttps://thehackernews.com/2022/06/log4shell-still-being-exploited-to-hack.htmlVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant to this incident because BO Team's success depended on unrestricted lateral movement between hypervisor management planes, CI/CD systems, and Windows domain infrastructure — paths that segmentation-aware enforcement would likely have constrained. By reducing workload-to-workload reachability and controlling egress destinations, CNSF would likely have limited the blast radius before the supply chain signing server was reached.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: CNSF inline enforcement at the network perimeter would likely have reduced the reachability of the malicious JNDI callback traffic generated during the Log4Shell exploit chain, constraining the attacker's ability to complete the outbound callback necessary for remote code execution on the vCenter hypervisor.
Control: Zero Trust Segmentation
Mitigation: Zero Trust Segmentation enforcing least-privilege, identity-aware policies between the hypervisor management plane and domain controller access paths would likely have constrained credential reuse across administrative boundaries and reduced the scope of privilege escalation reachable from a single compromised hypervisor.
Control: East-West Traffic Security
Mitigation: East-West Traffic Security enforcing workload-to-workload segmentation policies would likely have limited the attacker's ability to freely pivot between hypervisor management planes, CI/CD infrastructure, and Windows domain controllers, reducing the number of reachable targets from any single compromised workload.
Control: Multicloud Visibility & Control
Mitigation: Centralized traffic observability through Multicloud Visibility and Control would likely have surfaced the anomalous DNS resolution patterns associated with nofrillsdns[.]com infrastructure, and FQDN-based egress filtering could have constrained outbound callback destinations to only approved domains, reducing the attacker's ability to maintain reliable C2 connectivity.
Control: Egress Security & Policy Enforcement
Mitigation: Egress Security and Policy Enforcement with FQDN filtering and anomalous outbound traffic detection would likely have constrained unauthorized SCP-based data transfers to non-approved external destinations, reducing the volume of source code and credential material that could have been successfully moved out of the environment.
Had prior CNSF controls constrained lateral movement and east-west reachability, the code-signing server and CI/CD pipeline would likely have remained outside the attacker's reachable scope, reducing the probability of a successful supply chain injection and limiting compromised asset exposure to earlier-stage infrastructure rather than the signing and build systems.
Impact at a Glance
Affected Business Functions
- Software Development CI/CD Pipeline Integrity
- Code-Signing Infrastructure and Release Management
- Active Directory and Identity Management Services
- Source Code Repository Confidentiality (GitLab)
Estimated downtime: 30 days
Estimated loss: N/A
Full compromise of software development infrastructure including: (1) source code repositories hosted on GitLab containing proprietary commercial software intellectual property; (2) credentials for all Active Directory domain users extracted from the ntds.dit database; (3) private keys of the GitLab server and mail server; (4) credentials of domain administrators and privileged users obtained via LSASS memory dumps and registry hive decryption; (5) code-signing certificate and private key of the software release signing server, enabling potential downstream supply chain compromise of the developer's customer base across the Russian Federation; (6) SSH private keys for Ansible orchestration systems providing lateral access to additional infrastructure. The theft of the code-signing key represents a critical long-term risk as it could be used to sign future malware with a trusted certificate.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy Inline IPS (Suricata) with current Log4Shell and JNDI exploit signatures at all ingress points to VMware vCenter and exposed management interfaces to block CVE-2021-44228 exploitation at the network layer before attacker payloads execute.
- • Enforce Zero Trust Segmentation with identity-based microsegmentation policies isolating the code-signing server, CI/CD infrastructure (GitLab, Ansible), and hypervisor management planes from general workload networks, ensuring lateral movement between these high-value assets requires explicit policy authorization.
- • Implement Egress Security & Policy Enforcement with FQDN-based filtering and outbound allow-listing to block backdoor callbacks to dynamic DNS services (nofrillsdns[.]com) and prevent unauthorized SCP/SSH-based data exfiltration to unapproved external destinations.
- • Activate Multicloud Visibility & Control with centralized traffic observability and anomaly baselining to detect hourly cron-triggered DNS resolution patterns, abnormal east-west credential traffic between hypervisors and domain controllers, and lateral movement using legitimate binaries across virtualization clusters.
- • Apply Encrypted Traffic (HPE) integrity monitoring on all data-in-transit paths between development infrastructure components and enforce Cloud Firewall (ACF) egress controls to detect and alert on anomalous outbound data volumes from code-signing and source code repository servers, limiting undetected exfiltration of intellectual property and signing credentials.



