Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/hunting-persistence-mechanisms-on-windowsActive Directory and Windows

hunting-persistence-mechanisms-on-windows

⁨Hunts for Windows persistence across autostart locations: Run keys, services,⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/hunting-persistence-mechanisms-on-windows

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
BMdxIMHW9M…4rRb4qDw==The CLI checks the SHA-256 and the signature before it writes a file.
Package1df430d0…3042aa78
1df430d0a51d…0fed3042aa784 files · ⁦3.3 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-persistence-mechanisms-on-windows@da7600a

When to Use

  • You are hunting for how an adversary maintains a foothold across reboots.
  • You have autostart inventories (Autoruns exports, registry/scheduled-task/WMI dumps) from one or many hosts and want to surface anomalies.
  • You want to baseline a fleet and flag entries that deviate or were recently added.

Do not use a single host's autoruns list as ground truth — many legitimate entries look unusual; comparison against a fleet baseline is what makes anomalies meaningful.

Prerequisites

  • Autostart data per host: Run/RunOnce keys, services, scheduled tasks, WMI event subscriptions, startup folders, and (ideally) signing status.
  • A baseline (golden image or fleet majority) to diff against.

Workflow

Step 1: Inventory the ASEPs

Collect the common Autostart Extensibility Points across hosts: Run keys (T1547.001), services (T1543.003), scheduled tasks (T1053.005), and WMI subscriptions (T1546.003).

Step 2: Baseline and diff

Compare each host's entries to the fleet baseline; entries appearing on few hosts, unsigned, or pointing to user-writable/temp paths bubble up.

bash
python scripts/analyst.py hunt autostart.json --baseline baseline.json

Step 3: Score anomalies

Raise priority for: unsigned binaries, LOLBins launched with encoded args, paths in %TEMP%/%APPDATA%, recently created tasks, and WMI consumers running scripts.

Step 4: Triage candidates

For each high-score entry, pull the target binary's signing/hash, the creating user/time, and correlate with process and network telemetry.

Step 5: Confirm and respond

Validate suspicious entries (sandbox/RE the binary), escalate confirmed persistence to IR, and turn the pattern into a detection.

Validation

  • Anomalies are ranked against a baseline, not flagged from one host in isolation.
  • High-score entries map to concrete artifacts (path, hash, signer) for triage.
  • Confirmed persistence ties back to a known intrusion timeline.

Pitfalls

  • Treating every unsigned entry as malicious; many legitimate tools are unsigned.
  • Checking only Run keys and missing services/tasks/WMI subscriptions.
  • No timestamps, so you cannot distinguish long-standing from newly planted entries.

References

  • See references/api-reference.md for the autostart hunter.
  • ATT&CK Persistence tactic and Autoruns (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a1df430d0Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login