mcpField
A
analyzing-powershell-empire-artifacts

analyzing-powershell-empire-artifacts

github.com/mukul975Security35.2k295 installsUpdated 8w ago
Repository

About analyzing-powershell-empire-artifacts

This skill helps SOC analysts and threat hunters analyze Windows event logs for traces of PowerShell Empire. It detects launcher, payload, module, and staging URL patterns, then produces a JSON report with a timeline and MITRE ATT&CK mappings.

Key features

  1. 01Analyze Windows event logs or EVTX files
  2. 02Detect the default Empire launcher
  3. 03Find stager and encoded payload indicators
  4. 04Match known modules and URL patterns
  5. 05Report IOCs and suspicious-event timelines
  6. 06Map MITRE ATT&CK techniques

Use cases

  1. 01Investigate incidents involving PowerShell Empire
  2. 02Build detection rules or threat-hunting queries
  3. 03Assess monitoring coverage for related attack techniques

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill analyzing-powershell-empire-artifacts

After installing, type/analyzing-powershell-empire-artifactsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

LICENSE
references/
api-reference.md
scripts/
agent.py

Details

From the project README

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.

Comments

Markdown supported