hunting-for-startup-folder-persistence

mukul975/Anthropic-Cybersecurity-Skills · updated May 25, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/hunting-for-startup-folder-persistence
0 commentsdiscussion
summary

Detect T1547.001 startup folder persistence by monitoring Windows startup directories for suspicious file creation, analyzing autoruns entries, and using Python watchdog for real-time filesystem monitoring.

skill.md
name
hunting-for-startup-folder-persistence
description
Detect T1547.001 startup folder persistence by monitoring Windows startup directories for suspicious file creation, analyzing autoruns entries, and using Python watchdog for real-time filesystem monitoring.
domain
cybersecurity
subdomain
threat-hunting
tags
- threat-hunting - T1547.001 - startup-folder - persistence - autoruns - watchdog - filesystem-monitoring
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

Hunting for Startup Folder Persistence

Overview

Attackers use Windows startup folders for persistence (MITRE ATT&CK T1547.001 — Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder). Files placed in %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup or C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup execute automatically at user logon. This skill scans startup directories for suspicious files, monitors for real-time changes using Python watchdog, and analyzes file metadata to detect persistence implants.

When to Use

  • When investigating security incidents that require hunting for startup folder 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

Prerequisites

  • Python 3.9+ with watchdog, pefile (optional for PE analysis)
  • Access to Windows startup folders (user and all-users)
  • Windows Event Logs for Event ID 4663 correlation (optional)

Steps

  1. Enumerate all files in user and system startup directories
  2. Analyze file types, creation timestamps, and digital signatures
  3. Flag suspicious file extensions (.bat, .vbs, .ps1, .lnk, .exe)
  4. Check for recently created files (< 7 days) as potential implants
  5. Monitor startup folders in real-time using watchdog FileSystemEventHandler
  6. Correlate with known legitimate startup entries
  7. Generate threat hunting report with T1547.001 MITRE mapping

Expected Output

  • JSON report listing all startup folder contents with risk scores, file metadata, and suspicious indicators
  • Real-time monitoring alerts for new file creation in startup directories
how to use hunting-for-startup-folder-persistence

How to use hunting-for-startup-folder-persistence on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add hunting-for-startup-folder-persistence
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/hunting-for-startup-folder-persistence

The skills CLI fetches hunting-for-startup-folder-persistence from GitHub repository mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/hunting-for-startup-folder-persistence

Reload or restart Cursor to activate hunting-for-startup-folder-persistence. Access the skill through slash commands (e.g., /hunting-for-startup-folder-persistence) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ 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.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.648 reviews
  • Henry Ramirez· Dec 28, 2024

    We added hunting-for-startup-folder-persistence from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kabir Sanchez· Dec 24, 2024

    I recommend hunting-for-startup-folder-persistence for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Hassan Thompson· Dec 20, 2024

    Keeps context tight: hunting-for-startup-folder-persistence is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Charlotte Martin· Nov 19, 2024

    Solid pick for teams standardizing on skills: hunting-for-startup-folder-persistence is focused, and the summary matches what you get after install.

  • Liam White· Nov 11, 2024

    Registry listing for hunting-for-startup-folder-persistence matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kabir Ramirez· Nov 3, 2024

    Useful defaults in hunting-for-startup-folder-persistence — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kabir Perez· Oct 22, 2024

    I recommend hunting-for-startup-folder-persistence for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sofia Robinson· Oct 10, 2024

    hunting-for-startup-folder-persistence has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Chen Khanna· Oct 2, 2024

    hunting-for-startup-folder-persistence reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Isabella Li· Sep 21, 2024

    hunting-for-startup-folder-persistence has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 48

1 / 5