CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

VerdantBamboo

actor · actor:verdantbamboo single-source

China-nexus APT deploying BRICKSTORM on edge devices, running MSP supply-chain intrusions, bypassing M365 conditional access, and using the AGENTPSD/PLENET tooling; GTIG now names the cluster ARMORY CASTLE and attributes the late-August 2026 zero-day exploitation of BeyondTrust Remote Support CVE-2026-102764 to it (GTIG, 2026-10-15).

Aliases: UNC5221, WARP PANDA, ARMORY CASTLE

Coverage
7
4 about it · 3 mentions · first 2026-05-30 → last 2026-11-15
Latest activity
2026-10-31
BeyondTrust Remote Support zero-day: Rapid7 reports a Metasploit module; the actor's persistence survives…
Peak priority
critical
1 critical · 3 high
Targets
technology
sectors: technology, public-sector, energy · regions: europe
Sources cited
29
18 hosts
2026-05-307 appearances2026-10-29

Action items (6)

Do-now tasks recorded on the entries about VerdantBamboo, newest first. Check the date before acting on an older one.

  • Immediate action: BeyondTrust and Google's Threat Intelligence Group confirm that an unauthenticated flaw in Remote Support (all versions up to 26.2.3) was exploited as a zero-day from late August 2026, GTIG attributing it to a suspected China-nexus espionage actor, and GTIG warns organizations to prepare for widespread exploitation now that the flaw is public, and Rapid7 reports a Metasploit module for it. Apply the BT26-05-RS patch to every self-hosted appliance (builds older than 24.3.1 must be upgraded first). The actor's persistence survives reboot and configuration reset and it deletes on-appliance logs, so snapshot and collect off-box logs from any appliance that was internet-reachable on an affected build, then redeploy from a clean patched image any whose compromise status is confirmed or unknown and rotate everything it held.
    2026-10-16CVE-2026-102764
  • Apply the BT26-05-RS patch to every self-hosted BeyondTrust Remote Support appliance now and confirm in the /appliance interface that it is installed (a build older than 24.3.1 must be upgraded first, which closes the hole but does not undo earlier exposure); apply it to self-hosted Privileged Remote Access appliances too, since BeyondTrust built and tested the patch for both products although its advisory names only Remote Support as impacted.
    2026-10-16CVE-2026-102764
  • For every appliance that was internet-reachable on a build up to 26.2.3 at any time since late August 2026: before any change, snapshot a virtual appliance with memory and export its disk, and collect the off-box syslog, reverse-proxy or WAF and perimeter firewall logs because the actor deletes on-appliance logs; then redeploy from a clean, fully patched image every appliance whose compromise status is confirmed or unknown, and rotate the credentials it held in dependency order, including the Remote Support Vault and any credential typed into a support session.
    2026-10-16CVE-2026-102764
  • Inventory which guest VMs use the VMXNET3 adapter and patch the ESX hosts carrying them to ESXi-9.1.0.0200, ESXi-9.0.2.0100, ESXi80U3k or ESXi80U2f: the escape is reachable from guest administrative privilege, which makes any tenant-operated or lower-trust VM on a shared host a path to the hypervisor.
    2026-07-30CVE-2026-59309 +4
  • Patch vCenter to 9.1.0.0300, 9.0.2.0100 or 8.0 U3k/U2f as applicable (vCenter 7.0 through Broadcom extended support), since there is no workaround, and on any appliance that was network-reachable and unpatched between 29 July and today, check the appliance's own scheduled-task and cron configuration for entries the platform team did not create, and its egress records for outbound SSH sessions from the appliance itself.
    2026-07-30CVE-2026-59309 +4
1 older action item
  • On the ESX hosts of any vCenter estate that was exposed or compromised, install the build that fixes CVE-2026-41709 and review administrator activity from vCenter task and event records and from syslog forwarded off the host, because Broadcom says the flaw lets an administrator act without being logged and CrowdStrike reports it used as a zero-day.
    2026-07-30CVE-2026-59309 +4

Defender insights

What each entry about VerdantBamboo tells a defender to do, newest first.

2026-10-16CRITICALexploitedBeyondTrust Remote Support zero-day: Rapid7 reports a Metasploit module; the actor's persistence survives reset

Exposure · triage · detection

2026-07-30HIGHexploitedVMware vCenter's pre-auth Syslog RCE is exploited; patch it with the auth bypass and VMXNET3 escape, no workaround

Relationships explore in graph

Typed, source-stated connections from the entity registry; each edge cites the entry whose reporting establishes it.

uses

Story timeline

