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

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

BO Team gained initial access by exploiting an exposed SSH service on a Linux terminal server, then used CVE-2021-44228 (Log4Shell) in an unpatched VMware vCenter 7.0.3 instance to obtain a root-level remote shell, enabling deep lateral movement across the entire infrastructure.

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.

Initial Compromise

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.

Privilege Escalation

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.

Lateral Movement

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.

Command & Control

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.

Exfiltration

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.

Impact (Mitigations)

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)
Operational Disruption

Estimated downtime: 30 days

Financial Impact

Estimated loss: N/A

Data Exposure

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

  • • 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.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image