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-lateral-movement-over-smb-and-wmiActive Directory and Windows

hunting-lateral-movement-over-smb-and-wmi

⁨Hunts for lateral movement via remote service creation, admin share writes, and⁩

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-lateral-movement-over-smb-and-wmi

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

SignatureSigned, ed25519
3OdQ7ub+qE…Iiuv9lAg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagea773ec93…067c3d2e
a773ec930885…dcdf067c3d2e4 files · ⁦3.2 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-lateral-movement-over-smb-and-wmi@da7600a

When to Use

  • You have Windows logon (4624), service install (7045/4697), and process-creation telemetry and want to detect remote execution tools (PsExec, WMIexec, SMBexec) moving between hosts.
  • You are reconstructing an attacker's east-west movement.

Do not use this to alert on all Type 3 logons — network logons are normal. Hunt the service-creation, admin-share, and remote-WMI patterns that accompany them.

Prerequisites

  • Logon (4624 Type 3), service install (7045/4697), and process-creation events.

Workflow

Step 1: Correlate remote-execution indicators

bash
python scripts/analyst.py hunt events.csv

Flags PsExec-style service installs (PSEXESVC, randomly named services running from ADMIN$), remote WMI parents (wmiprvse.exe spawning cmd/powershell), and named-pipe service binaries.

Step 2: Build a movement graph

Group by source account and target host to see fan-out across systems.

Step 3: Confirm

Distinguish admin tooling from intrusion by account, timing, and target breadth.

Step 4: Operationalize

Write Sigma rules for PsExec service creation and wmiprvse.exe child shells.

Validation

  • Remote service installs are flagged by image path/name patterns, not service installs broadly.
  • wmiprvse.exe-parented shells are correlated with the originating account where possible.
  • Findings map to ATT&CK T1021.002/.003.

Pitfalls

  • Legitimate admin/management software using PsExec or remote WMI.
  • Renamed PsExec service binaries evading name checks.
  • Missing the logon-to-execution correlation across separate event sources.

References

  • See references/api-reference.md for the hunter.
  • ATT&CK T1021.002 and Event 4624/4697 docs (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, 2026da7600aa773ec93Signed–

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