Every entry that names VerdantBamboo, newest first. Rows tagged mention only name it in passing: they are listed for completeness and add nothing to the action items, pivots or ATT&CK profile on this page.

  1. 2026-10-29CVE-2026-109618 / CVE-2026-109619 and CVE-2026-123039, Check Point Force, Spark and Cloud firewalls: PHP2Shell on the Mobile Access and VPN web interfaces, chained with a local root escalation, is exploited against unpatched gateways (implant, ESXi wiper); the fix is in Jumbo takes R81.20 take 174, R82 take 132, R82.10 take 52 and R82.20 take 14
    mentiontrending-vulnerabilitiesCheck Point gateways exploited (PHP2Shell, root escalation): Jumbo R81.20 t174, R82 t132, R82.10 t52, R82.20 t14
  2. 2026-10-16CVE-2026-102764, BeyondTrust Remote Support: an unauthenticated file-operation flaw exploited as a zero-day since late August by a suspected China-nexus actor that left a web shell and boot-time sudo persistence (CVSS 4.0 9.3)
    trending-vulnerabilitiesBeyondTrust Remote Support zero-day: Rapid7 reports a Metasploit module; the actor's persistence survives reset
  3. 2026-07-30VMSA-2026-0006, VMware vCenter: unauthenticated Directory Service auth bypass and Syslog traversal RCE (both CVSS 9.8), plus a VMXNET3 guest-to-host escape
    trending-vulnerabilitiesVMware vCenter's pre-auth Syslog RCE is exploited; patch it with the auth bypass and VMXNET3 escape, no workaround
  4. 2026-06-11CrowdStrike 2026 Technology Threat Landscape Report: technology is now the most-targeted sector
    mentionresearch
  5. 2026-06-05VerdantBamboo (UNC5221 / WARP PANDA): an 18-month China-nexus intrusion that lived entirely on EDR-blind edge appliances and proxied into Microsoft 365 past Conditional Access
    active-threatsVerdantBamboo (UNC5221 / WARP PANDA): an 18-month China-nexus intrusion that lived entirely on EDR-blind edge appliances and proxied into Microsoft 365 past
  6. 2026-06-02Operation Dragon Weave: China-nexus espionage against Czech government with Azure Blob Storage dead-drop C2
    mentiondeep-dive
  7. 2026-05-30ESET APT Activity Report Q4 2025–Q1 2026: Sandworm strikes NATO energy, Lazarus targets EU drone sector, UNC5221 pivots to Ivanti SPAWN toolset
    research
ATT&CK techniques (19 across 10 tactics)

19 techniques observed across 3 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessValid Accounts · Valid Accounts: Cloud Accounts · Exploit Public-Facing Application
  • ExecutionScheduled Task/Job: Cron
  • PersistenceBoot or Logon Initialization Scripts · Scheduled Task/Job: Cron · Valid Accounts · Valid Accounts: Cloud Accounts · Account Manipulation · Server Software Component: Web Shell
  • Privilege EscalationBoot or Logon Initialization Scripts · Scheduled Task/Job: Cron · Valid Accounts · Valid Accounts: Cloud Accounts · Account Manipulation · Abuse Elevation Control Mechanism: Setuid and Setgid · Abuse Elevation Control Mechanism: Sudo and Sudo Caching · Escape to Host
  • StealthIndicator Removal: File Deletion · Valid Accounts · Valid Accounts: Cloud Accounts
  • Defense ImpairmentDisable or Modify Tools: Clear Linux or Mac System Logs · Exploitation for Defense Impairment
  • Credential AccessCredentials from Password Stores
  • CollectionData from Local System
  • Command and ControlProxy · Remote Access Tools · Protocol Tunneling
  • ImpactData Encrypted for Impact

Initial Access TA0001

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1078.004Valid Accounts: Cloud Accounts×1

Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application. Cloud Accounts can exist solely in the cloud; alternatively, they may be hybrid-joined between on-premises systems and the cloud through syncing or federation with other identity sources such as Windows Active Directory.

Evidence: 2026-06-05/verdantbamboo-unc5221-warp-panda-an-18-month-china-nexus-int · ATT&CK page ↗

T1190Exploit Public-Facing Application×2

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · 2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape · ATT&CK page ↗

Execution TA0002

T1053.003Scheduled Task/Job: Cron×1

Adversaries may abuse the <code>cron</code> utility to perform task scheduling for initial or recurring execution of malicious code. The <code>cron</code> utility is a time-based job scheduler for Unix-like operating systems. The <code> crontab</code> file contains the schedule of cron entries to be run and the specified times for execution. Any <code>crontab</code> files are stored in operating system-specific file paths.

Evidence: 2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape · ATT&CK page ↗

Persistence TA0003

T1037Boot or Logon Initialization Scripts×1

Adversaries may use scripts automatically executed at boot or logon initialization to establish persistence. Initialization scripts can be used to perform administrative functions, which may often execute other programs or send information to an internal logging server. These scripts can vary based on operating system and whether applied locally or remotely.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1053.003Scheduled Task/Job: Cron×1

Adversaries may abuse the <code>cron</code> utility to perform task scheduling for initial or recurring execution of malicious code. The <code>cron</code> utility is a time-based job scheduler for Unix-like operating systems. The <code> crontab</code> file contains the schedule of cron entries to be run and the specified times for execution. Any <code>crontab</code> files are stored in operating system-specific file paths.

Evidence: 2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape · ATT&CK page ↗

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1078.004Valid Accounts: Cloud Accounts×1

Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application. Cloud Accounts can exist solely in the cloud; alternatively, they may be hybrid-joined between on-premises systems and the cloud through syncing or federation with other identity sources such as Windows Active Directory.

Evidence: 2026-06-05/verdantbamboo-unc5221-warp-panda-an-18-month-china-nexus-int · ATT&CK page ↗

