The Chinese state-sponsored threat actor Volt Typhoon has been linked to a data breach at a U.S. water utility, the Park County Water District. A joint advisory from CISA, the FBI, and the NSA confirms the group exploited a vulnerability in an internet-facing edge device to gain access. Following the initial breach, the actors employed 'living off the land' (LotL) tactics, using legitimate system tools to conduct reconnaissance and move laterally. The primary objective was espionage, as evidenced by the exfiltration of sensitive operational documents like engineering schematics. While the utility's OT network and water safety were not compromised, the incident underscores Volt Typhoon's persistent efforts to pre-position themselves within U.S. critical infrastructure for potential future disruptive operations.
Volt Typhoon's modus operandi is characterized by stealth and a reliance on legitimate tools to evade detection. By exploiting edge devices, they gain an initial foothold and then immediately pivot to using credentials and built-in Windows utilities. This makes their activity extremely difficult to distinguish from normal administrative behavior, allowing them to dwell in networks for long periods. The choice to steal operational documents rather than disrupt systems indicates a strategic intelligence-gathering mission, likely aimed at understanding and mapping vulnerabilities within U.S. critical infrastructure for future use.
The attack followed Volt Typhoon's established playbook:
T1190 - Exploit Public-Facing Application).T1078 - Valid Accounts).net, ipconfig, systeminfo) to map the IT network and identify sensitive data (T1018 - Remote System Discovery). They then moved laterally to access file servers and other systems.T1005 - Data from Local System).T1041 - Exfiltration Over C2 Channel).A key takeaway is Volt Typhoon's deliberate avoidance of malware. By using only legitimate tools already present on the system, they significantly reduce their forensic footprint and bypass many security products.
While there was no direct impact on the water supply or operational control systems, the strategic impact is significant. The exfiltration of engineering schematics and maintenance schedules provides a hostile nation-state with detailed blueprints of a U.S. critical infrastructure facility. This intelligence can be used to:
This incident is a clear example of pre-positioning, where an adversary gains access and knowledge to enable future offensive operations at a time of their choosing.
Detecting LotL activity requires a focus on behavior, not signatures.
| Type | Value | Description | Context |
|---|---|---|---|
command_line_pattern |
net user /domain, net group /domain |
Legitimate commands frequently used by Volt Typhoon for Active Directory reconnaissance. | Windows Event ID 4688, EDR logs. Look for execution by unusual accounts or from unusual source systems. |
log_source |
Firewall logs | Monitor for outbound connections from unexpected sources within the IT network, especially to known malicious infrastructure. | SIEM, Firewall/Proxy logs |
process_name |
wmic.exe, nltest.exe |
Other built-in Windows tools abused by Volt Typhoon for discovery and lateral movement. | EDR process creation logs |
event_id |
4624 (Successful Logon) |
Correlate logons across systems to identify anomalous lateral movement patterns, e.g., an IT helpdesk account logging into an engineering server. | Windows Security Event Logs in a SIEM |
Centralized Log Management.User Behavior Analysis (D3-UBA).Patching the vulnerability in the internet-facing appliance would have prevented the initial access.
Mapped D3FEND Techniques:
Proper IT/OT segmentation was effective in this incident, preventing the breach from impacting industrial control systems.
To detect stealthy 'living off the land' actors like Volt Typhoon, organizations must move beyond signature-based detection and implement robust behavioral analysis. This involves using EDR and identity security tools to establish a baseline of normal activity for users and systems. Detections should focus on anomalous sequences of legitimate commands. For example, a service account that normally only runs specific applications suddenly executing net.exe, whoami.exe, and nltest.exe is a major red flag. By analyzing the context—who is running the command, from what host, at what time, and in what sequence—security teams can identify the subtle indicators of a Volt Typhoon intrusion that would otherwise be lost in the noise of normal administrative activity.
Assume that initial access will eventually occur and focus on preventing the attacker from achieving their objectives. For an espionage actor like Volt Typhoon, this means blocking data exfiltration. Implement a default-deny policy for outbound network traffic from all servers, including those in the IT environment. Only allow connections to known, legitimate destinations required for patching, business operations, or administration. This 'egress filtering' makes it significantly more difficult for attackers to exfiltrate stolen data or establish command and control channels. While Volt Typhoon is known to proxy traffic through compromised SOHO routers, a strict egress policy can still disrupt their standard TTPs and increase the chances of detection.
The initial entry point for this attack was a vulnerable edge device. Critical infrastructure operators must have a rigorous program for hardening and managing all internet-facing systems. This includes disabling any unnecessary ports or services, changing default credentials, and, most importantly, maintaining an aggressive patching cadence. A comprehensive asset inventory is a prerequisite; you cannot protect what you do not know you have. Use EASM and vulnerability scanning tools to continuously identify and assess the security of the network perimeter. For an actor like Volt Typhoon that specializes in exploiting edge devices, a hardened perimeter is the most effective preventative control.

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.
Help others stay informed about cybersecurity threats