How do I install the Hunting For Anomalous Powershell Execution skill?

Run npx skillmds add thedixitjain/hunting-for-anomalous-powershell-execution in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hunting For Anomalous Powershell Execution safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hunting For Anomalous Powershell Execution?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hunting For Anomalous Powershell Execution free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hunting For Anomalous Powershell Execution?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hunting For Anomalous Powershell Execution by thedixitjain

Name: Hunting For Anomalous Powershell Execution
Rating: 4.5 (4 reviews)
Author: thedixitjain

Hunting For Anomalous Powershell Execution

'Hunt for malicious PowerShell activity by analyzing Script Block Logging (Event 4104), Module Logging (Event 4103), and process creation events. The analyst parses Windows Event Log EVTX files to detect obfuscated commands, AMSI bypass attempts, encoded payloads, credential dumping keywords, and suspicious download cradles. Activates for requests involving PowerShell threat hunting, script block analysis, encoded command detection, or AMSI bypass identification. '

thedixitjain fba677a 4 files · 26.1 KB Updated Sep 9, 2026 2 repo stars

File contents

Hunting for Anomalous PowerShell Execution

Overview

PowerShell Script Block Logging (Event ID 4104) records the full deobfuscated script text executed on a Windows endpoint, making it the primary data source for hunting malicious PowerShell. Combined with Module Logging (4103) and process creation events, analysts can detect encoded commands, AMSI bypass patterns, download cradles, credential theft tools, and fileless attack techniques even when the attacker uses obfuscation layers.

When to Use

When investigating security incidents that require hunting for anomalous powershell execution
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

Windows Event Log exports (.evtx) from Microsoft-Windows-PowerShell/Operational
Python 3.8+ with python-evtx and lxml libraries
Script Block Logging enabled via Group Policy
Understanding of common PowerShell attack techniques

Steps

Parse EVTX files extracting Event 4104 script block text and metadata
Reassemble multi-part script blocks using ScriptBlock ID correlation
Scan script text for AMSI bypass indicators and obfuscation patterns
Detect encoded command execution and base64 payloads
Identify download cradles, credential dumping, and lateral movement commands
Score and prioritize findings by threat severity

Expected Output

{
  "total_events": 1247,
  "suspicious_events": 23,
  "amsi_bypass_attempts": 2,
  "encoded_commands": 8,
  "download_cradles": 5,
  "credential_access": 3
}

Source: mukul975/Anthropic-Cybersecurity-Skills → skills/hunting-for-anomalous-powershell-execution/SKILL.md

---name: hunting-for-anomalous-powershell-executiondescription: 'Hunt for malicious PowerShell activity by analyzing Script Block Logging (Event 4104), Module Logging (Event 4103), and process creation events. The analyst parses Windows Event Log EVTX files to detect obfuscated commands, AMSI bypass attempts, encoded payloads, credential dumping keywords, and suspicious download cradles. Activates for requests involving PowerShell threat hunting, script block analysis, encoded command detection, or AMSI bypass identification. '--- # Hunting for Anomalous PowerShell Execution ## Overview PowerShell Script Block Logging (Event ID 4104) records the full deobfuscated script text executed on a Windows endpoint, making it the primary data source for hunting malicious PowerShell. Combined with Module Logging (4103) and process creation events, analysts can detect encoded commands, AMSI bypass patterns, download cradles, credential theft tools, and fileless attack techniques even when the attacker uses obfuscation layers. ## When to Use - When investigating security incidents that require hunting for anomalous powershell execution - 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 - Windows Event Log exports (.evtx) from Microsoft-Windows-PowerShell/Operational - Python 3.8+ with python-evtx and lxml libraries - Script Block Logging enabled via Group Policy - Understanding of common PowerShell attack techniques ## Steps 1. Parse EVTX files extracting Event 4104 script block text and metadata 2. Reassemble multi-part script blocks using ScriptBlock ID correlation 3. Scan script text for AMSI bypass indicators and obfuscation patterns 4. Detect encoded command execution and base64 payloads 5. Identify download cradles, credential dumping, and lateral movement commands 6. Score and prioritize findings by threat severity ## Expected Output ```json { "total_events": 1247, "suspicious_events": 23, "amsi_bypass_attempts": 2, "encoded_commands": 8, "download_cradles": 5, "credential_access": 3 } ``` --- **Source:** [`mukul975/Anthropic-Cybersecurity-Skills`](https://github.com/mukul975/Anthropic-Cybersecurity-Skills) → `skills/hunting-for-anomalous-powershell-execution/SKILL.md`

Frequently asked questions