T1098Account Manipulation×1

Adversaries may manipulate accounts to maintain and/or elevate access to victim systems. Account manipulation may consist of any action that preserves or modifies adversary access to a compromised account, such as modifying credentials or permission groups. These actions could also include account activity designed to subvert security policies, such as performing iterative password updates to bypass password duration policies and preserve the life of compromised credentials.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1505.003Server Software Component: Web Shell×1

Adversaries may backdoor web servers with web shells to establish persistent access to systems. A Web shell is a Web script that is placed on an openly accessible Web server to allow an adversary to access the Web server as a gateway into a network. A Web shell may provide a set of functions to execute or a command-line interface on the system that hosts the Web server.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

Privilege Escalation TA0004

T1037Boot or Logon Initialization Scripts×1

Adversaries may use scripts automatically executed at boot or logon initialization to establish persistence. Initialization scripts can be used to perform administrative functions, which may often execute other programs or send information to an internal logging server. These scripts can vary based on operating system and whether applied locally or remotely.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1053.003Scheduled Task/Job: Cron×1

Adversaries may abuse the <code>cron</code> utility to perform task scheduling for initial or recurring execution of malicious code. The <code>cron</code> utility is a time-based job scheduler for Unix-like operating systems. The <code> crontab</code> file contains the schedule of cron entries to be run and the specified times for execution. Any <code>crontab</code> files are stored in operating system-specific file paths.

Evidence: 2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape · ATT&CK page ↗

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1078.004Valid Accounts: Cloud Accounts×1

Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application. Cloud Accounts can exist solely in the cloud; alternatively, they may be hybrid-joined between on-premises systems and the cloud through syncing or federation with other identity sources such as Windows Active Directory.

Evidence: 2026-06-05/verdantbamboo-unc5221-warp-panda-an-18-month-china-nexus-int · ATT&CK page ↗

T1098Account Manipulation×1

Adversaries may manipulate accounts to maintain and/or elevate access to victim systems. Account manipulation may consist of any action that preserves or modifies adversary access to a compromised account, such as modifying credentials or permission groups. These actions could also include account activity designed to subvert security policies, such as performing iterative password updates to bypass password duration policies and preserve the life of compromised credentials.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1548.001Abuse Elevation Control Mechanism: Setuid and Setgid×1

An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context. On Linux or macOS, when the setuid or setgid bits are set for an application binary, the application will run with the privileges of the owning user or group respectively. Normally an application is run in the current user’s context, regardless of which user or group owns the application. However, there are instances where programs need to be executed in an elevated context to function properly, but the user running them may not have the specific required privileges.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1548.003Abuse Elevation Control Mechanism: Sudo and Sudo Caching×1

Adversaries may perform sudo caching and/or use the sudoers file to elevate privileges. Adversaries may do this to execute commands as other users or spawn processes with higher privileges.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1611Escape to Host×1

Adversaries may break out of a container or virtualized environment to gain access to the underlying host. This can allow an adversary access to other containerized or virtualized resources from the host level or to the host itself. In principle, containerized / virtualized resources should provide a clear separation of application functionality and be isolated from the host environment.

Evidence: 2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape · ATT&CK page ↗

Stealth TA0005

T1070.004Indicator Removal: File Deletion×1

Adversaries may delete files left behind by the actions of their intrusion activity. Malware, tools, or other non-native files dropped or created on a system by an adversary (ex: Ingress Tool Transfer) may leave traces to indicate to what was done within a network and how. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1078.004Valid Accounts: Cloud Accounts×1

Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application. Cloud Accounts can exist solely in the cloud; alternatively, they may be hybrid-joined between on-premises systems and the cloud through syncing or federation with other identity sources such as Windows Active Directory.

Evidence: 2026-06-05/verdantbamboo-unc5221-warp-panda-an-18-month-china-nexus-int · ATT&CK page ↗

Defense Impairment TA0112

T1685.006Disable or Modify Tools: Clear Linux or Mac System Logs×1

Adversaries may clear system logs to hide evidence of an intrusion. macOS and Linux both keep track of system or user-initiated actions via system logs. The majority of native system logging is stored under the `/var/log/` directory. Subfolders in this directory categorize logs by their related functions, such as:

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1687Exploitation for Defense Impairment×1

Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.

Evidence: 2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape · ATT&CK page ↗

Credential Access TA0006

T1555Credentials from Password Stores×1

Adversaries may search for common password storage locations to obtain user credentials. Passwords are stored in several places on a system, depending on the operating system or application holding the credentials. There are also specific applications and services that store passwords to make them easier for users to manage and maintain, such as password managers and cloud secrets vaults. Once credentials are obtained, they can be used to perform lateral movement and access restricted information.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

Collection TA0009

T1005Data from Local System×1

Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

Command and Control TA0011

T1090Proxy×2

Adversaries may use a connection proxy to direct network traffic between systems or act as an intermediary for network communications to a command and control server to avoid direct connections to their infrastructure. Many tools exist that enable traffic redirection through proxies or port redirection, including HTRAN, ZXProxy, and ZXPortMap. Adversaries use these types of proxies to manage command and control communications, reduce the number of simultaneous outbound network connections, provide resiliency in the face of connection loss, or to ride over existing trusted communications paths between victims to avoid suspicion. Adversaries may chain together multiple proxies to further disguise the source of malicious traffic.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · 2026-06-05/verdantbamboo-unc5221-warp-panda-an-18-month-china-nexus-int · ATT&CK page ↗

