Got Incident? Investigate 60 million events < 1 minute

LogTotal for Incident Response, Complete Enterprise Platform Access is Live

Buy 7-day IR Retainer Pass for $799

SOC Prime Bias: Critical

20 Nov 2026 14:14 UTC

ARMORY CASTLE Exploits CVE-2026-123890 and CVE-2026-102764

Author Photo
SOC Prime Team linkedin icon Follow
ARMORY CASTLE Exploits CVE-2026-123890 and CVE-2026-102764
shield icon

Detection stack

  • AIDR
  • Alert
  • ETL
  • Query

Summary

The PRC-nexus threat actor ARMORY CASTLE is exploiting zero-day vulnerabilities in BeyondTrust Remote Support and VMware vCenter Server to establish persistence and exfiltrate sensitive data. The campaign uses specialized Golang-based tools such as BONESAW and SAWSNAKE to bypass authentication and abuse SAML tokens. The actor demonstrates deep platform knowledge by deploying customized malware across Linux appliances and ESXi hosts.

Investigation

Mandiant and Google Threat Intelligence Group (GTIG) investigated recent activity involving exploitation of CVE-2026-102764 and CVE-2026-123890. Forensic analysis identified the BONESAW utility supporting remote exploitation alongside several custom malware families. Researchers traced lateral movement from compromised Remote Support devices to internal Linux appliances and subsequently into VMware vCenter and ESXi environments.

Mitigation

Organizations should immediately apply Broadcom security updates addressing VMware vCenter vulnerabilities. Deploying the VCSA Hardening & Logging Tool is strongly recommended to enforce granular iptables controls at the kernel level. A Zero Trust architecture, combined with strict egress filtering and isolation of management interfaces, can significantly disrupt the observed attack chain.

Response

When malicious activity is detected, organizations should isolate affected vCenter and ESXi environments and review VAMI API logs for unauthorized SSH activation. Conduct comprehensive hunting for known webshells such as SLIMSAVAGE and CAGEMATCH, as well as custom backdoors including BEARBONES and LAZYBONES. Validate SAML signing keys and audit newly created SSO administrator accounts for unauthorized access.

Attack Flow

We are still updating this part.

Detections

Downloads to Suspicious Folders (via cmdline)

SOC Prime Team
20 Nov 2026

Remote File Upload / Download via Standard Tools (via cmdline)

SOC Prime Team
20 Nov 2026

Archive Was Created In Linux Tmp Folder (via file_event)

SOC Prime Team
20 Nov 2026

Possible Base64 Encoded Strings Manipulation (via cmdline)

SOC Prime Team
20 Nov 2026

IOCs (HashSha256) to detect: ARMORY CASTLE Exploits vSphere

SOC Prime AI Rules
20 Nov 2026

IOCs (SourceIP) to detect: ARMORY CASTLE Exploits vSphere

SOC Prime AI Rules
20 Nov 2026

IOCs (DestinationIP) to detect: ARMORY CASTLE Exploits vSphere

SOC Prime AI Rules
20 Nov 2026

ARMOY CASTLE Privilege Escalation and Reconnaissance in vCenter Exploitation [Linux Process Creation]

SOC Prime AI Rules
20 Nov 2026

Simulation Execution

  • Attack Narrative & Commands: An attacker has gained initial access to a Linux-based vCenter component. To escalate privileges, they attempt to write a malicious GDB payload using a base64 encoded string to bypass simple string filters. Once privileges are gained, the attacker performs internal reconnaissance using nmap to scan for VMware-specific ports (443, 2012, 389) to identify further targets for lateral movement. Finally, they attempt to trigger a known application vulnerability pattern associated with the Slimavage exploit.

  • Regression Test Script:

      #!/bin/bash
      # ARMORY CASTLE Simulation Script
    
      echo "[+] Starting ARMORY CASTLE Simulation..."
    
      # 1. Simulate Base64 GDB Payload Injection
      echo "[+] Executing Base64 payload injection..."
      /bin/sh -c echo IWNobW9kIHUrcyAvYmluL2VudgpxCg== | base64 -d > /tmp/gdb_file
    
      # 2. Simulate Nmap Reconnaissance
      echo "[+] Executing Nmap reconnaissance..."
      /usr/sbin/nmap -sS -p 443,2012,389 --open 127.0.0.1
    
      # 3. Simulate Slimavage Pattern (Simulated via echo to represent the process string)
      # Note: Since we cannot easily trigger a Java ProcessBuilder via Bash, 
      # we simulate the string presence in a command context.
      echo "[+] Executing Slimavage pattern simulation..."
      echo "ProcessBuilder('/bin/sh', '-c', request.getParameter('i'))" > /tmp/slimavage_sim.txt
      cat /tmp/slimavage_sim.txt
  • Cleanup Commands:

      #!/bin/bash
      # Cleanup Simulation Artifacts
      rm -f /tmp/gdb_file
      rm -f /tmp/slimavage_sim.txt
      echo "[+] Cleanup complete."