Hunts for registry-based persistence mechanisms (MITRE T1547) in Windows environments, including Run/RunOnce keys, Winlogon Shell/Userinit modifications, Image File Execution Options (IFEO) debugger injection, and COM hijacking via CLSID overrides. Use when auditing the registry for persistence artifacts or building detections for registry-based malware autostart techniques.
Start a fresh conversation. Replace the highlighted placeholders.
Use hunting-for-registry-persistence-mechanisms to hunt the authorized Windows scope [hosts, time range, and available telemetry] for registry persistence artifacts, validate and correlate findings, and produce a prioritized report with evidence, confidence, risk, and recommended response actions.
Required inputs
[hosts, time range, and available telemetry]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: hunting-for-registry-persistence-mechanismsdescription: Hunts for registry-based persistence mechanisms (MITRE T1547) in Windows environments, including Run/RunOnce keys, Winlogon Shell/Userinit modifications, Image File Execution Options (IFEO) debugger injection, and COM hijacking via CLSID overrides. Use when auditing the registry for persistence artifacts or building detections for registry-based malware autostart techniques.domain: cybersecuritysubdomain: threat-huntingtags: - threat-hunting- mitre-attack- registry- persistence- windows- t1547- proactive-detectionversion: '1.0'author: mahipallicense: Apache-2.0d3fend_techniques: - Executable Denylisting- Execution Isolation- File Metadata Consistency Validation- Content Format Conversion- File Content Analysisnist_csf: - DE.CM-01- DE.AE-02- DE.AE-07- ID.RA-05mitre_attack: - T1046- T1057- T1082- T1083- T1547
Hunting For Registry Persistence Mechanisms
When to Use
When proactively hunting for indicators of hunting for registry persistence mechanisms in the environment
After threat intelligence indicates active campaigns using these techniques
During incident response to scope compromise related to these techniques
When EDR or SIEM alerts trigger on related indicators
During periodic security assessments and purple team exercises
Prerequisites
EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)
SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)
Sysmon deployed with comprehensive configuration
Windows Security Event Log forwarding enabled
Threat intelligence feeds for IOC correlation
Workflow
Formulate Hypothesis: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.
Identify Data Sources: Determine which logs and telemetry are needed to validate or refute the hypothesis.
Execute Queries: Run detection queries against SIEM and EDR platforms to collect relevant events.
Analyze Results: Examine query results for anomalies, correlating across multiple data sources.
Validate Findings: Distinguish true positives from false positives through contextual analysis.
Correlate Activity: Link findings to broader attack chains and threat actor TTPs.
Document and Report: Record findings, update detection rules, and recommend response actions.
Key Concepts
Concept
Description
T1547.001
Registry Run Keys
T1547.004
Winlogon Helper DLL
T1546.012
IFEO Injection
T1546.015
COM Hijacking
Tools & Systems
Tool
Purpose
CrowdStrike Falcon
EDR telemetry and threat detection
Microsoft Defender for Endpoint
Advanced hunting with KQL
Splunk Enterprise
SIEM log analysis with SPL queries
Elastic Security
Detection rules and investigation timeline
Sysmon
Detailed Windows event monitoring
Velociraptor
Endpoint artifact collection and hunting
Sigma Rules
Cross-platform detection rule format
Common Scenarios
Scenario 1: Malware adding HKCU Run key for user-level persistence
Scenario 2: Adversary modifying Winlogon Shell for system-level persistence
Scenario 3: IFEO debugger injection for accessibility feature backdoor
Scenario 4: COM object InprocServer32 hijack for DLL loading