Windows ImageLoad of DLL from spoolsv.exe spool drivers subfolders

Flags spoolsv.exe DLL loads originating from Print Spooler x64\3/x64\4 driver folders on Windows.

FreeReviewedSigma · Informational · v5
Product
windows
Category
image_load
Author
FPT.EagleEye, Thomas Patzke (improvements) (SigmaHQ), DRL 1.1
Published
2021-06-29
Updated
2026-07-31

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule flags DLL loads where the initiating image is spoolsv.exe and the loaded module path matches specific spool driver x64 subfolders. Such behavior can indicate print spooler abuse or persistence attempts that load additional code through the spooler service. It relies on Windows image load telemetry that includes both the initiating Image and the ImageLoaded path for .dll modules.

Related detections9 linkedT1574 — drag to rearrange
Suspicious Execution or Load from Fake System32 Directory Imprint (via process_creation)
Suspicious LD_PRELOAD Library Injection via PUMAKIT Userland Rootkit
Windows DLL Search Order Hijacking: Suspicious DLL Writes to App Dependency Folders
Windows Registry Persistence: DbgManagedDebugger Debugger Value Added
Windows Suspicious DLL Deletion in Spooler Driver Folder (PrintNightmare/CVE-2021-1675)
Windows DLL execution via register-cimprovider.exe with -path dll
Windows Registry Printer Driver Installations with Empty Manufacturer Field
Windows Process Creation: Suspicious SetupComplete.cmd execution for CVE-2019-1378 exploitation
Windows regsvr32 Executes DLL with Uncommon Extension in Command Line
Windows ImageLoad of DLL from spoolsv.exe spool drivers subfolders
Pivot detection · T1574 · 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.