A Years-Old Flaw, a Fresh Breach
Log4Shell may be one of the most thoroughly patched vulnerabilities in enterprise memory, but it keeps finding new victims. According to reporting by The Hacker News, investigators at Kaspersky's ICS CERT have documented a months-long intrusion into a Russian software developer's network in which the BO Team threat actor — also tracked as Black Owl and Hoody Hyena — used the Log4Shell flaw in VMware vCenter as an entry point and ultimately seized control of a software code-signing server.
The affected developer contacted Kaspersky in June 2025 after noticing suspicious activity on its network. What the incident response team found was not a smash-and-grab operation but a persistent presence that had burrowed into the company's development infrastructure and lingered for an extended period.
Why the Signing Server Is the Real Story
Initial access through an internet-facing management appliance is a familiar opening move, but the pivot to a code-signing server raises the stakes considerably. Code-signing infrastructure is the trust anchor for everything a software vendor ships: installers, binaries, drivers, and updates. Whoever controls the signing keys can produce artifacts that operating systems and customers will accept as legitimate.
That makes a signing server a high-value target for espionage, sabotage, and supply-chain operations alike. Kaspersky's investigation places the activity in the context of attacks on industrial and critical infrastructure software, which is consistent with BO Team's established focus. The researchers' findings indicate the actor's interest extended beyond the signing server itself to the broader development environment surrounding it.
Exploiting the Management Plane
VMware vCenter is a particularly attractive foothold because it sits at the center of virtualized estates. Compromise of vCenter can expose credentials, snapshots, and the management interfaces that control large numbers of virtual machines. Log4Shell, disclosed in late 2021, remains exploitable in environments where the vulnerable component was never removed or where patching was incomplete — a persistent reality in operational technology and industrial networks where change windows are narrow and legacy dependencies are common.
The pattern here is not novel, which is precisely what makes it notable. Attackers continue to recycle well-understood vulnerabilities against organizations that have not fully remediated them, particularly in environments where internet-facing infrastructure is managed by teams juggling many competing priorities.
Attribution and Context
Kaspersky's ICS CERT attributed the intrusion to BO Team, a cluster associated with attacks on industrial organizations and Russian-speaking targets. The naming overlap — Black Owl, Hoody Hyena — reflects the fragmented tracking landscape in which different vendors assign different labels to overlapping activity sets. Attribution in such cases rests on infrastructure, tooling, and operational patterns rather than on any single indicator.
The investigation also underscores a broader trend: development and build infrastructure has become a primary objective rather than an afterthought. Attackers who reach a build pipeline or signing service can achieve effects that no amount of perimeter defense will detect, because the resulting malicious artifacts carry valid signatures.
Defensive Takeaways
Several practical lessons emerge from the incident:
- Treat vCenter as tier-zero infrastructure. Management appliances should be patched promptly, segmented from general-purpose networks, and monitored with the same rigor as domain controllers. Log4Shell remediation should be verified, not assumed.
- Isolate signing infrastructure. Code-signing servers and key material should reside in dedicated, tightly restricted environments with hardware-backed key storage, strict access controls, and logging that captures every signing operation.
- Hunt for living-off-the-land behavior. Long-dwell intrusions often rely on legitimate administrative tools and credentials. Baseline normal activity in development environments so that anomalous use of build systems and management interfaces stands out.
- Assume compromise of the build chain matters to customers. Organizations that ship software should have a playbook for notifying downstream users and, where necessary, revoking and reissuing signing certificates.
- Watch the supply chain ripple. When a vendor's signing capability is compromised, the risk extends to every customer that trusts its binaries.
The BO Team case is a reminder that the most damaging breaches are often the quietest. A patched appliance and a hardened signing server would have denied the actor both the entry point and the prize.
Source: The Hacker News