Skip to content

SSZcreate/Pentab_server / .agents/skills/cybersecurity/skills/hunting-for-startup-folder-persistence

hunting-for-startup-folder-persistence

Unverified

Detects T1547.001 startup folder persistence by monitoring Windows startup directories for suspicious file creation, cross-referencing Autoruns entries, and running a Python watchdog script for real-time filesystem monitoring. Use when hunting for malware or implants that survive reboot via startup-folder placement, or when validating autoruns/EDR findings against known-good startup baselines.

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
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall