Dell Zero-Day Exploited for Two Years by Chinese Spies to Steal Data

Dell Patches Critical RecoverPoint Zero-Day (CVE-2026-22769) Actively Exploited by China-Nexus Group UNC6201

CRITICAL
February 17, 2026
6m read
VulnerabilityThreat ActorCyberattack

Related Entities

Threat Actors

UNC6201

Organizations

Dell Google Threat Intelligence GroupMandiant CISA VMware

Other

GRIMBOLTBRICKSTORMSLAYSTYLE

CVE Identifiers

CVE-2026-22769
CRITICAL
CVSS:10

Full Report

Executive Summary

On February 17, 2026, Dell disclosed a critical zero-day vulnerability, CVE-2026-22769, affecting its RecoverPoint for Virtual Machines product. The vulnerability, which scores a maximum 10.0 on the CVSS scale, is due to hardcoded credentials. Investigations by Google's Threat Intelligence Group and Mandiant revealed that a suspected China-nexus cyberespionage group, tracked as UNC6201, has been actively exploiting this flaw since at least mid-2024. The attackers used this access to deploy webshells and stealthy backdoors, including BRICKSTORM and a new malware called GRIMBOLT, for long-term persistence and data access. Dell has released patch 6.0.3.1 HF1, and all customers are urged to apply it immediately.


Threat Overview

The vulnerability resides in the RecoverPoint for Virtual Machines appliance, a solution used for backup and recovery in VMware environments. The core issue is the presence of hardcoded credentials, which allows an unauthenticated remote attacker to gain access to the appliance's underlying operating system with root privileges.

The threat actor, UNC6201, demonstrated a sophisticated attack chain:

  1. Initial Access: The actor exploited CVE-2026-22769 by using the hardcoded credentials to log into the appliance's embedded Apache Tomcat Manager.
  2. Webshell Deployment: Once authenticated, the attackers deployed a webshell known as SLAYSTYLE to establish a persistent command and control channel.
  3. Payload Delivery: Using the webshell, the actor installed multiple malware families to solidify their foothold. This included BRICKSTORM, a known stealthy backdoor, and GRIMBOLT, a new C#-based backdoor.
  4. Evasion and Persistence: The GRIMBOLT backdoor is notable for being compiled using native ahead-of-time (AOT) compilation, a technique designed to hinder reverse engineering and analysis. This allowed the actor to maintain long-term, undetected access for cyberespionage purposes.

The two-year gap between the start of exploitation and public disclosure highlights the effectiveness of the actor's stealth techniques and the critical danger posed by hardcoded credentials in enterprise products.

Technical Analysis

The attack leverages several techniques mapped to the MITRE ATT&CK framework:

  • T1190 - Exploit Public-Facing Application: The initial attack vector was the exploitation of the vulnerable RecoverPoint appliance accessible over the network.
  • T1552.004 - Hardcoded Credentials: The root cause of the vulnerability is hardcoded credentials within the product, which the attackers used for initial access.
  • T1505.003 - Web Shell: The deployment of the SLAYSTYLE webshell on the compromised Apache Tomcat server provided the attackers with persistent access and a platform to execute further commands.
  • T1105 - Ingress Tool Transfer: The attackers transferred their backdoors (BRICKSTORM, GRIMBOLT) to the compromised system after gaining initial access.
  • T1027 - Obfuscated Files or Information: The use of native AOT compilation for the GRIMBOLT backdoor is a form of obfuscation intended to make analysis more difficult.

Impact Assessment

The exploitation of CVE-2026-22769 poses a severe risk to organizations. Since RecoverPoint appliances are deeply integrated into virtualization infrastructure and have access to critical backup data, a compromise can have catastrophic consequences:

  • Data Theft: Attackers can access or exfiltrate sensitive data from virtual machine backups.
  • Ransomware Deployment: Although this campaign was focused on espionage, the same access could be used to destroy backups and deploy ransomware across the virtual environment.
  • Lateral Movement: The compromised appliance serves as a powerful pivot point into the broader corporate network.
  • Long-Term Espionage: The stealthy nature of the backdoors allows for long-term, undetected monitoring and data exfiltration, which is consistent with the objectives of a nation-state actor like UNC6201. Given the appliance's role, business impact includes significant data recovery costs, regulatory fines for data breaches, and loss of intellectual property.

Cyber Observables for Detection

Security teams should hunt for the following indicators:

Type Value Description
url_pattern /manager/html Suspicious or unauthorized access attempts to the Apache Tomcat Manager interface on RecoverPoint appliances.
process_name java Look for Java processes associated with Tomcat spawning anomalous child processes (e.g., sh, bash, cmd.exe).
file_path /usr/local/tomcat/webapps/ Monitor for newly created or modified JSP, WAR, or other executable files in Tomcat web application directories, indicative of webshells like SLAYSTYLE.
network_traffic_pattern Outbound C2 from RecoverPoint appliance Any outbound network connections from the RecoverPoint appliance to non-Dell or non-standard IP addresses should be considered highly suspicious.
command_line_pattern *ncaot* Search for command-line artifacts related to the execution of C#/.NET native AOT compiled binaries like GRIMBOLT.

Detection & Response

  • Log Analysis: Immediately review access logs for the RecoverPoint appliance's web interface and Apache Tomcat logs. Search for successful logins from unknown IP addresses or unusual user agents, especially to the /manager/html path.
  • Endpoint Detection (EDR): If possible, deploy EDR agents or monitoring tools on the appliance's underlying OS. Hunt for suspicious processes, file creation events in web directories, and outbound network connections.
  • Network Monitoring: Use network traffic analysis to baseline normal traffic from the RecoverPoint appliance. Alert on any connections to suspicious or non-standard external destinations. Reference D3FEND technique D3-NTA - Network Traffic Analysis.
  • File Integrity Monitoring: Check the integrity of all files in the Tomcat web directories. Compare file hashes against known-good versions to identify webshells or other malicious modifications.

Mitigation

  • Immediate Patching: The primary mitigation is to apply Dell's patch (version 6.0.3.1 HF1 or later) immediately. This is a critical action. Reference D3FEND technique D3-SU - Software Update.
  • Network Isolation: If patching is not immediately possible, restrict network access to the RecoverPoint management interface. It should only be accessible from a trusted management network or specific administrative jump hosts. Do not expose this interface to the internet. Reference D3FEND technique D3-NI - Network Isolation.
  • Credential Management: As a general best practice, enforce strong, unique passwords for all management interfaces and disable or change any default credentials. While this specific flaw was hardcoded, the principle remains vital. Reference D3FEND technique D3-SPP - Strong Password Policy.
  • Assume Compromise: Given the long exploitation window, organizations should consider appliances that were unpatched and accessible as potentially compromised. A full incident response investigation may be warranted.

Timeline of Events

1
June 1, 2024
Active exploitation of CVE-2026-22769 by UNC6201 is believed to have begun around this time.
2
February 17, 2026
Dell issues a security advisory and releases a patch for CVE-2026-22769.
3
February 17, 2026
This article was published

MITRE ATT&CK Mitigations

Applying the vendor-supplied patch (6.0.3.1 HF1) is the most effective way to remediate the vulnerability.

Restricting network access to the RecoverPoint management interface to only trusted administrative hosts significantly reduces the attack surface.

While the flaw was hardcoded, this incident underscores the importance of eliminating default or weak credentials from all systems. This mitigation encourages a culture of strong credential management.

Audit

M1047enterprise

Regularly auditing access logs for critical appliances can help detect anomalous or unauthorized login attempts before a full compromise occurs.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

zero-dayhardcoded credentialscyberespionageVMwarebackup securityUNC6201

📢 Share This Article

Help others stay informed about cybersecurity threats