hunting-for-registry-run-key-persistence

hunting-for-registry-run-key-persistence is a skill for Claude Code from oyi77/1ai-skills. It costs 66 tokens per session (1,253 once invoked), scanned A, original, MIT.

A cybersecurity guide for finding Windows Registry Run keys, settings that start programs automatically when a user logs in, being used to keep malware running.

In plain words
What is it for?
It is for investigating Windows persistence, reviewing Sysmon logs, and detecting suspicious startup entries such as temporary executables or encoded PowerShell commands.
Why use it?
Attackers can use these startup settings to survive a reboot while appearing like normal system configuration. The guide connects registry changes with file creation and process activity.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the 1ai-skills plugin — 209 skills, 4 commands shipped together

Good fit It is for investigating Windows persistence, reviewing Sysmon logs, and detecting suspicious startup entries such as temporary executables or encoded PowerShell commands.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oyi77/1ai-skills/hunting-for-registry-run-key-persistence
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add oyi77/1ai-skills --skill hunting-for-registry-run-key-persistence
Clone the repo
git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 209 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for hunting-for-registry-run-key-persistence

README.md
[![agentmods](https://agentmods.dev/badge/skills/oyi77/1ai-skills/hunting-for-registry-run-key-persistence/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/hunting-for-registry-run-key-persistence)
Your own site
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/hunting-for-registry-run-key-persistence"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/hunting-for-registry-run-key-persistence/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hunting-for-registry-run-key-persistence

Your own site · 80×15
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/hunting-for-registry-run-key-persistence"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/hunting-for-registry-run-key-persistence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,253 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.01253
Opus 5 $0.00033 $0.00626
Sonnet 5 $0.00013 $0.00251
Haiku 4.5 $0.00007 $0.00125

Measured 8d ago against content hash 184dd8e6152a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

hunting-for-registry-run-key-persistence scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cybersecurity/_deprecated/hunting-for-registry-run-key-persistence/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Hunting for Registry Run Key Persistence

Overview

Registry Run keys (T1547.001) are one of the most commonly used persistence mechanisms by adversaries. When a program is added to a Run key in the Windows registry, it executes automatically when a user logs in. Attackers abuse keys under HKLM\Software\Microsoft\Windows\CurrentVersion\Run, HKCU\Software\Microsoft\Windows\CurrentVersion\Run, and their RunOnce counterparts to maintain persistence. Sysmon Event ID 13 (RegistryEvent - Value Set) captures registry value modifications including the target object path, the process that made the change, and the new value. Detection involves monitoring these events for suspicious executables in temp directories, encoded PowerShell commands, LOLBin paths, and processes that do not normally create Run key entries. Chaining Event 13 with Event 1 (Process Creation) and Event 11 (FileCreate) strengthens detection by confirming payload creation and execution.

When to Use

Trigger phrases:

  • "hunting for registry run key persistence"

  • "Detect MITRE ATT&CK T1547"

  • When investigating security incidents that require hunting for registry run key persistence

  • When building detection rules or threat hunting queries for this domain

  • When SOC analysts need structured procedures for this analysis type

  • When validating security monitoring coverage for related attack techniques

When NOT to Use

  • When you lack proper authorization for testing
  • For production systems without change management
  • When the task requires legal or compliance expertise beyond technical scope

Prerequisites

  • Windows systems with Sysmon installed and configured to log Event ID 13
  • Sysmon config with RegistryEvent rules for Run/RunOnce keys
  • Python 3.9+ with json, xml.etree.ElementTree, re modules
  • SIEM or log aggregator collecting Sysmon logs (Splunk, Elastic, Sentinel)
  • Knowledge of legitimate auto-start programs for baseline comparison

Steps

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}

Read the full file on GitHub · 126 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 126 lines · 66 tokens per session scan A 184dd8e6152a

Subscribe to this mod's changes

hunting-for-registry-run-key-persistence is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,253 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

hunting-wmi-event-subscription-persistence

Hunts for malicious WMI permanent event subscription persistence by correlating EventFilter, CommandLineEventConsumer/ActiveScriptEventConsumer, and FilterToConsumerBinding records from Sysmon Event IDs 19/20/21 or WMI repository exports. Activates for requests to hunt WMI persistence, detect event consumer backdoors…

meltedinhex/analyst-ai-pack · 83 tokens

hunting-scheduled-task-abuse

Hunts for malicious scheduled task persistence by analyzing task registration events (4698) and schtasks process creation for suspicious actions, triggers, and hidden tasks. Activates for requests to hunt scheduled task abuse, detect malicious schtasks usage, or find persistence via the Task Scheduler.

meltedinhex/analyst-ai-pack · 63 tokens

analyzing-cobalt-strike-beacon-configuration

Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.

mukul975/Anthropic-Cybersecurity-Skills · 42 tokens

analyzing-malware-persistence-with-autoruns

Use Sysinternals Autoruns to systematically enumerate and analyze malware persistence mechanisms across Windows registry run keys, scheduled tasks, services, drivers, and startup locations. Use when hunting for persistence during Windows incident response, triaging a compromised endpoint, or validating that malware…

mukul975/Anthropic-Cybersecurity-Skills · 74 tokens

analyzing-azure-activity-logs-for-threats

Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in Azure environments. Use when investigating suspicious Azure tenant activity or…

mukul975/Anthropic-Cybersecurity-Skills · 68 tokens

analyzing-powershell-script-block-logging

Parse Windows PowerShell Script Block Logs (Event ID 4104) from EVTX files to detect obfuscated commands, encoded payloads, and living-off-the-land techniques. Uses python-evtx to extract and reconstruct multi-block scripts, applies entropy analysis and pattern matching for Base64-encoded commands, Invoke-Expression…

mukul975/Anthropic-Cybersecurity-Skills · 88 tokens