Helper prerequisites
This bundled skill supplies methodology text; it does not install the local helper files invoked below. Before running a command using agent.py or a scripts/ path, create that file from a complete implementation when one is supplied, or obtain and review the matching upstream helper. Check its --help and dependencies against the shown arguments. If no implementation is available, the invocation is a workflow illustration rather than a runnable command; use the documented underlying tools instead.
Analyzing PowerShell Script Block Logging
When to Use
- When investigating security incidents that require analyzing powershell script block logging
- 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
Detection Gaps & Validation
- If 4104 is disabled, you have nothing: Script Block Logging must be enabled via GPO (
Administrative Templates > Windows PowerShell > Turn on PowerShell Script Block Logging) or registry HKLM\...\PowerShell\ScriptBlockLogging\EnableScriptBlockLogging=1. Attackers running powershell -version 2 downgrade to an engine with no 4104/AMSI at all. Hunt for 400/600 engine-start events showing v2 and for the absence of expected 4104 volume on a host.
- AMSI bypass precedes the malicious block:
amsiInitFailed, [Ref].Assembly.GetType('...AmsiUtils'), and reflection/obfuscated variants neutralize scanning. Detect the bypass string itself in 4104, since the subsequent payload may log as benign or not at all.
- Obfuscation defeats naive regex: tick marks (
I+EX), string -join/-f format ops, [char] arrays, gzip+base64, and SecureString hide IEX/DownloadString. Score on Shannon entropy and decoded content, not literal keywords. Reconstruct multi-part scripts by ScriptBlockId ordered by MessageNumber before scoring — a split payload evades per-event matching.
- Watch 4103 too: Module/pipeline logging (EID 4103) captures invocation detail 4104 misses; correlate both.
- Validate the rule fires: in a lab, run an
-EncodedCommand download cradle and an AMSI bypass, then confirm your parser flags both EID 4104 entries and that base64 decodes as UTF-16LE. FP tuning: legitimate admin tooling, Chocolatey, SCCM, and installers emit large/encoded blocks — baseline by signing cert and parent process before alerting.
Prerequisites
- Familiarity with security operations concepts and tools
- Access to a test or lab environment for safe execution
- Python 3.8+ with required dependencies installed
- Appropriate authorization for any testing activities
Instructions
- Install dependencies:
pip install python-evtx lxml
- Collect PowerShell Operational logs:
Microsoft-Windows-PowerShell%4Operational.evtx
- Parse Event ID 4104 entries using python-evtx to extract ScriptBlockText, ScriptBlockId, and MessageNumber/MessageTotal for multi-part script reconstruction.
- Apply detection heuristics:
- Base64-encoded commands (
-EncodedCommand, FromBase64String)
- Download cradles (
DownloadString, DownloadFile, Invoke-WebRequest, Net.WebClient)
- AMSI bypass patterns (
AmsiUtils, amsiInitFailed)
- Obfuscation indicators (high entropy, tick-mark insertion, string concatenation)
- Generate a report with reconstructed scripts, risk scores, and MITRE ATT&CK mappings.
python scripts/agent.py --evtx-file /path/to/PowerShell-Operational.evtx --output ps_analysis.json
Examples
Detect Encoded Command Execution
import base64
if "-encodedcommand" in script_text.lower():
encoded = script_text.split()[-1]
decoded = base64.b64decode(encoded).decode("utf-16-le")
Reconstruct Multi-Block Script
Scripts split across multiple 4104 events share a ScriptBlockId. Concatenate blocks ordered by MessageNumber to recover the full script.
1---2name: analyzing-powershell-script-block-logging3description: Parse Windows PowerShell Script Block Logs (Event ID 4104) from EVTX files to detect obfuscated commands, encoded4 payloads, and living-off-the-land techniques. Uses python-evtx to extract and reconstruct multi-block scripts, applies entropy5 analysis and pattern matching for Base64-encoded commands, Invoke-Expression abuse, download cradles, and AMSI bypass attempts.6domain: cybersecurity7subdomain: security-operations8tags:9- powershell10- script-block-logging11- event-id-410412- obfuscation-detection13- windows-forensics14- endpoint-security15version: '1.0'16author: Krishna Kumar (xalgord)17license: Apache-2.018nist_csf:19- DE.CM-0120- RS.MA-0121- GV.OV-0122- DE.AE-0223metadata:24 source: https://skillmd.com/skills/xalgord/analyzing-powershell-script-block-logging25---2627## Helper prerequisites2829This bundled skill supplies methodology text; it does not install the local helper files invoked below. Before running a command using `agent.py` or a `scripts/` path, create that file from a complete implementation when one is supplied, or obtain and review the matching upstream helper. Check its `--help` and dependencies against the shown arguments. If no implementation is available, the invocation is a workflow illustration rather than a runnable command; use the documented underlying tools instead.30313233# Analyzing PowerShell Script Block Logging343536## When to Use3738- When investigating security incidents that require analyzing powershell script block logging39- When building detection rules or threat hunting queries for this domain40- When SOC analysts need structured procedures for this analysis type41- When validating security monitoring coverage for related attack techniques4243## Detection Gaps & Validation4445- **If 4104 is disabled, you have nothing:** Script Block Logging must be enabled via GPO (`Administrative Templates > Windows PowerShell > Turn on PowerShell Script Block Logging`) or registry `HKLM\...\PowerShell\ScriptBlockLogging\EnableScriptBlockLogging=1`. Attackers running `powershell -version 2` downgrade to an engine with no 4104/AMSI at all. Hunt for 400/600 engine-start events showing v2 and for the absence of expected 4104 volume on a host.46- **AMSI bypass precedes the malicious block:** `amsiInitFailed`, `[Ref].Assembly.GetType('...AmsiUtils')`, and reflection/obfuscated variants neutralize scanning. Detect the *bypass string itself* in 4104, since the subsequent payload may log as benign or not at all.47- **Obfuscation defeats naive regex:** tick marks (`I`+`EX`), string `-join`/`-f` format ops, `[char]` arrays, gzip+base64, and `SecureString` hide `IEX`/`DownloadString`. Score on Shannon entropy and decoded content, not literal keywords. Reconstruct multi-part scripts by `ScriptBlockId` ordered by `MessageNumber` before scoring — a split payload evades per-event matching.48- **Watch 4103 too:** Module/pipeline logging (EID 4103) captures invocation detail 4104 misses; correlate both.49- **Validate the rule fires:** in a lab, run an `-EncodedCommand` download cradle and an AMSI bypass, then confirm your parser flags both EID 4104 entries and that base64 decodes as UTF-16LE. **FP tuning:** legitimate admin tooling, Chocolatey, SCCM, and installers emit large/encoded blocks — baseline by signing cert and parent process before alerting.5051## Prerequisites5253- Familiarity with security operations concepts and tools54- Access to a test or lab environment for safe execution55- Python 3.8+ with required dependencies installed56- Appropriate authorization for any testing activities5758## Instructions59601. Install dependencies: `pip install python-evtx lxml`612. Collect PowerShell Operational logs: `Microsoft-Windows-PowerShell%4Operational.evtx`623. Parse Event ID 4104 entries using python-evtx to extract ScriptBlockText, ScriptBlockId, and MessageNumber/MessageTotal for multi-part script reconstruction.634. Apply detection heuristics:64 - Base64-encoded commands (`-EncodedCommand`, `FromBase64String`)65 - Download cradles (`DownloadString`, `DownloadFile`, `Invoke-WebRequest`, `Net.WebClient`)66 - AMSI bypass patterns (`AmsiUtils`, `amsiInitFailed`)67 - Obfuscation indicators (high entropy, tick-mark insertion, string concatenation)685. Generate a report with reconstructed scripts, risk scores, and MITRE ATT&CK mappings.6970```bash71python scripts/agent.py --evtx-file /path/to/PowerShell-Operational.evtx --output ps_analysis.json72```7374## Examples7576### Detect Encoded Command Execution77```python78import base6479if "-encodedcommand" in script_text.lower():80 encoded = script_text.split()[-1]81 decoded = base64.b64decode(encoded).decode("utf-16-le")82```8384### Reconstruct Multi-Block Script85Scripts split across multiple 4104 events share a `ScriptBlockId`. Concatenate blocks ordered by `MessageNumber` to recover the full script.