Techniques › T1546.002 › AN0441
AN0441 Analytic 0441
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Unusual screensaver (.scr) executions correlated with recent registry modifications to HKCU\Control Panel\Desktop values such as SCRNSAVE.exe, ScreenSaveTimeout, and ScreenSaveActive. Detection focuses on PE image paths not consistent with known legitimate screensavers and triggered after user inactivity timeout.</p>
- Detects
- T1546.002 Screensaver
- Part of
- DET0154 Detect Screensaver-Based Persistence via Registry and Execution Chains
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| WinEventLog:Security | EventCode=4688 | DC0032 Process Creation |
| WinEventLog:Sysmon | EventCode=13, 14 | DC0063 Windows Registry Key Modification |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
TimeWindow | Adjust the user inactivity threshold that defines 'screensaver trigger window'; shorter timeouts may increase sensitivity. |
SuspiciousPathRegex | Allow tuning based on expected paths for legitimate .scr files vs suspicious locations (e.g., user temp directories). |
ParentProcessAllowList | Allowlisting known legitimate initiators of .scr files (e.g., user32.dll context) to reduce false positives. |
RegistryEditorProcessName | Monitor for registry modification performed by unusual processes (e.g., powershell.exe, reg.exe). |