Potential Protocol Tunneling via Yuze

 1[metadata]
 2creation_date = "2026/03/18"
 3integration = ["endpoint", "windows", "sentinel_one_cloud_funnel", "m365_defender", "system", "crowdstrike"]
 4maturity = "production"
 5updated_date = "2026/03/18"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10Identifies execution of Yuze, a lightweight open-source tunneling tool used for intranet penetration. Yuze supports
11forward and reverse SOCKS5 proxy tunneling and is typically executed via rundll32 loading yuze.dll with the RunYuze
12export. Threat actors may use it to proxy C2 or pivot traffic.
13"""
14from = "now-9m"
15index = [
16    "endgame-*",
17    "logs-crowdstrike.fdr*",
18    "logs-endpoint.events.process-*",
19    "logs-m365_defender.event-*",
20    "logs-sentinel_one_cloud_funnel.*",
21    "logs-system.security*",
22    "logs-windows.sysmon_operational-*",
23    "winlogbeat-*",
24]
25language = "eql"
26license = "Elastic License v2"
27name = "Potential Protocol Tunneling via Yuze"
28note = """## Triage and analysis
29
30### Investigating Potential Protocol Tunneling via Yuze
31
32Yuze is a C-based tunneling tool used for intranet penetration and supports forward and reverse SOCKS5 proxy tunneling. It is commonly executed as `rundll32 yuze.dll,RunYuze reverse -c <ip>:<port>` and has been observed in threat actor campaigns.
33
34### Possible investigation steps
35
36- Confirm the command line contains `yuze.dll` and `RunYuze`; typical form is `rundll32 yuze.dll,RunYuze reverse -c <ip>:<port>`.
37- Extract the remote endpoint from the `-c` argument (C2 or relay) and look up the IP/domain in threat intelligence.
38- Locate where yuze.dll was loaded from; check file creation time to see if it was recently dropped.
39- Identify the parent process that started rundll32 (script, scheduled task, exploit, etc.) to understand the execution chain.
40- Correlate with network events for outbound connections from this host to the IP/port in the command line.
41
42### False positive analysis
43
44- Legitimate use of Yuze is rare; most hits are likely malicious or red-team. If you use Yuze for authorized testing, consider an exception by host or user.
45
46### Response and remediation
47
48- Isolate the host and terminate the rundll32 process.
49- Remove yuze.dll from disk and hunt for other copies or related artifacts.
50- Block the C2/relay IP or domain at DNS/firewall; rotate credentials if the tunnel was used for access.
51"""
52references = [
53    "https://attack.mitre.org/techniques/T1572/",
54    "https://github.com/P001water/yuze",
55    "https://www.trendmicro.com/tr_tr/research/26/c/dissecting-a-warlock-attack.html",
56]
57risk_score = 47
58rule_id = "e7f2c4a1-9b3d-5e8f-c6a0-2d1b4e7f8c3a"
59severity = "medium"
60tags = [
61    "Domain: Endpoint",
62    "OS: Windows",
63    "Use Case: Threat Detection",
64    "Tactic: Command and Control",
65    "Resources: Investigation Guide",
66    "Data Source: Elastic Defend",
67    "Data Source: Sysmon",
68    "Data Source: SentinelOne",
69    "Data Source: Microsoft Defender for Endpoint",
70    "Data Source: Crowdstrike", 
71    "Data Source: Elastic Endgame", 
72    "Data Source: Windows Security Event Logs"
73]
74timestamp_override = "event.ingested"
75type = "eql"
76
77query = '''
78process where host.os.type == "windows" and event.type == "start" and
79  ( 
80    (process.args : "reverse" and process.args : ("-c", "-s")) or 
81    (process.args : ("proxy", "fwd") and process.args : "-l") 
82   ) and 
83  (?process.code_signature.exists == false or process.name : "rundll32.exe")
84'''
85
86
87[[rule.threat]]
88framework = "MITRE ATT&CK"
89[[rule.threat.technique]]
90id = "T1572"
91name = "Protocol Tunneling"
92reference = "https://attack.mitre.org/techniques/T1572/"
93
94[rule.threat.tactic]
95id = "TA0011"
96name = "Command and Control"
97reference = "https://attack.mitre.org/tactics/TA0011/"