Skip to main content
Mallory
← Back to News
actively-exploited-vulnerabilityinformation-technology-sector-threatpersistence-methodcredential-access-method

BO Team Exploits Log4Shell to Breach Russian Developer's Code-Signing Infrastructure

Active Exploitation · 4 sources · Updated 1d ago · First seen Nov 16, 2026

BO Team Exploits Log4Shell to Breach Russian Developer's Code-Signing Infrastructure

BO Team compromised an unnamed Russian software developer in a months-long intrusion that exposed confidential information and critical software-development infrastructure, according to Kaspersky ICS CERT. The attackers, also known as Black Owl, Hoody Hyena, and Lifting Zmiy, exploited Log4Shell in VMware vCenter and gained access to development systems, a code-signing server, virtualization infrastructure, and Windows and Linux environments. Investigators assessed that the likely objective was a software supply-chain attack against the developer's customers, but did not establish that malicious software reached customers.

The attackers maintained persistent backdoors, stole credentials, and abused legitimate administration tools to move laterally while limiting detection. MITRE ATT&CK's related credential-access guidance identifies theft of the Active Directory NTDS database as technique T1003.003, although the supplied incident account does not establish that BO Team used that specific method. Response measures removed the attackers' access, and a subsequent credential-phishing campaign in late July was detected and prevented. The compromise highlights the need to patch exposed virtualization infrastructure, isolate code-signing systems, and investigate credential theft across development and identity environments.

This is being exploited nowSee which actors are running it and whether you're in range.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

16 events · Jun 2025
  1. Reported Nov 16, 20262d ago

    Follow-up credential-phishing campaign is detected and prevented

    After losing access, the attackers launched a credential-phishing campaign in late July using emails titled 'Account disconnected from the mail server' and a replica of the organization's website. The campaign was detected and prevented; messages passed SPF and DKIM checks, which investigators interpreted as evidence that the attackers possessed a private key obtained through the mail-server compromise.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  2. Reported Nov 16, 20262d ago

    Incident response removes attacker access

    Response measures removed the attackers' access to the compromised infrastructure. Investigators assessed that the response apparently prevented completion of the suspected supply-chain operation.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  3. Reported Nov 16, 20262d ago

    Kaspersky attributes the intrusion to BO Team

    Kaspersky attributed the intrusion to BO Team, also known as Black Owl, Hoody Hyena, and Lifting Zmiy, and assessed the group to be of Ukrainian origin. Unlike some of the group's previous operations, this intrusion involved no reported data destruction or public claim of responsibility.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  4. Reported Nov 16, 20262d ago

    Intrusion reaches the developer's code-signing server

    The attackers compromised the server used to sign compiled builds of the developer's commercial software; investigators found malware use on this server and suspected an attempt to execute a malicious WMI script and install a backdoor. Investigators assessed a likely software supply-chain objective but did not establish that malicious software reached customers.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  5. Reported Nov 16, 20262d ago

    Attackers obtain terminal-server root access and install credential capture

    After obtaining domain administrator privileges, the attackers accessed the terminal server as root and modified /usr/bin/nxnode-login to capture user credentials. They also brute-forced an administrator's terminal-server password after approximately 2,500 failed attempts, enabling placement of the Ansible system's private key.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  6. Reported Nov 16, 20262d ago

    Administrator password reuse enables compromise of the Windows infrastructure

    Reused passwords among system administrator accounts in different domains allowed the attackers to compromise the organization's entire Windows infrastructure.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  7. Reported Nov 16, 20262d ago

    Active Directory database theft exposes all domain users' credentials

    The attackers dumped the system registry with regedit.exe and used the extracted material to decrypt ntds.dit, obtaining credentials for all domain users. They transferred collected information to the terminal server with scp.exe and accessed the domain controller using a domain administrator's Kerberos ticket.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  8. Reported Nov 16, 20262d ago

    Security software blocks Nanodump during credential-dumping activity

    A security solution detected and blocked an attempt to dump lsass.exe with Nanodump, after which the attackers deleted event logs. The attackers also used comsvcs.dll to create an LSASS memory dump.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  9. Reported Nov 16, 20262d ago

    Compromised domain credentials enable domain-controller access

    The attackers obtained several domain-account credentials through the Linux terminal server and accessed a domain controller using a system administrator's account. Investigators considered virtual-machine memory access on compromised hypervisors a possible source of the credentials.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  10. Reported Nov 16, 20262d ago

    Stolen secrets expose GitLab repositories and Ansible orchestration

    Secrets found on compromised virtual machines enabled access to the GitLab development server, some source-code repositories, and the server's private key. The attackers used that key to connect to the organization's Ansible orchestration system.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  11. Reported Nov 16, 20262d ago

    Attackers access guest systems and deploy an SSH remote-control payload

    The attackers collected virtual-machine and firewall information and accessed guest operating systems through compromised hypervisors. An obfuscated Bash script decrypted and launched an ELF binary providing remote control over SSH.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  12. Reported Nov 16, 20262d ago

    Stolen hypervisor certificate enables access to a second virtualization cluster

    The attackers accessed the corporate proxy server and abused a compromised hypervisor's certificate to enter a second virtualization cluster. They deployed a similar backdoor there.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  13. Reported Nov 16, 20262d ago

    Attackers establish persistent remote access on a hypervisor

    The attackers connected to a hypervisor over SSH and installed an hourly cron script named pgcache. The backdoor downloaded a secondary script that deployed Global Socket for remote control, using attacker-controlled DNS records to activate downloads.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  14. Reported Nov 16, 20262d ago

    Log4Shell exploitation provides root access to VMware vCenter

    After initial access attempts failed, the attackers exploited CVE-2021-44228 on VMware vCenter 7.0.3 to obtain a root command shell.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  15. Reported Nov 16, 20262d ago

    Attackers breach a Linux terminal server and map internal services

    Attackers compromised the Russian software developer's Linux terminal server through an exposed SSH service. They used it to discover internal services and attempt access to internal portals and VMware vCenter.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
  16. Jun 2025

    Russian developer requests Kaspersky investigation after detecting suspicious activity

    The unnamed software developer contacted Kaspersky ICS CERT in June 2025 after detecting suspicious activity. The investigation uncovered a months-long compromise involving confidential information theft and extensive access across development, virtualization, Windows, and Linux infrastructure.

    BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Vulnerabilities

1 linked

Threat actors

1 linked

Affected products

5 linked
GitlabWindowsActive DirectoryVmware Vcenter ServerAnsible

Observables

3 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?Correlate live exploitation activity against the software you actually run, and see where you're exposed.
See Who's Exploiting This
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.