BO Team Uses Log4Shell to Breach VMware vCenter, Compromise Code-Signing Server
Threat actors exploited the Log4Shell vulnerability in VMware vCenter to gain access to a Russian firm's development infrastructure. The breach led to unauthorized control of a critical code-signing server used for authenticating software.
TL;DR
- BO Team exploited Log4Shell in VMware vCenter to infiltrate a Russian software firm.
- Attackers maintained persistent access for months, targeting development systems.
- A code-signing server was compromised, risking trusted software distribution.
- Kaspersky's ICS CERT identified the breach during a forensic investigation.
- Organizations should audit legacy systems for unpatched vulnerabilities like Log4Shell.
In a sophisticated cyberattack, the threat group known as BO Team leveraged the infamous Log4Shell vulnerability to penetrate VMware vCenter servers belonging to a Russian software developer. The breach, which went undetected for months, ultimately gave attackers access to sensitive internal systems, including a critical code-signing server.
The incident came to light following an internal investigation initiated by the affected company, which later collaborated with Kaspersky's ICS CERT team to analyze the scope of the compromise. This case highlights the ongoing risks posed by unpatched vulnerabilities in enterprise software environments, even years after initial disclosure.
Attack Vector and Initial Access
- BO Team exploited CVE-2021-44228 (Log4Shell) in VMware vCenter to gain remote code execution.
- Initial compromise occurred in late 2024, allowing lateral movement within the network.
- Attackers targeted development infrastructure, indicating strategic intent to disrupt software integrity.
Impact on Development Infrastructure
- Months-long persistence enabled full control over internal systems.
- A code-signing server was breached, potentially allowing malicious binaries to appear legitimate.
- Kaspersky confirmed that stolen certificates were not used to sign malware at the time of reporting.
Lessons for Security Teams
- Legacy vulnerabilities like Log4Shell remain high-value targets for advanced threat actors.
- Code-signing infrastructure requires strict access controls and continuous monitoring.
- Prompt patching and asset inventory are essential to reduce exposure to known exploits.
Sources
Sources
Security email updates
One digest email when we publish new security articles (TL;DR plus links to read more). Unsubscribe anytime from the message footer. See our Privacy Policy.