New to Claude Skills? Learn how to install them →

mukul975 on GitHub

Hunting For Registry Persistence

Free

Proactively detect Windows registry persistence mechanisms.

Get this skill

Free · Opens the source repo

What Hunting For Registry Persistence does

Hunting For Registry Persistence is a specialized skill designed for cybersecurity professionals focused on identifying registry-based persistence mechanisms in Windows environments. This skill leverages the MITRE ATT&CK framework, specifically technique T1547, to aid in the detection of various methods adversaries use to maintain persistence on compromised systems. By examining registry entries such as Run/RunOnce keys, Winlogon modifications, and COM hijacking, users can uncover potential indicators of compromise (IoCs) associated with malicious activities.

The skill is particularly useful during proactive threat hunting, incident response, and security assessments. It guides users through a structured workflow, starting from formulating a hypothesis based on threat intelligence to documenting findings and updating detection rules. This systematic approach ensures that security teams can effectively correlate activity across different data sources, enhancing their ability to identify and respond to threats in real-time.

To utilize this skill, users should have a robust security infrastructure in place, including an EDR platform with telemetry capabilities and a SIEM for log analysis. The skill also emphasizes the importance of threat intelligence feeds for correlating indicators and validating findings. By integrating these components, security teams can improve their detection capabilities and respond swiftly to potential threats.

Overall, Hunting For Registry Persistence is an essential tool for security analysts and incident responders who need to stay ahead of sophisticated threat actors leveraging registry-based techniques to maintain footholds within Windows environments.

When to use it

Use this skill when proactively hunting for registry persistence indicators or during incident response to scope compromises related to these techniques.

When not to use it

This skill may not be suitable for environments lacking the necessary telemetry or security infrastructure, such as EDR or SIEM systems.

What you can build with it

Malware Persistence Detection

Identify when malware adds a Run key in HKCU to maintain user-level persistence.

Winlogon Modification

Detect adversaries modifying Winlogon Shell for system-level persistence.

Debugger Injection Analysis

Investigate IFEO debugger injection techniques used for backdoor access.

How to install Hunting For Registry Persistence

View source

1. Install with the skills CLI

npx skills add mukul975/anthropic-cybersecurity-skills/hunting-for-registry-persistence-mechanisms --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by mukul975

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

  1. Formulate Hypothesis: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.
  2. Identify Data Sources: Determine which logs and telemetry are needed to validate or refute the hypothesis.
  3. Execute Queries: Run detection queries against SIEM and EDR platforms to collect relevant events.
  4. Analyze Results: Examine query results for anomalies, correlating across multiple data sources.
  5. Validate Findings: Distinguish true positives from false positives through contextual analysis.
  6. Correlate Activity: Link findings to broader attack chains and threat actor TTPs.
  7. Document and Report: Record findings, update detection rules, and recommend response actions.

Key Concepts

ConceptDescription
T1547.001Registry Run Keys
T1547.004Winlogon Helper DLL
T1546.012IFEO Injection
T1546.015COM Hijacking

Tools & Systems

ToolPurpose
CrowdStrike FalconEDR telemetry and threat detection
Microsoft Defender for EndpointAdvanced hunting with KQL
Splunk EnterpriseSIEM log analysis with SPL queries
Elastic SecurityDetection rules and investigation timeline
SysmonDetailed Windows event monitoring
VelociraptorEndpoint artifact collection and hunting
Sigma RulesCross-platform detection rule format

Common Scenarios

  1. Scenario 1: Malware adding HKCU Run key for user-level persistence
  2. Scenario 2: Adversary modifying Winlogon Shell for system-level persistence
  3. Scenario 3: IFEO debugger injection for accessibility feature backdoor
  4. Scenario 4: COM object InprocServer32 hijack for DLL loading

Output Format

Hunt ID: TH-HUNTIN-[DATE]-[SEQ]
Technique: T1547.001
Host: [Hostname]
User: [Account context]
Evidence: [Log entries, process trees, network data]
Risk Level: [Critical/High/Medium/Low]
Confidence: [High/Medium/Low]
Recommended Action: [Containment, investigation, monitoring]

Frequently asked questions about Hunting For Registry Persistence

Similar skills