T1219Remote Access Tools×1

An adversary may use legitimate remote access tools to establish an interactive command and control channel within a network. Remote access tools create a session between two trusted hosts through a graphical interface, a command line interaction, a protocol tunnel via development or management software, or hardware-level access such as KVM (Keyboard, Video, Mouse) over IP solutions. Desktop support software (usually graphical interface) and remote management software (typically command line interface) allow a user to control a computer remotely as if they are a local user inheriting the user or software permissions. This software is commonly used for troubleshooting, software installation, and system management. Adversaries may similarly abuse response features included in EDR and other defensive tools that enable remote access.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · ATT&CK page ↗

T1572Protocol Tunneling×2

Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection/network filtering and/or enable access to otherwise unreachable systems. Tunneling involves explicitly encapsulating a protocol within another. This behavior may conceal malicious traffic by blending in with existing traffic and/or provide an outer layer of encryption (similar to a VPN). Tunneling could also enable routing of network packets that would otherwise not reach their intended destination, such as SMB, RDP, or other traffic that would be filtered by network appliances or not routed over the Internet.

Evidence: 2026-10-16/cve-2026-102764-beyondtrust-remote-support-zero-day · 2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape · ATT&CK page ↗

Impact TA0040

T1486Data Encrypted for Impact×1

Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources. They can attempt to render stored data inaccessible by encrypting files or data on local and remote drives and withholding access to a decryption key. This may be done in order to extract monetary compensation from a victim in exchange for decryption or a decryption key (ransomware) or to render data permanently inaccessible in cases where the key is not saved or transmitted.

Evidence: 2026-07-30/vmware-vmsa-2026-0006-vcenter-auth-bypass-vmxnet3-escape · ATT&CK page ↗

Entries about VerdantBamboo (4)

2026-10-16 · view entry permalink →

CRITICALCVE-2026-102764exploitedupdatedNATOB1

CVE-2026-102764, BeyondTrust Remote Support: an unauthenticated file-operation flaw exploited as a zero-day since late August by a suspected China-nexus actor that left a web shell and boot-time sudo persistence (CVSS 4.0 9.3)

BeyondTrust's advisory BT26-05 of 2026-10-15 fixes CVE-2026-102764, an improper origin validation (CWE-290) in an internal messaging component of Remote Support that lets a remote attacker perform file operations on the appliance without authenticating; every version up to 26.2.3 is affected (BeyondTrust, 2026-10-15). Google's Threat Intelligence Group found in an incident response that ARMORY CASTLE, a suspected PRC-nexus espionage actor it formerly tracked as UNC5221, exploited the flaw as a zero-day in late August 2026 (GTIG, 2026-10-15); BeyondTrust dates the exploitation of one hosted instance and one self-hosted appliance to 2026-08-29 (BeyondTrust, 2026-10-15). GTIG warns that ARMORY CASTLE and others have historically exploited broadly once a flaw is public (GTIG, 2026-10-15); BeyondTrust lists government among the actor's documented targets (BeyondTrust, 2026-10-15). On 2026-10-30 Rapid7 published a root-cause analysis in which one forged message makes an internal file-transfer service write a PHP file into the site's public directory, run as the site's operating-system user, and says a Metasploit module now implements the chain (Rapid7, 2026-10-30).

After the exploit GTIG saw SAWFLY, a lightweight PHP web shell that evaluates attacker-supplied code as the appliance's unprivileged site account; the actor then made a root-owned SUID copy of the system shell, tried to dump the appliance's native secrets vault, and persisted through a boot-time script that adds a passwordless-sudo line to the sudoers template, so the escalation survives reboot and configuration reset (GTIG, 2026-10-15). It deleted appliance logs throughout, raised an account's Jump Item and Team permissions from No Access to Administrator, and exposed BARECLAW, a custom SOCKS5-over-WebSocket tunneler, by editing the HAProxy configuration (GTIG, 2026-10-15).

Triage: an administrator changing Jump Item roles or signing in from a new network under a change ticket is routine; BeyondTrust's signal is a privileged session from a residential or VPN address tied to no administrator or ticket (BeyondTrust, 2026-10-15).

exploited this vulnerability as a zero-day, in late August 2026

CVE-2026-102764 affects all supported Remote Support versions up to 26.2.3 and allows an unauthenticated remote attacker to perform file operations on the appliance

Customers cannot audit the appliance host file system, and host-level persistence survives reboot and configuration reset.

Google Threat Intelligence Group / Mandiant 2026-10-15

BeyondTrust has remediated a critical vulnerability in Remote Support (RS) that could allow a remote attacker to perform file operations on an affected appliance.

As of today we are withholding the technical details of the vulnerability.

BeyondTrust

A Metasploit module now implements the chain with PHP and Unix Command targets.

Detection that only searches for requests ending in .php would miss the successful request in this example.

Rapid7 2026-10-30
Updaterun 2026-10-31T0256Z-intelheadlinesummaryimmediate_actionsourcesevidenceactionsbody

