Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

ARMORY CASTLE Moves from Remote Support to vCenter

The ARMORY CASTLE vCenter attack moved from BeyondTrust Remote Support through Linux appliances. Trace the reported chain, affected builds, and checks.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
19 November 2026
Reading time
8 min read
A guarded path from a remote support appliance to a virtualized server control plane

The ARMORY CASTLE vCenter attack shows how a compromised remote support appliance can become a route into the virtualization control plane. Google Threat Intelligence Group (GTIG) published the sequence on November 19, 2026. Its forensic evidence places the vCenter exploitation in early September, before Broadcom publicly disclosed CVE-2026-123890.

GTIG attributes the operation to ARMORY CASTLE, formerly UNC5221, which it describes as a suspected PRC-nexus espionage actor. That is GTIG’s attribution, not an independently established identity. A cyber threat intelligence platform can help defenders track GTIG’s report while examining the path from BeyondTrust Remote Support through internal Linux systems to vCenter and ESXi.

How Did the ARMORY CASTLE vCenter Attack Begin?

GTIG says the actor first exploited CVE-2026-102764 in BeyondTrust Remote Support. BeyondTrust says it released the BT26-05 patch on October 8 for supported Remote Support versions. Its October account says the actor used the appliance to gain interactive control, pursue stored credentials, and reach downstream systems.

The BeyondTrust Remote Support flaw profile covers the entry vulnerability. The new GTIG report follows the operation beyond that appliance. It describes reconnaissance focused on VMware services and a move to internal Linux appliances without endpoint detection tooling.

GTIG-reported movement across the environment
GTIG-reported movement across the environmentAttack path in 4 steps: 1, Remote Support foothold (Remote support), then initial access and internal reconnaissance; 2, Internal Linux foothold (Linux appliance), then webshells, privilege escalation and staging; 3, vCenter control (vCenter), then BONESAW exploitation and SSO administrator access; 4, ESXi access (ESXi).Remote supportLinux appliancevCenterESXiinitial access and…webshells, privilege…BONESAW exploitation and…RemoteSupport…InternalLinux…vCentercontrolESXi access
  1. Remote Support footholdRemote supportinitial access and internal reconnaissance
  2. Internal Linux footholdLinux appliancewebshells, privilege escalation and staging
  3. vCenter controlvCenterBONESAW exploitation and SSO administrator access
  4. ESXi accessESXi

This diagram condenses GTIG’s observed order and does not assert that every deployment has the same layout. The pivot matters because the remote support appliance and vCenter hold different kinds of authority. Access to the first can reveal paths and credentials; control of the second can affect an entire virtualized estate.

What Happened on the Intermediate Linux Appliance?

GTIG reports that ARMORY CASTLE planted SLIMSAVAGE, a command-execution webshell, on an internal Linux appliance. About four hours later, the actor added CAGEMATCH, a separate webshell for staging transferred files. The roles were complementary: one ran commands while the other moved tooling into place.

The actor then escalated privileges to root and staged tools for the next move, according to GTIG. Its account describes BEARBONES as a modified SSH server that could bypass normal password validation and capture credentials. GTIG places BEARBONES after BONESAW and SAWSNAKE, before the actor moved laterally to the vCenter appliance.

These behaviors provide a useful investigation boundary. Review web server changes, unexpected command execution, new staging activity, privilege changes, and unusual SSH listeners on management-adjacent Linux systems. Off-host logs matter because an intruder with root access can change or remove local evidence.

BeyondTrust recommends forwarding appliance syslog and session events to a SIEM in near real time. It says the actor deleted local logs during its investigation. That advice also supports the Linux and vCenter review: preserve independent records before rebuilding or changing access.

How Did CVE-2026-123890 Change the Level of Access?

Broadcom describes CVE-2026-123890 as a critical authentication bypass in VMware Directory Service. An actor with network access to vCenter may gain unauthorized access, and Broadcom gives it a CVSS 3.1 base score of 9.8. The advisory lists no workaround and directs customers to fixed versions. Broadcom and NVD give a CVSS 3.1 score; neither record provides a CVSS 4.0 score for this flaw.

GTIG provides the campaign detail behind that advisory. It says BONESAW exploited the flaw to obtain an authenticated vCenter administrator session without a valid password. GTIG observed the tool create an SSO administrator account and extract directory data, enabling further movement into the server.

The root issue, as GTIG explains it, is a cryptographic and authorization failure in the vCenter directory authentication flow. The flow disclosed information that let the attacker establish an administrator session. This summary deliberately omits the protocol steps and tool options that would turn the finding into an exploitation recipe.

GTIG dates BONESAW execution against a vCenter server to early September 2026. It also recovered a July build timestamp, while cautioning that build metadata can be modified. Broadcom’s November 19 disclosure date marks public notice and available fixes; it is not the date of the observed intrusion.

After BONESAW, GTIG observed SAWSNAKE, a separate SAML utility. The report says it could use stolen signing material to forge authentication assertions and obtain administrative sessions. Treat unexpected SSO account creation and privileged sessions as potential persistence, even after the vulnerable service is patched.

Which vCenter Versions Need a Patch?

Broadcom’s VMSA-2026-0009 response matrix names the fixed releases below for CVE-2026-123890. Match the installed branch and product to the advisory before scheduling the change. The same advisory also covers other CVEs, so use the row for this specific authentication bypass.

