Individual skill
detecting-suspicious-powershell-execution
Detect suspicious PowerShell execution patterns including encoded commands, download cradles, AMSI bypass attempts, and constrained language mode evasion.
internal/tools/skills/data/threat-hunting/detecting-suspicious-powershell-execution/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,320
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- threat-hunting Declared skill tag
- mitre-attack Declared skill tag
- powershell Declared skill tag
- execution Declared skill tag
- t1059 Declared skill tag
- amsi Declared skill tag
- proactive-detection Declared skill tag
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Detecting Suspicious Powershell Execution
## When to Use
- When proactively hunting for indicators of detecting suspicious powershell execution in the environment
- After threat intelligence indicates active campaigns using these techniques
- During incident response to scope compromise related to these techniques
- When EDR or SIEM alerts trigger on related indicators
- During periodic security assessments and purple team exercises
## Detection Gaps & Validation
- **Script Block Logging (4104) is the ground truth:** EID 4104 captures the deobfuscated script. With the GPO off you only have 4688/Sysmon EID 1 command lines, which obfuscation defeats — confirm 4104 and 4103 (Module Logging) are enabled and forwarded.
- **`-EncodedCommand` and aliases:** rules keyed on the literal `powershell.exe -enc` miss `-e`, `-ec`, `pwsh`, and renamed/copied binaries — match on EID 1 `OriginalFileName = PowerShell.EXE` plus base64 entropy, not the image name.