Rapid7 published a root-cause analysis on 2026-10-30 and says a Metasploit module now implements the chain, with PHP and Unix Command targets (Rapid7, 2026-10-30). An anonymous customer session, started through the public customer connection, sends a message whose source address carries a reserved local router ID; the appliance's customer worker accepts that address as proof that the request came from a local component, which exposes an internal file-transfer service with its native filesystem provider. Rapid7 used it to write a PHP file into the site's public directory and ran it as the site's operating-system user (Rapid7, 2026-10-30). The successful request was an extensionless URL, because the web server answers a direct .php request with 404 and maps an extensionless URL to the existing file, so detection that only searches for requests ending in .php would miss it; the appliance's thin-scc logs record file-transfer stream creation and rejected requests (Rapid7, 2026-10-30). Rapid7 tested Remote Support 24.1.2 and says other affected releases and fixed builds have not been established (Rapid7, 2026-10-30); BeyondTrust's advisory remains the reference for affected and fixed versions (BeyondTrust, 2026-10-15).

Builds on: NCSC-CH flags critical pre-auth bypass in BeyondTrust RS/PRA appliances (CVE-2026-40138/-40139) · VerdantBamboo (UNC5221 / WARP PANDA): an 18-month China-nexus intrusion that lived entirely on…

vulnerability16 Oct 04:16Zmulti-sourceOpen finding →

2026-07-30 · view entry permalink →

HIGHCVE-2026-59309 +4exploitedupdatedNATOA1

VMSA-2026-0006, VMware vCenter: unauthenticated Directory Service auth bypass and Syslog traversal RCE (both CVSS 9.8), plus a VMXNET3 guest-to-host escape

Broadcom published VMSA-2026-0006 on 2026-07-29, covering five vulnerabilities across VMware ESX, vCenter, Workstation and Fusion, and stating that they "were privately reported to Broadcom" with updates available to remediate them (Broadcom, 2026-07-29). Three national CERTs picked it up immediately: NCSC-CH on 2026-07-29 (NCSC Switzerland, 2026-07-29), NCSC-NL on 2026-07-29 (NCSC-NL, 2026-07-29), and BSI CERT-Bund, whose advisory is dated 2026-07-28 with a 2026-07-29 revision (BSI CERT-Bund, 2026-07-29).

Two of the five sit on vCenter and need no credentials. CVE-2026-59309 (CVSS 9.8) is an authentication bypass in the VMware Directory Service, and Broadcom's own attack-vector text is unambiguous about the prerequisite: "a malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system" (Broadcom, 2026-07-29). CVE-2026-59310, also CVSS 9.8, is a directory-traversal flaw in vCenter's Syslog server that reaches arbitrary code execution through manipulated file and directory paths (Broadcom, 2026-07-29). vCenter is the control plane for an entire virtual estate: an unauthenticated path into it is a path to every workload it manages, which is why an anonymous network-reachable bypass warranted out-of-cycle handling even though no exploitation had been reported at first publication. CVE-2026-59310 has since been exploited in the wild, as the updates below record.

The third flaw crosses the isolation boundary in the other direction. CVE-2026-47876 (CVSS 9.3) is an out-of-bounds write in the VMXNET3 virtual network adapter, and Broadcom scopes it precisely: "a malicious actor with local administrative privileges on a virtual machine with VMXNET3 virtual network adapter may exploit this issue to execute code on the host. Non VMXNET3 virtual adapters are not affected by this issue" (Broadcom, 2026-07-29). That precondition is the useful part of the triage: exposure is determined by adapter configuration rather than by ESX version alone, so the inventory question is which guests run VMXNET3 and how much you trust whoever administers them.

Two lower-severity issues complete the advisory. CVE-2026-41703 is an out-of-bounds read that Broadcom scores differently by product: 7.6 on ESX, where it says a denial of service of the host process is the more likely outcome than information disclosure, against 2.7 on Workstation and Fusion, where it restricts the impact to information disclosure (Broadcom, 2026-07-29). CVE-2026-41709 is insufficient logging on ESX that allows an administrator to act without the action being recorded (Broadcom, 2026-07-29); CrowdStrike says WARP PANDA exploited it as a zero-day and CISA lists it as exploited, so ESX audit logs are not a complete record of administrator activity.

Two further product families are in scope: Broadcom lists VMware Telco Cloud Platform and VMware Telco Cloud Infrastructure as impacted, with their own knowledge-base fix path rather than the vCenter and ESXi build numbers below (Broadcom, 2026-07-29).

Fixed builds differ per flaw and per track. vCenter takes 9.1.0.0300, 9.0.2.0100, 8.0 U3k or, on the U2 branch, 8.0 U2f, with Cloud Foundation 5.x served by an async patch to 8.0 U3k; the VMXNET3 escape is fixed in ESXi-9.1.0.0200, ESXi-9.0.2.0100, ESXi80U3k and ESXi80U2f, and the 7.0 lines are served only under Broadcom extended support (Broadcom, 2026-08-19). Broadcom records no workaround for any of the five, which removes the usual option of mitigating while the maintenance window is arranged.

