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-suspicious-powershell-executionDFIR and threat hunting

hunting-suspicious-powershell-execution

⁨Hunts malicious PowerShell using script-block (EID 4104) and module logging:⁩

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-suspicious-powershell-execution

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

SignatureSigned, ed25519
XMAerylceS…b+QR4ICQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package5c2a893c…63805edb
5c2a893c02b6…b76563805edb4 files · ⁦3.4 KB⁩
ScanMedium7 findings
  • command.pipe_to_shellSKILL.md:57
  • command.base64_execSKILL.md:58
  • command.pipe_to_shellSKILL.md:87
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-suspicious-powershell-execution@da7600a

When to Use

  • You have PowerShell script-block (Event ID 4104) and/or module logging and want to hunt abuse.
  • You are testing a hypothesis that attackers use encoded commands, download cradles, or AMSI/logging bypasses.
  • You need to score and decode a large volume of PowerShell events into a triage queue.

Do not use simple keyword blocklists as the sole method — admins legitimately use many of the same cmdlets; score combinations and decode before judging.

Prerequisites

  • Script-block logging enabled (Event ID 4104) and exported to a queryable store.
  • A baseline of normal administrative PowerShell for your environment.

Workflow

Step 1: Collect script-block events

Pull EID 4104 script-block text (and EID 4103 module logging) over the hunt window. Reassemble multi-part script blocks before analysis.

Step 2: Score suspicious constructs

Weight combinations rather than single keywords: -EncodedCommand, IEX/Invoke-Expression with Net.WebClient/Invoke-WebRequest, FromBase64String, -w hidden -nop, AMSI strings, and [Ref].Assembly reflection.

bash
python scripts/analyst.py score events.json

Step 3: Decode payloads

Base64-decode -EncodedCommand (UTF-16LE) and recover layered encodings to read the real intent (download URLs, in-memory loaders).

Step 4: Baseline and pivot

Compare against normal admin activity; for survivors, pull the parent process, user, host, and network connections to confirm.

Step 5: Confirm and operationalize

Validate true positives, escalate to IR, and convert the scoring logic into a detection rule.

Validation

  • High-score events decode to coherent malicious intent, not benign admin scripts.
  • Multi-part script blocks are reassembled before scoring (no truncated false negatives).
  • Confirmed cases tie to a parent process and user consistent with intrusion.

Pitfalls

  • Flagging single keywords (IEX alone) and drowning in admin noise.
  • Forgetting -EncodedCommand is UTF-16LE, producing garbled decodes.
  • Ignoring AMSI/logging-bypass attempts that precede the real payload.

References

  • See references/api-reference.md for the scorer/decoder.
  • Script-block logging docs and ATT&CK T1059.001 (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. MediumCommand · command.pipe_to_shellSKILL.md:57
  2. MediumCommand · command.base64_execSKILL.md:58
  3. MediumCommand · command.pipe_to_shellSKILL.md:87
  4. MediumFile · Executable script shipped with the skillscripts/analyst.py
  5. MediumCommand · command.base64_execscripts/analyst.py:20
  6. MediumCommand · command.pipe_to_shellscripts/analyst.py:21
  7. 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, 2026da7600a5c2a893cSigned–

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