Windows: Detect .SCR screen saver file creation outside common system directories

Alerts on creation of .scr screen saver files in unusual locations on Windows.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
Christopher Peacock @securepeacock, SCYTHE @scythe_io (SigmaHQ), DRL 1.1
Published
2022-04-27
Updated
2026-07-31

ATT&CK techniques

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

This rule flags file creation events where the target filename ends with .scr and the file is not located in typical Windows system folders. Creating screensaver files in unusual paths can be used to stage or execute code under the screensaver file extension. It relies on Windows file event telemetry that includes the target filename for write/create operations.

Related detections9 linkedT1218.011 — drag to rearrange
Malicious Zardoor Backdoor Execution via rundll32 (via process_creation)
Malicious Rundll32 Loading an Export From a User Path (via process_creation)
Renamed Regsvr32 or Rundll32 Loading a DLL With a Non-Standard Extension (via process_creation)
Malicious Rundll32 DllRegisterServer Execution From a User-Writable Path (via process_creation)
IMEEX Framework DLL Execution via Rundll32 Loading imaadp (via process_creation)
Suspicious Persistence via pcalua Launching rundll32 Control_RunDLL
Suspicious Rundll32 Executing DLL Start Export With Control Flags
Suspicious Rundll32 Execution of Timestamp-Named DLL
Suspicious Rundll32 Loading DLL from LocalAppData with Short Export (via process_creation)
Windows: Detect .SCR screen saver file creation outside common system directories
Pivot detection · T1218.011 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.