Hunt for registry-based persistence mechanisms including Run keys, Winlogon modifications, IFEO injection, and COM hijacking in Windows environments.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhunting-for-registry-persistence-mechanismsExecute the skills CLI command in your project's root directory to begin installation:
Fetches hunting-for-registry-persistence-mechanisms from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate hunting-for-registry-persistence-mechanisms. Access via /hunting-for-registry-persistence-mechanisms in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
8.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
8.6K
stars
| name | hunting-for-registry-persistence-mechanisms |
| description | Hunt for registry-based persistence mechanisms including Run keys, Winlogon modifications, IFEO injection, and COM hijacking in Windows environments. |
| domain | cybersecurity |
| subdomain | threat-hunting |
| tags | - threat-hunting - mitre-attack - registry - persistence - windows - t1547 - proactive-detection |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| d3fend_techniques | - Executable Denylisting - Execution Isolation - File Metadata Consistency Validation - Content Format Conversion - File Content Analysis |
| nist_csf | - DE.CM-01 - DE.AE-02 - DE.AE-07 - ID.RA-05 |
| Concept | Description |
|---|---|
| T1547.001 | Registry Run Keys |
| T1547.004 | Winlogon Helper DLL |
| T1546.012 | IFEO Injection |
| T1546.015 | COM Hijacking |
| 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 |
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]
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
hunting-for-registry-persistence-mechanisms reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added hunting-for-registry-persistence-mechanisms from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: hunting-for-registry-persistence-mechanisms is the kind of skill you can hand to a new teammate without a long onboarding doc.
hunting-for-registry-persistence-mechanisms is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend hunting-for-registry-persistence-mechanisms for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
hunting-for-registry-persistence-mechanisms reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend hunting-for-registry-persistence-mechanisms for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for hunting-for-registry-persistence-mechanisms matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in hunting-for-registry-persistence-mechanisms — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in hunting-for-registry-persistence-mechanisms — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 30