hunting-for-registry-persistence-mechanisms

Detect registry-based persistence mechanisms including Run keys, IFEO injection, and COM hijacking on Windows.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill hunting-for-registry-persistence-mechanisms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunting-for-registry-persistence-mechanisms
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/threat-hunting/hunting-for-registry-persistence-mechanisms
Command: npx skills add https://github.com/xalgord/xalgorix --skill hunting-for-registry-persistence-mechanisms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Windows attackers commonly establish persistence through registry modifications, and default monitoring configurations routinely miss techniques like IFEO debuggers and per-user COM hijacks. This Skill guides analysts through a structured hunt for registry persistence so these footholds are found before they are used.

Core Features & Use Cases

  • Technique Coverage: Hunts MITRE ATT&CK T1547.001 (Run keys), T1547.004 (Winlogon helper DLLs), T1546.012 (IFEO injection), and T1546.015 (COM hijacking).
  • Detection Gap Analysis: Documents blind spots such as unmounted NTUSER.DAT hives, fileless registry values, and Sysmon EID 13 filter gaps, with Atomic test validation steps.
  • Structured Workflow: Provides a seven-step hunt process from hypothesis formulation through documentation, with a standardized finding output format.
  • Use Case: After threat intelligence reports a campaign using IFEO debugger persistence, run this hunt across your fleet using Sysmon and EDR telemetry to scope exposure and tune false positives from legitimate installers.

Quick Start

Hunt my Windows environment for registry persistence mechanisms including Run keys, Winlogon modifications, IFEO injection, and COM hijacking.

Frequently Asked Questions about hunting-for-registry-persistence-mechanisms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hunt for registry persistence mechanisms on Windows?

Formulate a hypothesis based on ATT&CK techniques like T1547.001, then query Sysmon Event ID 13 and EDR telemetry for writes to Run keys, Winlogon, IFEO, and COM CLSID paths. Validate findings by correlating TargetObject, Details, and Image fields across data sources.

What registry keys do attackers use for persistence?

Common targets include HKLM and HKCU Run and RunOnce keys, Winlogon Shell and Userinit values, Image File Execution Options Debugger entries, and COM hijacking via HKCU\Software\Classes\CLSID InprocServer32. Each maps to specific MITRE ATT&CK sub-techniques.

Why does Sysmon miss some registry persistence events?

Sysmon Event ID 13 only fires for paths included in the RegistryEvent filter, and default configurations often exclude IFEO and per-user Classes hives. Fileless values written directly into registry data also produce no file creation events to correlate.

Can I detect persistence in offline user registry hives?

Yes, logged-off users' HKCU data lives in unmounted NTUSER.DAT files, which live reg query commands miss. Hunt these by mounting or parsing offline hives with tools like Velociraptor during endpoint artifact collection.

How do I reduce false positives when hunting Run keys?

Baseline by signer and value path rather than by key alone, since msiexec installers, GPO, and software-update agents legitimately write Run keys. Validate coverage by running Atomic Red Team tests for T1547.001, T1546.012, and T1546.015.