At first publication nothing here was reported exploited. Broadcom states the vulnerabilities "were privately reported to Broadcom" and credits Atredis Partners, Nguyen Hoang Thach of STARLabs SG working with Pwn2Own held by the Zero Day Initiative, Maxim Suhanov, and CrowdStrike (Broadcom, 2026-07-29), and none of the three national CERTs reported in-the-wild activity. What earned this out-of-cycle attention at publication was the reachability profile rather than an exploitation signal: two anonymous network paths into a virtualization control plane, with no interim control available. CVE-2026-59310 and CVE-2026-41709 have since been reported exploited, as the updates below record.

Detection on the vCenter side means watching the two named services rather than the appliance generally: authentication events from the Directory Service, where a successful bind that no operator session accounts for is the signal, and Syslog-server request logging, where path-traversal sequences in a requested file or directory path have no legitimate counterpart. For the guest-to-host escape the telemetry is host-side: hypervisor crash and process-fault records on ESX hosts running VMXNET3 guests, since a failed escape attempt is far more likely to surface as an anomalous fault than as a clean compromise. On hardening, NCSC-NL is the source that spells out the architectural control: access to ESX and vCenter should be made available only from a separated management environment and not reachable directly from the internet or external networks (NCSC-NL, 2026-07-29). Broadcom's own advisory offers no hardening section and records "Workarounds: None" against every one of the five.

A malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system.

A malicious actor with local administrative privileges on a virtual machine with VMXNET3 virtual network adapter may exploit this issue to execute code on the host. Non VMXNET3 virtual adapters are not affected by this issue.

Multiple vulnerabilities in VMware ESX, vCenter, Workstation, and Fusion were privately reported to Broadcom. Updates are available to remediate these vulnerabilities in affected Broadcom products.

Broadcom 2026-07-29

Compromised systems identified by QUIRSO were found to first establish contact with the attacker's domains on August 3, five days after Broadcom publicly disclosed the flaw.

followed by the deployment of a malicious cron job to establish persistence on the host using reverse_ssh

The Hacker News 2026-08-12

The presence of reverse_ssh should not, by itself, be treated as proof of malicious activity.

In combination with unauthorized installation, unexpected outbound connections or execution on a vulnerable vCenter appliance, however, it is a high-priority indicator requiring investigation.

QUIRSO GmbH 2026-08-10

Current exploitation status: Actively Exploited

NCSC Switzerland 2026-07-29

The digital forensics company assessed a suspected advanced persistent threat (APT) actor was responsible, counting 361 victim IP addresses across 47 countries

Infosecurity Magazine, citing QUIRSO GmbH 2026-08-13

based on the investigation so far, it's suspected that the deployment of the locker may not have been the primary objective of the campaign

The Hacker News, paraphrasing QUIRSO's assessment

In several of these cases, and as late as early 2026, the adversary exploited ESXi command logging bypass vulnerability CVE-2026-41709 as a zero-day.

CrowdStrike 2026-10-28
Updaterun 2026-08-13T0412Z-intelactionscvesevidenceregionssectorssourcestagstechniquesbody

One of the five VMSA-2026-0006 flaws, none of which was reported exploited at disclosure, has now been confirmed in use against real estates.

QUIRSO, a German security firm, reports that an incident-response engagement gave it visibility into an exploitation campaign against internet-accessible vCenter systems using CVE-2026-59310, the CVSS 9.8 directory traversal in the vCenter Syslog server that reaches arbitrary code execution from network access alone (QUIRSO, 2026-08-10). The timeline is the part that should reset patch priorities: "Compromised systems identified by QUIRSO were found to first establish contact with the attacker's domains on August 3, five days after Broadcom publicly disclosed the flaw" (The Hacker News, 2026-08-12). QUIRSO records 361 unique victim IP addresses across 47 countries, with Germany, the United States, Turkey, Iran and France the most affected and 185 of the 361 addresses in those five countries; it is explicit that an address does not correspond to an organisation, since some belong to hosting providers and shared infrastructure. By 5 August, 343 of the 361 addresses had already appeared: the campaign reached roughly 95 per cent of its observed footprint within three days of starting (QUIRSO, 2026-08-10). QUIRSO assesses that while the attacker might have had prior knowledge of the flaw, the correlation with disclosure suggests the advisory itself was the campaign's starting point.

Switzerland's NCSC updated its own VMSA-2026-0006 advisory on 12 August, setting "Current exploitation status: Actively Exploited" and citing QUIRSO's report (NCSC-CH, 2026-08-12).

What the attacker does after landing. The chain reported is path-traversal activity consistent with the flaw, "followed by the deployment of a malicious cron job to establish persistence on the host using reverse_ssh" (The Hacker News, 2026-08-12), an open-source SSH-based reverse-shell framework whose legitimate penetration-testing features include automatic connect-back, port forwarding and file transfer. The choice is a deliberate one about direction of travel: the control channel is established outbound from the appliance, which sidesteps controls built to stop unsolicited inbound access (QUIRSO, 2026-08-10). QUIRSO says a follow-up publication examining the attacker's tradecraft, infrastructure and post-exploitation activity is planned, and that further detection content is being released in coordination with law-enforcement partners.

