huntrule

Windows Registry Markers for FlowCloud Malware Configuration and Keylogger Components

Detects registry activity referencing specific HARDWARE marker GUID keys and the Setup\PrintResponsor path on Windows.

FreeReviewedSigma · Critical · v5
Product
windows
Category
registry_event
Author
NVISO (SigmaHQ), DRL 1.1
Published
2020-06-09
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Persistence → Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies specific Windows registry paths used as markers for FlowCloud malware configuration storage alongside components consistent with a keylogger. Attackers may leverage these locations for persistence and to organize malware-related data, making registry telemetry valuable for early detection. The detection relies on Windows registry event logs that record TargetObject matches for the defined HARDWARE and SYSTEM keys.

Reporting behind it

Related detections9 linkedT1112 — drag to rearrange
Malicious Enabling of Restricted Admin Mode via Registry by UAT-8837
Suspicious Enabling of Remote Desktop via fDenyTSConnections Registry by DeadLock Ransomware
Malicious Service DLL Hijack for Persistence via Lotus Blossom
Suspicious Loopback Proxy Server Configured via Registry (via registry_set)
Malicious WDigest Credential Caching Enabled via Registry (via registry_set)
Suspicious Remote Desktop Enabled via fDenyTSConnections Registry by Sandworm
Malicious Gh0stBins RAT Registry Marker HHClient
Suspicious PebbleDash C2 Configuration Stored Under WMI Security Key (via registry_set)
Suspicious WDigest UseLogonCredential Enablement for Plaintext Credential Theft (via registry_set)
Windows Registry Markers for FlowCloud Malware Configuration and Keylogger Components
Pivot detection · T1112 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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