Windows Registry Ports Key Changes with Script/Binary File Indicators

Flags registry modifications to the Ports key with path- or executable/script-like details that may indicate printer-based exploitation attempts.

FreeReviewedSigma · High · v5
Product
windows
Category
registry_set
Author
EagleEye Team, Florian Roth (Nextron Systems), NVISO (SigmaHQ), DRL 1.1
Published
2020-05-13
Updated
2026-07-31

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

Detects registry updates to the Windows NT CurrentVersion "Ports" key where the entry details include Windows paths or suspicious executable/script-related extensions. Attackers may use this persistence or execution path by modifying printer port configuration to trigger code via the print spooler or related components. The rule relies on Windows registry set telemetry, matching the target key path and string indicators in the written value data.

Related detections9 linkedT1112 — drag to rearrange
Suspicious Registry Value under Console WindowsUpdates for C2 Storage
Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)
Suspicious PowerShell Payload Staging in HKCU Printers Registry Key
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Suspicious Disabling of Chromium App-Bound Encryption via Policy Registry Key (via registry_set)
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious ClickFix RunMRU Entry Recording LOLBIN Command from Run Dialog
Windows Registry Ports Key Changes with Script/Binary File Indicators
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.