huntrule

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
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

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.

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