Windows Registry Event: Pandemic implant key path contains null Instance

Detects registry activity targeting CurrentControlSet\services\null\Instance, associated with Windows implant persistence staging.

FreeReviewedSigma · Critical · v5
Product
windows
Category
registry_event
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-06-01
Updated
2026-07-31

ATT&CK techniques

C2
  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. Exfiltration

  13. Impact

What it detects

This rule matches Windows registry events where the TargetObject contains the path fragment \SYSTEM\CurrentControlSet\services\null\Instance. Attackers that use registry-based persistence or configuration changes may write service-related keys, making this a high-signal indicator of implant deployment. Telemetry relies on registry event logs that capture the TargetObject value for write or modification operations on Windows.

Related detections9 linkedT1105 — drag to rearrange
Suspicious Curl Download From Sysinternals Live Service (via process_creation)
Suspicious Remote Script Transfer via Bitsadmin (via process_creation)
Suspicious PowerShell Download Cradle via ClickFix Fake CAPTCHA (via process_creation)
Malicious Curl MSI Download to ProgramData via Process Creation
Suspicious CloudZ RAT Payload Download via curl to ProgramData
Suspicious Velociraptor Agent Deployment via msiexec From Cloud Storage
Suspicious PowerShell Download of lib.zip Archive
Suspicious File Download Via Bitsadmin Transfer
Suspicious PowerShell Download Of Text-Disguised Payload
Windows Registry Event: Pandemic implant key path contains null Instance
Pivot detection · T1105 · 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.