MITRE ATT&CK T1546.002: Screensaver
When to use this skill
Use this skill when the task involves T1546.002, Screensaver, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1546.002
- Technique name: Screensaver
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1546/002
- Tactics: persistence, privilege-escalation
- Platforms: Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may establish persistence by executing malicious content triggered by user inactivity. Screensavers are programs that execute after a configurable time of user inactivity and consist of Portable Executable (PE) files with a .scr file extension.(Citation: Wikipedia Screensaver) The Windows screensaver application scrnsave.scr is located in C:\Windows\System32</code>, and C:\Windows\sysWOW64</code> on 64-bit Windows systems, along with screensavers included with base Windows installations.
The following screensaver settings are stored in the Registry (HKCU\Control Panel\Desktop</code>) and could be manipulated to achieve persistence:
- SCRNSAVE.exe - set to malicious PE path
- ScreenSaveActive - set to '1' to enable the screensaver
- ScreenSaverIsSecure - set to '0' to not require a password to unlock
- ScreenSaveTimeout - sets user inactivity timeout before screensaver is executed
Adversaries can use screensaver settings to maintain persistence by setting the screensaver to run malware after a certain timeframe of user inactivity.(Citation: ESET Gazer Aug 2017)
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Disable or Remove Feature or Program
- Execution Prevention
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
ATT&CK contributors
1---2name: attack-ent-t1546-002-screensaver3description: "Analyze MITRE ATT&CK T1546.002 Screensaver in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1546.002, Screensaver, or enterprise ATT&CK. Adversaries may establish persistence by executing malicious content triggered by user inactivity."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1546-002-screensaver7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1546.00210 attack_stix_id: attack-pattern--ce4b7013-640e-48a9-b501-d0025a95f4bf11 attack_version: "1.3"12 attack_modified: "2025-10-24T17:49:24.634Z"13---1415# MITRE ATT&CK T1546.002: Screensaver1617## When to use this skill1819Use this skill when the task involves T1546.002, Screensaver, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T1546.00225- Technique name: Screensaver26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1546/00228- Tactics: persistence, privilege-escalation29- Platforms: Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may establish persistence by executing malicious content triggered by user inactivity. Screensavers are programs that execute after a configurable time of user inactivity and consist of Portable Executable (PE) files with a .scr file extension.(Citation: Wikipedia Screensaver) The Windows screensaver application scrnsave.scr is located in <code>C:\Windows\System32\</code>, and <code>C:\Windows\sysWOW64\</code> on 64-bit Windows systems, along with screensavers included with base Windows installations.3738The following screensaver settings are stored in the Registry (<code>HKCU\Control Panel\Desktop\</code>) and could be manipulated to achieve persistence:3940* <code>SCRNSAVE.exe</code> - set to malicious PE path41* <code>ScreenSaveActive</code> - set to '1' to enable the screensaver42* <code>ScreenSaverIsSecure</code> - set to '0' to not require a password to unlock43* <code>ScreenSaveTimeout</code> - sets user inactivity timeout before screensaver is executed4445Adversaries can use screensaver settings to maintain persistence by setting the screensaver to run malware after a certain timeframe of user inactivity.(Citation: ESET Gazer Aug 2017)4647## Agent workflow48491. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.502. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.513. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.524. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.535. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.546. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.5556## Bundled resources5758- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.59- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.60- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.61- `templates/detection-brief.md`: detection engineering brief template.62- `templates/hunt-plan.md`: threat hunt plan template.63- `templates/incident-response-note.md`: incident response note template.64- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.65- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.66- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6768To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6970## Detection guidance7172No ATT&CK detection guidance was present in the source STIX object.7374## Useful telemetry and data sources7576- Not specified in the STIX object.7778## Mitigations to consider7980- Disable or Remove Feature or Program81- Execution Prevention8283## Known threat context8485Use these examples only as contextual leads, not as proof that an observed event is this technique:8687- Gazer (malware)8889## Recommended output pattern9091When responding with this skill, structure the answer as:9293- Assessment: whether the evidence supports this ATT&CK mapping and why.94- Evidence: specific indicators, logs, behaviors, and assumptions.95- Detection: telemetry sources, analytic logic, and tuning considerations.96- Response: containment, eradication, recovery, and validation actions.97- Coverage gaps: missing logs, sensors, controls, or environmental details.98- References: include the ATT&CK URL and any user-provided evidence references.99100## ATT&CK contributors101102- Bartosz Jerzman