Flitz.ai Flitz.ai

November 17, 2026

A 5-Year-Old VMware Bug Just Compromised an Entire Software Supply Chain

A vulnerability patched five years ago just caused one of the worst outcomes a software company can face: a complete takeover, from its virtualization layer all the way to the server that digitally si...

A 5-Year-Old VMware Bug Just Compromised an Entire Software Supply Chain

A vulnerability patched five years ago just caused one of the worst outcomes a software company can face: a complete takeover, from its virtualization layer all the way to the server that digitally signs its commercial software. Kaspersky's ICS CERT team has published details of how a threat actor known as BO Team (also tracked as Black Owl, Hoody Hyena, and Lifting Zmiy) exploited Log4Shell in an unpatched VMware vCenter server to pull it off.

What actually happened

According to The Hacker News, the affected developer contacted Kaspersky in June 2025 after noticing something was wrong. Investigators traced the intrusion back to a vCenter server running version 7.0.3, still vulnerable to CVE-2021-44228 — Log4Shell — a flaw that was headline news back in December 2021 and has had a patch available ever since.

Using that single unpatched server, the attackers obtained a remote command line with root privileges, connected to the underlying hypervisor over SSH, and mapped out every host they could reach. From there they planted a script on the hypervisor that ran every hour, quietly checking for a signal to download malware. The backdoor stayed dormant until the attackers flipped it on by changing a single DNS record — a trigger that is nearly invisible to normal monitoring.

From the compromised hypervisor, BO Team moved into the company's source code repositories and its Ansible automation system, using stolen secrets and a private key to go even deeper. Kaspersky's conclusion is the part that should worry every software vendor and every business that relies on one: the compromise of the CI/CD pipeline and the code-signing server meant this was heading toward a full supply-chain attack — malicious code signed with the victim's own legitimate certificate, ready to be trusted by its customers.

Why "already patched" five years ago doesn't mean "already safe"

Log4Shell is one of the most famous vulnerabilities of the last decade. Most organizations assume it was dealt with long ago. This case shows that assumption is often wrong — old flaws survive for years in management infrastructure like vCenter precisely because it's treated as "internal plumbing" that nobody revisits once it's running. As one security analysis put it, vCenter should never be reachable from a general-purpose terminal host in the first place — yet in many networks it still is.

What to do today

  • Check your VMware vCenter version now. If it's not on a currently supported, patched release, update it immediately — don't wait for a maintenance window.
  • Isolate vCenter and hypervisor management interfaces. They should sit on a restricted management network, not reachable from everyday staff laptops or general-purpose jump hosts.
  • Review SSH access to hypervisors. Disable it where it isn't actively needed, and log every session that does occur.
  • Audit scheduled tasks and cron-like scripts on hypervisors and servers. An hourly script checking an external signal is exactly the kind of thing that hides in plain sight for months.
  • Protect your code-signing keys and CI/CD secrets separately from general infrastructure, with their own access controls and monitoring, so a hypervisor breach can't cascade straight into your build pipeline.
  • If you're a software vendor, assume your customers are a target too. A signed update is only as trustworthy as the infrastructure that signed it.

The bigger picture

This isn't an isolated incident. It's part of a daily stream of vulnerabilities, exploit chains and automated attacks that businesses of every size now face — and old, "already handled" bugs are proving just as dangerous as brand-new ones. We're tracking this space closely and will keep reporting the threats that actually matter for Swiss businesses, along with the concrete steps to close the door before someone else walks through it.

Many Swiss SMEs simply don't have the time or in-house expertise to track patch levels across virtualization, networks and servers while also running the business. Flitz.ai helps Swiss companies automate and secure their IT operations so these checks don't get forgotten between projects — including security basics like endpoint protection, two-factor authentication and ongoing administration of your Microsoft 365 and Windows environment. If you're not sure whether your own virtualization layer is exposed, a free network analysis is a good place to start.

Limited spots available this week

Get a FREE consultation

Get a FREE 1 hour consultation about your current application management setup, development process or any other tech setup problem.