Windows grpconv Utility Execution with Output Option

Alerts on Windows process command lines invoking GrpConv with -o, potentially for .grp conversion or persistence.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-05-19
Updated
2026-07-31

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 flags Windows process creation events where the command line contains an invocation of grpconv.exe with an output option ("grpconv.exe -o" or "grpconv -o"). Attackers may use this utility to convert legacy Windows 3.x .grp files or as part of persistence-related activity, making abnormal utility execution noteworthy. It relies on process creation telemetry, specifically the recorded command line for the spawned grpconv process.

Related detections9 linkedT1547 — drag to rearrange
Malicious MuddyRot Payload Drop in ProgramData SoftwareMemory Directory
Malicious ELAM Driver Disable via Bcdedit
Suspicious Lunar Backdoor State File Creation via File System
Suspicious Udev Rule Reload After Rules Directory Modification
Malicious TELEPUZ DLL Persistence via Masqueraded Loader in User Path
Suspicious Boot Verification Program Persistence via Registry (via registry_set)
SwimSnake Driver Execution Persistence via Session Manager PlatformExecute (via registry_set)
Suspicious Session Manager Execute Value Modification for Persistence (via registry_set)
Suspicious RDP Wds StartupPrograms Persistence Modification (via registry_set)
Windows grpconv Utility Execution with Output Option
Pivot detection · T1547 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.