EtherRAT Persistence via WindowsHost Run Key (via registry_set)

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-07-27
Updated
2026-08-28

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects EtherRAT establishing autostart persistence through a WindowsHost value under the CurrentVersion Run key that points to conhost or node executing the backdoor, a persistence behavior seen in The Gentlemen intrusions. Adversaries leverage Run key entries so the Node.js backdoor relaunches at every user logon.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Internet Shortcut URL File Registered for Run Key Persistence (via registry_set)
Malicious Run Key Persistence Named SystemAgentService
Suspicious Run Key Persistence Pointing to ProgramData Executable (via registry_set)
Suspicious Run Key Persistence Pointing to WScript via PhantomVAI Loader (via registry_set)
Suspicious Run Key Persistence Named Updater
Suspicious Run Key Persistence Executing VBScript as WindowsSecurityCheck
Suspicious RunOnce Persistence Pointing to User AppData
Malicious FalseFont Backdoor Run Key Persistence from AppData (via registry_set)
Malicious Registry Run Key Persistence via AHealthDB by Stately Taurus
EtherRAT Persistence via WindowsHost Run Key (via registry_set)
Pivot detection · T1547.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.