Windows PowerShell Script Block Logging: Nishang Commandlet Names and Arguments

High-severity alert on PowerShell script blocks that reference known Nishang commandlets and exfil/execution helper names.

FreeReviewedSigma · High · v2
Product
windows
Category
ps_script
Author
Alec Costello (SigmaHQ), DRL 1.1
Published
2019-05-16
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule matches PowerShell script block content for known Nishang framework commandlet/function names. These artifacts can indicate attacker tradecraft for credential access, persistence, data collection, and execution workflows delivered via PowerShell. It relies on Script Block Logging telemetry to observe the exact text of commands and parameters within executed PowerShell script blocks.

Related detections9 linkedT1059.001 — drag to rearrange
Malicious Metasploit Stager Delivery via mshta Remote HTA (via process_creation)
Suspicious PowerShell Download of Disguised Payload to ProgramData
Suspicious PowerShell WebClient Download of Executable Payload
Malicious Script Host Spawning PowerShell in Gootloader Chain
Suspicious PsExec Service Launching Encoded PowerShell Payload
Suspicious PowerShell Remote Script Execution via IEX DownloadString
Malicious SharePoint ToolShell Post-Exploitation via Encoded PowerShell (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Malicious Qilin Chrome Credential Harvesting Script Execution via IPScanner (via process_creation)
Windows PowerShell Script Block Logging: Nishang Commandlet Names and Arguments
Pivot detection · T1059.001 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.