Windows Proxy Configuration via Netsh
The Volt Typhoon group utilizes the Windows netsh utility to establish covert network proxies, enabling persistence and traffic redirection through the portproxy interface.
The Volt Typhoon threat actor group leverages the built-in Windows utility netsh.exe to configure network proxies on compromised hosts. By utilizing the portproxy and v4tov4 command-line parameters, attackers can intercept and redirect network traffic to unauthorized destinations. This technique is frequently employed as a mechanism for maintaining persistence and establishing covert Command and Control (C2) channels. The use of native binaries for malicious purposes, often referred to as Living-off-the-Land (LotL), allows the actor to blend in with legitimate system administration activities and evade signature-based detection. Defenders must prioritize the monitoring of netsh.exe execution, specifically when it involves arguments related to port forwarding, to identify potential unauthorized network configuration changes.
Attack Chain
- Attacker gains initial access to a target Windows system.
- Attacker executes
netsh.exewith administrative privileges. - Attacker runs
netsh interface portproxy add v4tov4to define a new proxy listener. - The system registers the listener, effectively creating a persistent network redirector.
- The proxy listener forwards inbound traffic to the specified C2 infrastructure.
- Attacker maintains covert connectivity while minimizing the footprint of additional malicious binaries.
Impact
Successful implementation of this technique allows threat actors to maintain persistent, covert access to critical infrastructure. The primary risk involves the manipulation of network communications and the potential for long-term data exfiltration. If left unmonitored, this behavior facilitates unauthorized ingress into enterprise environments and provides a robust C2 channel for the actor to continue their operations undetected.
Recommendation
- Deploy the Sigma rule below to detect unauthorized
netsh.exeusage and tune it against known administrative VPN clients. - Enable comprehensive process creation auditing (Sysmon Event ID 1 or Windows Event ID 4688) to capture command-line arguments.
- Filter and alert on
netsh.exeinvocations containingportproxyorv4tov4parameters, as this activity is highly abnormal in standard operational environments.
Immediate actions
Deploy Sigma rule to detect netsh portproxy configurations
Threat Hunt
Search historical logs for netsh.exe executions containing portproxy
Data: Process creation events with command-line arguments
Mitigations
Review and restrict administrative privileges for netsh configuration
T1090.001
Detection coverage 1
Detect Suspicious Netsh Portproxy Configuration
mediumDetects the use of netsh to configure a port proxy, often used for persistence or C2 traffic redirection.
Detection queries are available on the platform. Get full rules →