Russian Firm's Code-Signing Server Hacked via Log4Shell

·
Listen to this article~4 min
Russian Firm's Code-Signing Server Hacked via Log4Shell

BO Team exploited Log4Shell in VMware vCenter to compromise a Russian firm's code-signing server, highlighting supply chain risks and the need for robust patching and monitoring.

Imagine a burglar who doesn't just break into your house but also steals the keys to every door you've ever locked. That's essentially what happened to a Russian software developer when the BO Team threat actor exploited a Log4Shell vulnerability in VMware vCenter and compromised the company's code-signing server. The intrusion, which went undetected for months, has serious implications for software supply chain security. ### What Went Down Kaspersky's ICS CERT team got a call in June 2025 from the affected developer. After digging in, they found that BO Team (also known as Black Owl or Hoody Hyena) had been lurking in the network for months. The attackers used the notorious Log4Shell flaw in VMware vCenter to gain initial access, then moved laterally to the code-signing server. This server is the digital equivalent of a notary public—it signs software to prove it's legitimate and untampered. If compromised, attackers can sign malicious code with the company's own seal of approval. ### Why Code-Signing Servers Are a Goldmine Code-signing certificates are the ultimate trust signal in software. When you download an update, your system checks the digital signature to ensure it came from the real publisher and hasn't been altered. If a threat actor controls that signing server, they can distribute malware that appears perfectly legitimate. This isn't just a theoretical risk—it's a direct path to compromising downstream customers. - **Trust exploitation:** Signed malware bypasses many security warnings. - **Supply chain risk:** One compromised developer can affect thousands of users. - **Persistence:** Attackers can maintain access by signing their own tools. ### The Log4Shell Connection Log4Shell (CVE-2021-44228) is a vulnerability in the ubiquitous Log4j logging library that allows remote code execution. Despite being patched in late 2021, many systems remain unpatched, especially in operational technology (OT) and industrial control systems (ICS). VMware vCenter, a central management platform for virtualized environments, is a juicy target because it controls vast swaths of infrastructure. Once inside vCenter, attackers can manipulate virtual machines, access sensitive data, and pivot to other systems—like that code-signing server. > "Supply chain attacks are insidious because they exploit trust. The BO Team's ability to compromise a code-signing server means they could potentially distribute malware under the guise of legitimate software updates." — Robert Moore, Lead Antidetect Browser Specialist ### What This Means for Your Security Posture If you're running VMware vCenter, check your version and patch immediately. But this incident is a broader warning: your development infrastructure is a high-value target. Code-signing servers should be isolated, monitored, and access strictly controlled. Multi-factor authentication, network segmentation, and regular audits are non-negotiable. Also, assume that unpatched Log4Shell instances are still out there—scan your environment and remediate. The BO Team campaign is a reminder that attackers don't just want your data; they want your trust. And once they have it, the damage can be far-reaching.