← LeaderboardThe Skill Leaderboard

analyzing-powershell-empire-artifacts

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.

Published by mukul975 ↗mukul975/Anthropic-Cybersecurity-Skills

Try your first task

analyzing-powershell-empire-artifacts

Start a fresh conversation. Replace the highlighted placeholders.

Use analyzing-powershell-empire-artifacts to analyze [exported EVTX files] for PowerShell Empire indicators and return a JSON report with matched IOCs, decoded payloads, timeline, ATT&CK mappings, and severity scores.

Required inputs

  • [exported EVTX files]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: analyzing-powershell-empire-artifactsdescription: 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: cybersecuritysubdomain: threat-huntingtags: - PowerShell-Empire- threat-hunting- Script-Block-Logging- base64- stager- C2- MITRE-ATT&CK- T1059.001- forensicsversion: '1.0'author: mahipallicense: Apache-2.0d3fend_techniques: - Executable Denylisting- Execution Isolation- File Metadata Consistency Validation- Content Format Conversion- File Content Analysisnist_ai_rmf: - GOVERN-1.1- MEASURE-2.7- MANAGE-3.1nist_csf: - DE.CM-01- DE.AE-02- DE.AE-07- ID.RA-05mitre_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.