analyzing-powershell-empire-artifacts — Claude Code skill
The analyzing-powershell-empire-artifacts skill hunts for PowerShell Empire traces in Windows event logs and builds a report with IOCs, decoded payloads, and MITRE ATT&CK mappings.
Apache-2.0 303 installs ★ 36,511 updated 2026-08-31
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a claude-codeWhat analyzing-powershell-empire-artifacts does
The skill examines Windows Event Log data or exported EVTX files for PowerShell Empire traces. It checks Script Block Logging event 4104 and Module Logging event 4103, the powershell -noP -sta -w 1 -enc launcher, Base64 content using System.Net.WebClient or FromBase64String, known module calls, and staging URL patterns.
Its result is a JSON report containing matched IOCs, decoded Base64 payloads, a timeline of suspicious events, MITRE ATT&CK techniques, and severity scores. Use it for threat hunting, detection-rule work, or monitoring coverage checks. Python 3.9+ is required, along with access to Windows Event Log or EVTX files.
Coverage is incomplete when Event ID 4104 or 4103 logging has not been enabled through Group Policy.
What it helps with
- find PowerShell Empire traces in EVTX files
- inspect events 4104 and 4103
- spot Base64 payloads and staging URLs
- map findings to MITRE ATT&CK
- produce a JSON IOC report
Example prompts for the agent
- Analyze the exported EVTX files for PowerShell Empire indicators.
- Check events 4104 and 4103 for
System.Net.WebClient,FromBase64String, andInvoke-Mimikatzactivity. - Create a JSON report with IOCs, decoded payloads, and MITRE ATT&CK mappings.
How to install analyzing-powershell-empire-artifacts
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a claude-code2Manually: put the files in place
~/.claude/skills/analyzing-powershell-empire-artifacts/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/analyzing-powershell-empire-artifacts/
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a codex2Manually: put the files in place
.agents/skills/analyzing-powershell-empire-artifacts/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a cursor2Manually: put the files in place
.cursor/skills/analyzing-powershell-empire-artifacts/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mukul975/Anthropic-Cybersecurity-Skills skills/analyzing-powershell-empire-artifacts2Manually: put the files in place
.github/skills/analyzing-powershell-empire-artifacts/SKILL.md1Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a gemini-cli2Platform CLI
gemini skills install https://github.com/mukul975/Anthropic-Cybersecurity-Skills --path skills/analyzing-powershell-empire-artifactsManually: put the files in place
.devin/skills/analyzing-powershell-empire-artifacts/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about analyzing-powershell-empire-artifacts
How do I install analyzing-powershell-empire-artifacts in Claude Code?
Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a claude-code, then check ~/.claude/skills/analyzing-powershell-empire-artifacts/SKILL.md.
What does analyzing-powershell-empire-artifacts do?
It scans events 4104 and 4103 for PowerShell Empire artifacts such as the launcher, encoded payloads, module calls, and staging URLs, then creates a JSON report.
What does the skill need to run?
It needs Python 3.9+, access to Windows Event Log or EVTX files, and Script Block Logging plus Module Logging enabled through Group Policy.
Source text
SKILL.md · Apache-2.0
--- name: analyzing-powershell-empire-artifacts description: Detect PowerShell Empire post-exploitation framework artifacts in Windows Script Block Logging (Event ID 4104) and Module Logging (Event ID 4103), including the default launcher string, Base64-encoded WebClient/FromBase64String payloads, known module invocations (Invoke-Mimikatz, Invoke-Kerberoast), and staging URL patterns. Use when hunting for or confirming Empire C2 activity in Windows event logs. domain: cybersecurity subdomain: threat-hunting tags: - PowerShell-Empire - threat-hunting - Script-Block-Logging - base64 - stager - C2 - MITRE-ATT&CK - T1059.001 - forensics version: '1.0' author: mahipal license: Apache-2.0 d3fend_techniques: - Executable Denylisting - Execution Isolation - File Metadata Consistency Validation - Content Format Conversion - File Content Analysis nist_ai_rmf: - GOVERN-1.1 - MEASURE-2.7 - MANAGE-3.1 nist_csf: - DE.CM-01 - DE.AE-02 - DE.AE-07 - ID.RA-05 mitre_attack: - T1059.001 - T1071.001 - T1003.001 - T1558.003 - T1027.010 --- # Analyzing PowerShell Empire Artifacts ## Overview PowerShell Empire is a post-exploitation framework consisting of listeners, stagers, and agents. Its artifacts leave detectable traces in Windows event logs, particularly PowerShell Script Block Logging (Event ID 4104) and Module Logging (Event ID 4103). This skill analyzes event logs for Empire's default launcher string (`powershell -noP -sta -w 1 -enc`), Base64 encoded payloads containing `System.Net.WebClient` and `FromBase64String`, known module invocations (Invoke-Mimikatz, Invoke-Kerberoast, Invoke-TokenManipulation), and staging URL patterns. ## When to Use - When investigating security incidents that require analyzing powershell empire artifacts - 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 - Python 3.9+ with access to Windows Event Log or exported EVTX files - PowerShell Script Block Logging (Event ID 4104) enabled via Group Policy - Module Logging (Event ID 4103) enabled for comprehensive coverage ## Key Detection Patterns 1. **Default launcher** — `powershell -noP -sta -w 1 -enc` followed by Base64 blob 2. **Stager indicators** — `System.Net.WebClient`, `DownloadData`, `DownloadString`, `FromBase64String` 3. **Module signatures** — Invoke-Mimikatz, Invoke-Kerberoast, Invoke-TokenManipulation, Invoke-PSInject, Invoke-DCOM 4. **User agent strings** — default Empire user agents in HTTP listener configuration 5. **Staging URLs** — `/login/process.php`, `/admin/get.php` and similar default URI patterns ## Output JSON report with matched IOCs, decoded Base64 payloads, timeline of suspicious events, MITRE ATT&CK technique mappings, and severity scores.
© mahipal · Apache-2.0 · mukul975/Anthropic-Cybersecurity-Skills