In 30 seconds

Kaspersky's ICS CERT has documented a months-long break-in at a Russian software developer. As reported, the attackers exploited Log4Shell, a years-old bug in the widely used Log4j logging code, inside the company's VMware vCenter virtualization platform, took root-level control, and worked their way to the machine that digitally signs its software.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
The researchers attribute the whole operation to a crew they track as BO Team, also known as Black Owl and Hoody Hyena. That attribution is an assessment by Kaspersky, not an established fact about who was actually at the keyboards.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source list
What happened
The case became visible in June 2025, when the developer contacted Kaspersky's ICS CERT about suspicious activity on its network. Once the investigators dug in, they concluded the intruders had been inside for months before that call.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source list
The way in, as documented, was Log4Shell in VMware vCenter, the software that manages a company's virtual machines. Exploiting it handed the attackers root access to the hypervisor, the host system underneath those machines, where they planted backdoors.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
From that perch they grabbed secrets and a private key, the credentials that prove identity inside a company's systems, and used them to reach the developer's source code repositories and its Ansible automation setup.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
To keep the door open, they installed a script on the hypervisor that ran every hour and waited for a signal. Changing one DNS record was enough to tell it to fetch malware, and the reporting says this scheme is how they maintained access and evaded detection.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Why it matters
The most alarming detail is the code-signing server. Signing is how a vendor cryptographically vouches that a file really came from them, so a signing machine under attacker control is exactly what fuels fears of a supply chain attack: customers could be tricked into installing poisoned updates that look perfectly legitimate.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Source code plus stolen keys is a potent combination. Whoever holds a vendor's code and the credentials that authenticate its releases has the raw material for a convincing trojanized version, and the Ansible access means the automation that pushes changes across infrastructure was exposed too.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listBO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source list
What to do
Customers of the affected developer have an obvious first move: review any binaries and updates signed by the company, and press the vendor for details of its response. To be clear, nothing in the available evidence shows that a tampered, signed file was actually shipped to anyone.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
For everyone else the lesson is unglamorous. Log4Shell was made public in December 2021 and it still worked here, which argues for a fresh audit of vCenter servers and any other internet-facing system running vulnerable versions of Log4j.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Confirmed and still uncertain
What the investigation reportedly established: the intrusion happened, it ran for months, it entered through Log4Shell in vCenter, and it reached the development infrastructure, the source code repositories, the Ansible system, and the code-signing server.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
What remains open: the developer is never named in this reporting, so nobody outside the case can tell which products or customers sit in the blast radius. There is no evidence yet that signed malware was distributed, and the true identity behind the BO Team label rests entirely on Kaspersky's attribution.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
What people are saying
Kaspersky's ICS CERT is the voice behind the technical record. Its investigation, summarized by The Hacker News, pins the operation on BO Team, a group also tracked as Black Owl and Hoody Hyena.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source list
The Hacker News is also the main amplifier, framing the compromised signing server as a potential software supply chain incident and warning that the developer's customers have reason for concern about its signed software.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Evolution
The story grew in two directions. In June 2025 it looked like a live investigation into suspicious activity; by the time Kaspersky's team finished, the timeline had stretched back months and the scope had widened from a single hypervisor to the heart of the development pipeline.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source list
The final piece of the narrative was the persistence layer: the hourly script on the hypervisor with its DNS-record trigger, which explained how the intruders held their position for so long while evading detection.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Reach
2 independent groups, 3 updates, and 17 engagements.
Technical detail
Initial access: Log4Shell, the remote code execution flaw in Apache Log4j, exploited against VMware vCenter. The payoff was root access on the virtualization host and a set of planted backdoors.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source listBO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source list
Movement sideways depended on stolen credentials, including a private key, which let the attackers authenticate into the source code repositories and the Ansible system rather than break in all over again.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Persistence ran on a schedule. An hourly script on the hypervisor polled for a change in a DNS record, and when that record flipped, it downloaded malware. Waking the backdoor took nothing more than an edit to DNS, keeping the trigger far from the victim's own network.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Sources and evidence
This write-up rests on a thin but consistent base: one primary article from The Hacker News published on 16 November 2026, plus three posts from the outlet's X account summarizing the same findings. The underlying Kaspersky ICS CERT report is not part of this evidence batch.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source listTheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list
Everything about BO Team's responsibility comes from Kaspersky's attribution as relayed by that article. The victim appears only as an unnamed Russian software developer, and no statement from the company or independent corroboration from another research team appears in the batch.BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rssOpen original sourceSee in source list
Sources
- BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Serverthehackernews.com · rss
- TheHackersNewsx.com · TheHackersNews · x
- TheHackersNewsx.com · TheHackersNews · x
- TheHackersNewsx.com · TheHackersNews · x



