# SZB-1abe8912cb: Kaspersky reports BO Team exploited Log4Shell in VMware vCenter during intrusion at a Russian developer

Kaspersky's ICS CERT documented a months-long compromise of an unnamed Russian software developer's network, including theft of confidential information and a code-signing server.

- Type: Breach
- Status: Confirmed
- Vendor: VMware
- Product: vCenter Server
- Disclosed: 2026-11-16 06:53 UTC
- Way in: Exploited vulnerability (The Hacker News: “However, the threat actor managed to successfully target a VMware vCenter server (version 7.0.3) vulnerable to CVE-2021-44228 (aka Log4Shell and LogJam), obtai…”, [source](https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html))
- Attacker: BO Team (The Hacker News: “The activity, documented by Kaspersky's ICS CERT team after it was contacted by the affected developer in June 2025, has been attributed to a threat actor name…”, [source](https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html))
- Sources: 1 distinct
- First seen by cve.now: 2026-11-16 07:48 UTC · Updated: 2026-11-16 07:50 UTC

Written by a model from the sources below. Verify against them.

## Summary

Kaspersky says the attackers gained root access to a vCenter 7.0.3 server through the Log4Shell flaw (CVE-2021-44228) and planted a backdoor on the hypervisor.

## What to do

- Upgrade vCenter Server or apply the vendor's Log4j fixes so the Log4Shell flaw (CVE-2021-44228) is no longer present.
- Search hypervisors for the hourly cron script named "pgcache" in /etc/cron.hourly/ and remove any unauthorized backdoor.
- Rotate credentials for vCenter, hypervisor SSH access and any accounts that touched the affected systems.
- Verify the integrity of code-signing servers and CI/CD infrastructure before signing new releases.

## Timeline

- 2026-11-16 06:53 UTC: Made public by The Hacker News
- 2026-11-16 07:48 UTC: First seen by cve.now
- 2026-11-16 07:48 UTC: Confirmed as CVE-2021-44228

## Exploited CVEs

- [CVE-2021-44228](https://cve.now/CVE-2021-44228.md): Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints

## Evidence (1 source)

- 2026-11-16 · Press · [The Hacker News](https://thehackernews.com/2026/11/bo-team-exploits-log4shell-in-vmware.html): “However, the threat actor managed to successfully target a VMware vCenter server (version 7.0.3) vulnerable to CVE-2021-44228 (aka Log4Shell and LogJam), obtain a remote command line with root privileges, connect to the hypervisor over SSH, and identify accessible hosts.”

## Corrections

None so far.

Something wrong on this page? Report an error: https://github.com/sazabi/cve.now/issues/new?title=Wrong%20fact%20on%20SZB-1abe8912cb&body=https%3A%2F%2Fcve.now%2FSZB-1abe8912cb%0A%0AWhat%20is%20wrong%2C%20and%20the%20source%20that%20shows%20it%3A%0A

## Questions about the VMware breach

### Was VMware breached?

Yes. Confirmed as CVE-2021-44228.

### What should VMware customers do?

Upgrade vCenter Server or apply the vendor's Log4j fixes so the Log4Shell flaw (CVE-2021-44228) is no longer present. Search hypervisors for the hourly cron script named "pgcache" in /etc/cron.hourly/ and remove any unauthorized backdoor. Rotate credentials for vCenter, hypervisor SSH access and any accounts that touched the affected systems. Verify the integrity of code-signing servers and CI/CD infrastructure before signing new releases.

## Related

- Started as early warning SZB-1abe8912cb, first seen 2026-11-16 07:48 UTC
- Browse: [Breaches](https://cve.now/breaches.md) · [Early warnings](https://cve.now/early-warnings.md)

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/SZB-1abe8912cb
Site guide for agents: https://cve.now/llms.txt

## Public exploit activity: CVE-2021-44228

Public data from PoC-in-GitHub and FIRST EPSS. From 2026-08-20 to 2026-11-17: GitHub PoC repos rose from 446 to 509; EPSS held at 100.0%.

| Date | GitHub PoC repos | EPSS |
| --- | --- | --- |
| 2026-08-20 | 446 |  |
| 2026-09-01 | 447 |  |
| 2026-09-06 | 448 |  |
| 2026-09-07 | 449 |  |
| 2026-09-14 | 450 |  |
| 2026-09-18 | 451 |  |
| 2026-09-26 | 452 |  |
| 2026-09-27 | 453 |  |
| 2026-10-08 | 455 |  |
| 2026-10-09 | 456 |  |
| 2026-10-10 | 457 |  |
| 2026-10-17 | 457 | 100.0% |
| 2026-10-19 | 458 | 100.0% |
| 2026-10-20 | 459 | 100.0% |
| 2026-10-21 | 461 | 100.0% |
| 2026-10-22 | 465 | 100.0% |
| 2026-10-23 | 467 | 100.0% |
| 2026-10-24 | 468 | 100.0% |
| 2026-10-25 | 469 | 100.0% |
| 2026-10-27 | 471 | 100.0% |
| 2026-10-28 | 472 | 100.0% |
| 2026-10-29 | 481 | 100.0% |
| 2026-11-01 | 504 | 100.0% |
| 2026-11-02 | 506 | 100.0% |
| 2026-11-05 | 507 | 100.0% |
| 2026-11-12 | 508 | 100.0% |
| 2026-11-14 | 509 | 100.0% |
| 2026-11-17 | 509 |  |