Product branch Broadcom response
VMware Cloud Foundation or vSphere Foundation vCenter 9.1.x Update to 9.1.1.0200
VMware Cloud Foundation or vSphere Foundation vCenter 9.0.x Update to 9.0.2.0200
VMware vCenter 8.0 Update to 8.0 U3m
VMware vCenter 7.0 Contact Broadcom Support if an extended support contract applies
VMware Cloud Foundation vCenter 5.x Update to 5.2.5
Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2; Telco Cloud Infrastructure 3.0 Follow Broadcom KB463116

The affected row includes vCenter 7.0, but Broadcom does not give a general fixed version in that row. Its instruction is to contact support under extended support. Telco deployments also have a separate knowledge-base path rather than a version number in this matrix.

Patch records should include the actual installed build after the maintenance window. Confirm each vCenter node and linked management plane against its own branch. A successful installer run alone does not establish that the vulnerable deployment is now on Broadcom’s fixed release.

What Did the Actor Do After Reaching vCenter and ESXi?

GTIG observed the actor enable SSH on vCenter, connect with a newly created administrator account, and extract sensitive credentials. It then observed authentication to an ESXi host and further filesystem reconnaissance. Those actions turn the vCenter event into a broader virtualization incident.

On ESXi, GTIG saw the actor examine VMFS volumes and guest virtual machine data. The report also describes use of vmfs_browser.py, an existing tool used to inspect virtual disk contents. This is observed misuse of a separate tool, not one of the five newly identified malware families.

GTIG says the actor staged data on the host and moved it back through the compromised environment. It also observed LAZYBONES on another Linux appliance. GTIG had reported that backdoor in an earlier ARMORY CASTLE intrusion; the five newly identified families here are SLIMSAVAGE, CAGEMATCH, BEARBONES, BONESAW, and SAWSNAKE.

The ARMORY CASTLE actor profile gives context for the group’s earlier activity. The current investigation should rely on local evidence of access, accounts, and data movement. Shared tool names or a matching behavioral pattern alone cannot attribute a different incident to the same actor.

What Should Defenders Check Across the Chain?

Begin with self-hosted Remote Support exposure and BT26-05 patch state, then inventory every reachable vCenter deployment. Prioritize Broadcom’s fixed versions because the advisory gives no workaround. Restrict management access to trusted networks while preparing the change and preserve off-host records for the suspected interval.

Next, correlate Remote Support sessions with internal scans, Linux appliance changes, vCenter directory events, and ESXi access. Look for newly created SSO administrators, unusual privileged sessions, changes to SSH availability, and access to directory or credential stores. GTIG’s sequence gives the order; each environment needs its own timestamps and corroborating logs.

Defender review sequence
  • Inventory and patchMatch each vCenter branch to VMSA-2026-0009 and verify the installed build.
  • Preserve evidenceRetain Remote Support, Linux, vCenter, identity, and ESXi logs outside affected appliances.
  • Review identitiesInvestigate unexpected SSO administrators, privileged sessions, SSH changes, and credential access.
  • Scope data accessCorrelate VMFS and guest data activity with authorized maintenance and incident records.

If suspicious access is confirmed, assess the SSO signing material and administrative accounts with the incident team. Patching closes the listed flaw, but it cannot remove accounts, sessions, or stolen credentials created during an earlier compromise. The incident response plan template can help assign evidence and recovery owners.

GTIG did not assign ATT&CK identifiers to this report. Analysts should map its observations to local asset, identity, and log evidence before treating any technique as confirmed.

What Do Public Mentions Establish?

Brandefense Blackhole counted 25 dark-chat posts matching CVE-2026-102764 and one matching CVE-2026-123890 from August 21 through November 19, 2026. The units are matching posts per CVE, and the searches may overlap. These counts do not identify unique actors, affected organizations, or the timing of GTIG’s observed intrusion.

A separate GitHub search counted three public repositories naming CVE-2026-102764. The unit is repository names in the prepared search, not verified exploit attempts or active infections. Those observations justify monitoring discussion, while GTIG’s forensic account remains the evidence for this campaign’s exploitation.

The defender decision is clear even with attribution limits: patch affected vCenter branches and investigate whether the management plane was accessed before the patch. Follow the chain across appliances and identities rather than treating vCenter as an isolated server. The highest-value evidence is the correlation between entry, privilege, SSO, and ESXi activity.

Frequently Asked Questions

When did ARMORY CASTLE exploit the vCenter flaw?

GTIG says forensic evidence places BONESAW exploitation in early September 2026. Broadcom publicly disclosed CVE-2026-123890 on November 19, 2026.

Does patching vCenter close the entire incident?

A patch remediates the listed flaw. Investigate unexpected SSO accounts, privileged sessions, exposed credentials, and ESXi access because those effects can persist.

Which vCenter releases fix CVE-2026-123890?

Broadcom lists 9.1.1.0200, 9.0.2.0200, and 8.0 U3m for their respective branches. Other product branches have separate response instructions in VMSA-2026-0009.

Sources

  1. Google Threat Intelligence Group, ARMORY CASTLE Exploits vSphere, November 19, 2026
  2. Broadcom, VMSA-2026-0009, November 19, 2026
  3. BeyondTrust, ARMORY CASTLE and BT26-05: What Security Teams Need to Know
  4. NVD, CVE-2026-123890 record
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →