The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

Log4Shell Let BO Team Reach Code-Signing Server

By aminah ·16 Nov 2026 ·4 min read
Rows of server racks with dense network cabling in a data centre

A threat actor known as BO Team used the Log4Shell vulnerability in an unpatched VMware vCenter server to break into a Russian software developer and reach the server used to sign its software, according to an investigation by Kaspersky's ICS CERT team published on 5 November 2026 and reported on 16 November.

The developer, whose name was not disclosed, contacted Kaspersky in June 2025 after spotting suspicious activity on its network. Investigators found a months-long intrusion that compromised Windows and Linux servers, workstations, hypervisors, backup servers, security management servers and network equipment. The group behind it, also known as Black Owl, Hoody Hyena and Lifting Zmiy, is assessed to be of Ukrainian origin and has been active since at least 2023, focusing on espionage and hacktivism against Russian targets.

An exposed SSH service opened the door

The attackers first compromised the company's Linux terminal server through an internet-facing SSH service, then used it to map the internal network, looking for systems with accessible SMB, Kerberos, SSH, Telnet, FTP, HTTP, HTTPS, WinRM and LDAP services. Attempts to sign in to the VMware vCenter web interface from the terminal server failed. But the vCenter server itself, version 7.0.3, was vulnerable to CVE-2021-44228, Log4Shell, and the attackers exploited it to obtain a remote command line with root privileges.

Log4Shell, a remote code execution flaw in Apache Log4j, was disclosed in December 2021 and rated 10 out of 10. Patches were available within days, yet in June 2025 the flaw was still open on this system — a gap of more than three years between the patch and the exploitation.

A backdoor disguised as a database component

From vCenter, the attackers connected to the underlying hypervisor over SSH and planted a backdoor: a shell script named "pgcache" in the /etc/cron.hourly/ directory, apparently disguised as a legitimate PostgreSQL component, which ran every hour. The script downloaded and ran a second script from a domain on the free nofrillsdns.com service, which in turn downloaded the Global Socket (GSocket) utility to give the attackers remote control of the host.

The intrusion then spread through the whole environment. The attackers stole secrets from virtual machines, broke into the GitLab software development platform and some source-code repositories, seized the GitLab server's private key, and used it to reach the Ansible orchestration system. They dumped credentials from the LSASS process and the Active Directory database, and took advantage of the same password being used for system administrator accounts in different domains to compromise the company's entire Windows infrastructure.

The code-signing server was the prize

The server that drew particular interest was the one used to sign compiled builds of the company's commercial software. Kaspersky said attackers may have wanted to inject malicious code into a product build just before it was signed, creating a supply-chain attack on the developer's customers, or to steal the organisation's digital signature for later use signing malware.

No trojanised software release was confirmed as a result of the compromise, and Kaspersky said the rapid response after the incident was discovered meant the attackers lost access and were apparently unable to bring the attack to its intended conclusion. After losing access, the group tried a phishing campaign in late July 2026, sending emails with the subject "Account disconnected from the mail server" that bypassed SPF and DKIM checks using a private key stolen from the company's mail server. That attempt was detected and prevented.

The activity was traced to two IP addresses belonging to a provider in Ukraine, and the operators appeared to follow a standard work schedule in a time zone only slightly different from the victim's. The case is a reminder that a vulnerability patched years ago remains dangerous wherever it is still unpatched. The Hacker News and ThreatBeaconX both carry the details. Published 16 November 2026.