BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
The BO Team exploited a vulnerability in VMware vCenter to compromise a Russian software developer's code-signing server, raising concerns about supply chain security.

A Russian software developer's network has been compromised for several months by the BO Team, who exploited a vulnerability in VMware vCenter to gain access to critical infrastructure and a code-signing server. This incident highlights the potential dangers of supply chain attacks.
An investigation into suspicious activity within a Russian software developer's network has revealed a prolonged compromise of its development infrastructure and software code-signing server. The activity was documented by Kaspersky's ICS CERT team after the affected developer reached out for assistance in June 2025. The threat actor, known as BO Team, has been linked to various cyber espionage and hacktivism efforts targeting Russian entities.
The intrusion, which lasted several months, resulted in the theft of confidential information and the compromise of the organization's entire IT infrastructure, including servers and workstations. Active since at least 2023, BO Team is believed to be of Ukrainian origin and has a history of targeting Russian interests to disrupt operations and gather sensitive data.
BO Team is known for using various tools, including Mythic and Cobalt Strike, alongside their own malware, such as BrockenDoor and ZeronetKit. While they have previously employed ransomware and publicized their activities, the attack on the software developer did not involve data destruction or public claims of responsibility. Instead, the attackers focused on establishing a foothold within the victim's network by creating command channels and backdoors for future access.
The attack began with the compromise of the organization's Linux terminal server, exploiting an exposed SSH service. This allowed the attackers to conduct reconnaissance on the internal network, identifying systems with accessible services like SMB, Kerberos, and HTTP. Although the attackers attempted to connect to various servers and services, they were initially unsuccessful in accessing the VMware vCenter web interface.
However, the threat actor successfully targeted a vulnerable VMware vCenter server, obtaining a remote command line with root privileges. They deployed a backdoor on the hypervisor, which was set to run every hour, disguised as a legitimate PostgreSQL component. This backdoor enabled them to download and execute a secondary shell script from a remote server, providing the attackers with remote control of the compromised host. The situation escalated as the attackers attempted to access a code-signing server, raising concerns about potential supply chain attacks.
- It is unclear how many systems were affected by the compromise or the extent of the data stolen.
- The specific motivations behind the attack on the software developer remain unconfirmed.
- Details regarding the next-stage payload that the attackers intended to deploy are not yet known.
What it meansA threat actor exploited a vulnerability in VMware vCenter to compromise a Russian software developer's code-signing server, indicating potential risks to supply chain security.
Ask IT this weekWhat vulnerabilities exist in our use of VMware vCenter? How are they being monitored?Which systems in our network are accessible via SSH, and are they adequately secured?
DecisionIT should conduct a thorough assessment of all systems for vulnerabilities and ensure that security measures are in place, with security verifying the results.