IMEEX Framework Configuration Persistence via IMEEX Registry Subkeys (via registry_set)

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-11-09
Updated
2026-11-09

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects the IMEEX framework writing its configuration under a Software\Microsoft\IMEEX registry path, where it stores XOR-encoded file paths, execution type and parameters in N, A and P subkeys. This uniquely named key hierarchy is not used by legitimate software and reveals the implant persisting its module configuration.

Related detections9 linkedT1112 — drag to rearrange
Suspicious Remote Desktop Disable via fDenyTSConnections Registry Modification (via registry_set)
Suspicious Offline Registry Hive Library Loaded from User-Writable Path for Stealth Persistence (via image_load)
Suspicious Autostart Persistence via Registry Run Key Pointing to a Script Interpreter (via registry_set)
Masquerading PNGPlug Loader Payload Path Storage via DICKEXEPATH Registry Value (via registry_set)
Suspicious System Tray Concealment via NoTrayItemsDisplay Registry Modification (via registry_set)
Malicious Rhadamanthys Stealer Execution-Delay Timestamp via SibCode Registry Key (via registry_set)
Suspicious RiseLoader Infection Marker Registry Key (via registry_set)
Suspicious OneNote Embedded File Open Warning Disabled via Registry
Malicious WDigest UseLogonCredential Cleartext Credential Enablement
IMEEX Framework Configuration Persistence via IMEEX Registry Subkeys (via registry_set)
Pivot detection · T1112 · 9 related

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