BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
- ID
- 46932
- Status
- summarized
- Published
- 16 Nov 2026, 2:53 PM
- Fetched
- 16 Nov 2026, 4:14 PM
- Provider
- The Hacker News
- Category
- security
- Original URL
- https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html
- Source URL
- https://feeds.feedburner.com/TheHackersNews
Summary
- Score
- 3.0
- Created
- 16 Nov 2026, 4:15 PM
- Tags
- Audience
- developers
What happened
The Hacker News headline reports that a group tracked as "BO Team" exploited Log4Shell (the long-patched 2021 JNDI flaw in Log4j) inside VMware vCenter to compromise a Russian company's code-signing server. The supplied page text is almost entirely site navigation and boilerplate — it contains no CVE identifier, affected vCenter version, intrusion timeline, victim name, or detail on what was signed with the stolen keys.
Why it matters
The one actionable signal is that Log4Shell — a flaw with fixes available since late 2021 — is still being used as an entry point into vCenter, which means management-plane appliances are the unpatched gap. If you run vCenter, check its build/patch level this week, and check whether your code-signing keys or build pipeline are reachable from the same network segment as your hypervisor management interfaces. Beyond that, this excerpt gives you nothing to act on: no versions, no indicators, no victim detail.
Discussion angle
Why does a 2021 vulnerability keep working in 2026 — is it patch lag on appliances teams treat as 'set and forget', or is it that nobody owns the management plane? And separately: if your code-signing keys sit on a box reachable from vCenter, what does that chain of trust actually look like?