A second, separate signal sits alongside it and should not be merged with the first. The Hacker News reports Defused Cyber observing a spike in scanning against vCenter (version probes and walks of the single-sign-on flow) that it associates with CVE-2026-59309, the unauthenticated Directory Service authentication bypass from the same advisory. QUIRSO's co-founder Denis Szadkowski told the outlet there is not enough evidence to correlate that scanning with the intrusion set behind CVE-2026-59310, adding that "the forensic evidence strongly points toward CVE-2026-59310 as the initial access vector" for the compromises QUIRSO investigated (The Hacker News, 2026-08-12). Two flaws in one advisory are drawing attention independently; only one has confirmed compromises behind it.

Detection concepts, telemetry class first. The behaviours worth hunting are all unusual for a management appliance rather than unusual in general. In egress and flow records, an SSH-protocol session initiated from a vCenter appliance to an external destination inverts the normal direction of vCenter traffic, which is inbound administrative access and outbound management of hosts. In configuration and scheduling state on the appliance, cron or scheduled entries that no platform-engineering change record accounts for are the persistence artefact reported here. In process telemetry, execution lineage descending from the Syslog service is the exploitation artefact. QUIRSO's own framing of the tool is the right calibration and applies to any dual-use binary: "The presence of reverse_ssh should not, by itself, be treated as proof of malicious activity." and "In combination with unauthorized installation, unexpected outbound connections or execution on a vulnerable vCenter appliance, however, it is a high-priority indicator requiring investigation." (QUIRSO, 2026-08-10)

Triage: administrators do legitimately place scheduled jobs on appliances and do run SSH from jump hosts, so neither artefact alone resolves. What separates this activity is the appliance being the SSH client toward an external network, a scheduled entry created outside a change window and not present in the platform team's configuration baseline, and either appearing on a vCenter whose build predates the VMSA-2026-0006 fixes. On an appliance patched before 29 July none of the three should be present at all.

Updaterun 2026-08-28T0409Z-intelcvestagstechniquessourcesevidencebody

CISA added CVE-2026-59310 to its Known Exploited Vulnerabilities catalog on 2026-08-18, a jurisdiction-agnostic confirmation of active exploitation, independent of any US-FCEB remediation deadline, layered on top of NCSC-CH's own actively-exploited determination already recorded above.

QUIRSO's continued work on the campaign now attributes the activity to a suspected China-nexus actor and reports that Babuk-derived ransomware was deployed against ESXi hosts in at least one investigated case (The Hacker News, 2026-08-17). Infosecurity Magazine had reported only QUIRSO's earlier assessment that "a suspected advanced persistent threat (APT) actor was responsible" (Infosecurity Magazine, citing QUIRSO GmbH, 2026-08-13). The ransomware deployment is assessed by QUIRSO as plausibly a smokescreen rather than the operation's goal: the deployment of "the locker", the Babuk-derived payload, "may not have been the primary objective of the campaign" (The Hacker News, paraphrasing QUIRSO's assessment, 2026-08-17), plausibly intended to encrypt ESXi log files and hinder forensics rather than for extortion.

Both findings warrant the same caveat as the CVE-2026-59309 scanning correlation: every outlet surveyed (The Hacker News, Infosecurity Magazine, and further security-press pickup) cites QUIRSO's own Medium write-ups as the sole source for the China-nexus attribution (built on a UTC+08:00 activity pattern, Chinese-language code artefacts, and reuse of a Chinese security publication) at QUIRSO's own stated moderate confidence, and for the ransomware finding. Two outlets reporting one firm's conclusion is wide distribution of a single assessor's work, not independent corroboration of it: the attribution and the ransomware-deployment finding should be read as QUIRSO's own assessment, not as cross-verified intelligence; the multi-CERT corroboration covers the vulnerability and initial-exploitation facts only.

Nothing in this update changes the remediation guidance already given above: patch every internet-reachable vCenter to the fixed builds, and treat any instance that was internet-reachable and unpatched between 29 July and 3 August as a compromise-assessment candidate rather than a patch-and-close item; that assessment should now explicitly include a check for Babuk-derived encrypted files on any ESXi hosts the appliance manages, alongside the reverse_ssh persistence and cron-entry artefacts already described.

Correctionrun 2026-09-29T2134Z-auditevidencesummaryactionssourcessourcing_notebody

CVE-2026-59310, the vCenter Syslog traversal, has been exploited in the wild since before the update of 2026-08-13, and CISA added it to its Known Exploited Vulnerabilities catalog on 2026-08-18 (CISA KEV). The patch guidance is unchanged, and the compromise check in the actions applies to any vCenter that was exposed and unpatched.

The Directory Service authentication bypass may not be far behind. On one compromised vCenter appliance that QUIRSO analysed, the evidence shows malicious activity consistent with exploitation of CVE-2026-59309 as early as 2026-08-01, followed by the creation of an administrative account on vCenter, with no login events for the legitimate administrator account used to create it (The Hacker News, 2026-08-17). That is one appliance and a "consistent with" finding, and CVE-2026-59309 is not in CISA's KEV catalog, so its status here stays patch-available. On an exposed vCenter, an administrative account created without a matching administrator login is the signal to look for.

