mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-07-17 05:05:16 +03:00
mukul975
35 lines
2.0 KiB
Markdown
35 lines
2.0 KiB
Markdown
---
|
|
name: analyzing-powershell-empire-artifacts
|
|
description: Detect PowerShell Empire framework artifacts in Windows event logs by identifying Base64 encoded launcher patterns, default user agents, staging URL structures, stager IOCs, and known Empire module signatures in Script Block Logging events.
|
|
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
|
|
---
|
|
|
|
# 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.
|
|
|
|
## 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.
|