MITRE ATT&CK T1547.004: Winlogon Helper DLL
When to use this skill
Use this skill when the task involves T1547.004, Winlogon Helper DLL, 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: T1547.004
- Technique name: Winlogon Helper DLL
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1547/004
- Tactics: persistence, privilege-escalation
- Platforms: Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may abuse features of Winlogon to execute DLLs and/or executables when a user logs in. Winlogon.exe is a Windows component responsible for actions at logon/logoff as well as the secure attention sequence (SAS) triggered by Ctrl-Alt-Delete. Registry entries in HKLM\Software[\Wow6432Node\]\Microsoft\Windows NT\CurrentVersion\Winlogon</code> and HKCU\Software\Microsoft\Windows NT\CurrentVersion\Winlogon</code> are used to manage additional helper programs and functionalities that support Winlogon.(Citation: Cylance Reg Persistence Sept 2013)
Malicious modifications to these Registry keys may cause Winlogon to load and execute malicious DLLs and/or executables. Specifically, the following subkeys have been known to be possibly vulnerable to abuse: (Citation: Cylance Reg Persistence Sept 2013)
- Winlogon\Notify - points to notification package DLLs that handle Winlogon events
- Winlogon\Userinit - points to userinit.exe, the user initialization program executed when a user logs on
- Winlogon\Shell - points to explorer.exe, the system shell executed when a user logs on
Adversaries may take advantage of these features to repeatedly execute malicious code and establish persistence.
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
- Execution Prevention
- User Account Management
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Bazar (malware)
- Cannon (malware)
- DarkTortilla (malware)
- Dipsind (malware)
- Gazer (malware)
- KeyBoy (malware)
- LockBit 3.0 (malware)
- Qilin (malware)
- Remexi (malware)
- Revenge RAT (malware)
- Tropic Trooper (intrusion-set)
- Turla (intrusion-set)
- Wizard Spider (intrusion-set)
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-t1547-004-winlogon-helper-dll3description: "Analyze MITRE ATT&CK T1547.004 Winlogon Helper DLL in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1547.004, Winlogon Helper DLL, or enterprise ATT&CK. Adversaries may abuse features of Winlogon to execute DLLs and/or executables when a user logs in."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-t1547-004-winlogon-helper-dll7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1547.00410 attack_stix_id: attack-pattern--6836813e-8ec8-4375-b459-abb388cb1a3511 attack_version: "1.3"12 attack_modified: "2025-10-24T17:48:53.539Z"13---1415# MITRE ATT&CK T1547.004: Winlogon Helper DLL1617## When to use this skill1819Use this skill when the task involves T1547.004, Winlogon Helper DLL, 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: T1547.00425- Technique name: Winlogon Helper DLL26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1547/00428- Tactics: persistence, privilege-escalation29- Platforms: Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may abuse features of Winlogon to execute DLLs and/or executables when a user logs in. Winlogon.exe is a Windows component responsible for actions at logon/logoff as well as the secure attention sequence (SAS) triggered by Ctrl-Alt-Delete. Registry entries in <code>HKLM\Software[\\Wow6432Node\\]\Microsoft\Windows NT\CurrentVersion\Winlogon\</code> and <code>HKCU\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\</code> are used to manage additional helper programs and functionalities that support Winlogon.(Citation: Cylance Reg Persistence Sept 2013) 3738Malicious modifications to these Registry keys may cause Winlogon to load and execute malicious DLLs and/or executables. Specifically, the following subkeys have been known to be possibly vulnerable to abuse: (Citation: Cylance Reg Persistence Sept 2013)3940* Winlogon\Notify - points to notification package DLLs that handle Winlogon events41* Winlogon\Userinit - points to userinit.exe, the user initialization program executed when a user logs on42* Winlogon\Shell - points to explorer.exe, the system shell executed when a user logs on4344Adversaries may take advantage of these features to repeatedly execute malicious code and establish persistence.4546## Agent workflow47481. 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.492. 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.503. 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.514. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.525. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.536. 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.5455## Bundled resources5657- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.58- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.59- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.60- `templates/detection-brief.md`: detection engineering brief template.61- `templates/hunt-plan.md`: threat hunt plan template.62- `templates/incident-response-note.md`: incident response note template.63- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.64- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.65- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6667To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6869## Detection guidance7071No ATT&CK detection guidance was present in the source STIX object.7273## Useful telemetry and data sources7475- Not specified in the STIX object.7677## Mitigations to consider7879- Execution Prevention80- User Account Management8182## Known threat context8384Use these examples only as contextual leads, not as proof that an observed event is this technique:8586- Bazar (malware)87- Cannon (malware)88- DarkTortilla (malware)89- Dipsind (malware)90- Gazer (malware)91- KeyBoy (malware)92- LockBit 3.0 (malware)93- Qilin (malware)94- Remexi (malware)95- Revenge RAT (malware)96- Tropic Trooper (intrusion-set)97- Turla (intrusion-set)98- Wizard Spider (intrusion-set)99100## Recommended output pattern101102When responding with this skill, structure the answer as:103104- Assessment: whether the evidence supports this ATT&CK mapping and why.105- Evidence: specific indicators, logs, behaviors, and assumptions.106- Detection: telemetry sources, analytic logic, and tuning considerations.107- Response: containment, eradication, recovery, and validation actions.108- Coverage gaps: missing logs, sensors, controls, or environmental details.109- References: include the ATT&CK URL and any user-provided evidence references.110111## ATT&CK contributors112113- Praetorian