Updaterun 2026-10-29T0255Z-intelsummaryupdated_atentitiestagstechniquescvessourcesevidencesourcing_noteactionsbody

CISA added CVE-2026-41709, the ESX insufficient-logging flaw, to its Known Exploited Vulnerabilities catalog on 2026-10-28 on evidence of active exploitation, naming no actor (CISA KEV). CrowdStrike says WARP PANDA deployed several forms of malware in victims' VMware vCenter environments and that in several of these cases, as late as early 2026, the adversary exploited the ESXi command logging bypass CVE-2026-41709 as a zero-day; it describes intrusions at U.S.-based entities that included the legal sector, and gives no indicators, no account of what goes unlogged and no date of first exploitation (CrowdStrike, 2026-10-28). Broadcom's advisory rates the flaw 2.7 and carries no exploitation statement (Broadcom, 2026-07-29). CrowdStrike does not say how the actor obtained administrator rights on the host or whether the flaws of CVE-2026-59309 and CVE-2026-59310 were involved, so no link to them is drawn. Until the fix is installed, ESX logs from a period of administrator access are not reliable evidence of what was done; vCenter task and event records and syslog forwarded off the host are the sources to review.

Correctionrun 2026-11-01T1312Z-auditactionsbodycvesheadlinesourcessourcing_notetitle

Broadcom revised the advisory twice after first publication: on 2026-08-03 (VMSA-2026-0006.1) the vCenter 8.0 U2f and ESX 8.0 U2f express patches became available, and on 2026-08-19 (VMSA-2026-0006.2) it added patch guidance for the 7.0 lines, where vCenter and ESX 7.0 customers are told to contact Broadcom Support under an extended support contract (Broadcom, 2026-08-19). The fixed-build statements above now include those paths. Broadcom scores CVE-2026-41703 and CVE-2026-41709 with a network attack vector that needs high privileges, and credits Maxim Suhanov by name (Broadcom, 2026-08-19).

The 2026-08-28 section said Infosecurity Magazine reported the same assessment as The Hacker News; its article of 2026-08-13 reports only QUIRSO's earlier assessment of a suspected APT actor and predates the China-nexus and Babuk findings (Infosecurity Magazine, citing QUIRSO GmbH, 2026-08-13). CISA's catalog now marks CVE-2026-59310 as known to be used in ransomware campaigns, without naming an actor or a ransomware family (CISA KEV, 2026-10-30), so the ransomware finding no longer rests on QUIRSO alone.

vulnerability30 Jul 04:54Zmulti-sourceOpen finding →

2026-06-05 · view entry permalink →

HIGH

VerdantBamboo (UNC5221 / WARP PANDA): an 18-month China-nexus intrusion that lived entirely on EDR-blind edge appliances and proxied into Microsoft 365 past Conditional Access

Volexity attributes an incident-response case at a European organisation to a China-linked actor it tracks as VerdantBamboo (assessed with high confidence as UNC5221, also WARP PANDA), with access dating back at least 18 months (Volexity, 2026-06-04). Initial access came through the victim's MSP: the actor had planted a BSD build of the BRICKSTORM Golang backdoor on the MSP's pfSense firewall. The defining tradecraft is deliberate EDR avoidance; every implant sat on appliances that cannot run an endpoint agent (firewall, Synology NAS, a retired GroupWise server) or on an Egnyte Storage Sync Linux VM. BRICKSTORM's proxy capability on the Storage Sync host let the actor route authentication to the victim's M365 tenant through that appliance's trusted egress IP, defeating Conditional Access rules that would have blocked an unrecognised source address (T1090 internal proxy, T1078.004 cloud accounts). After Volexity's first remediation, VerdantBamboo simply re-authenticated to the firewall with stolen admin credentials, re-enabled SSL VPN, and redeployed BRICKSTORM to the NAS, alongside two previously undocumented implants: AGENTPSD (a PyInstaller-packaged Python HTTPS reverse shell kept as a fallback) and PLENET/GRIMBOLT (a .NET Native AOT backdoor on a Linux NAS).

Why it matters to us: this is the precise threat model a federal SOC carries; an MSP relationship plus a fleet of edge appliances that are invisible to EDR by design. Detection has to move off the endpoint: hunt M365 sign-in logs for interactive auth originating from the egress IPs of NAS / storage-sync / firewall appliances (those should never originate user logins), alert on SSL-VPN re-enablement and admin auth to perimeter devices, and treat any appliance the vendor forbids you from instrumenting as an assumed-breach surface. Mandate MFA on all firewall management and SSL-VPN interfaces, and put the MSP's access to your perimeter under the same scrutiny as a privileged insider. [SINGLE-SOURCE], Volexity primary IR (.

threat05 Jun 05:00Zsingle-sourceOpen finding →

Earlier coverage (1)

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns3
  • Research2
  • Deep dive1
  • Threats1

Source distribution

  • attack.mitre.org5 (17%)
  • thehackernews.com3 (10%)
  • beyondtrust.com2 (7%)
  • cisa.gov2 (7%)
  • crowdstrike.com2 (7%)
  • infosecurity-magazine.com2 (7%)
  • support.checkpoint.com2 (7%)
  • advisories.ncsc.nl1 (3%)
  • other10 (34%)
All cited sources (29)