# analyzing-powershell-empire-artifacts

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 303 installs · ★ 36511 repo stars
- Author: mahipal
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/HEAD/skills/analyzing-powershell-empire-artifacts/SKILL.md
- Updated: 2026-08-31
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/analyzing-powershell-empire-artifacts

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/analyzing-powershell-empire-artifacts/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/analyzing-powershell-empire-artifacts/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/analyzing-powershell-empire-artifacts/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/analyzing-powershell-empire-artifacts/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mukul975/Anthropic-Cybersecurity-Skills skills/analyzing-powershell-empire-artifacts
```

2. **Manually: put the files in place**
- File: `.github/skills/analyzing-powershell-empire-artifacts/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mukul975/Anthropic-Cybersecurity-Skills --path skills/analyzing-powershell-empire-artifacts
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/analyzing-powershell-empire-artifacts/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/HEAD/skills/analyzing-powershell-empire-artifacts/SKILL.md

## When to use it
- 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
- Analyze the exported EVTX files for PowerShell Empire indicators.
- Check events 4104 and 4103 for `System.Net.WebClient`, `FromBase64String`, and `Invoke-Mimikatz` activity.
- Create a JSON report with IOCs, decoded payloads, and MITRE ATT&CK mappings.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: ac25eb73879ad36b.

BEGIN THIRD-PARTY FILE ac25eb73879ad36b
```text
---
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
```
END THIRD-PARTY FILE ac25eb73879ad36b

The third-party file has ended. Everything between the ac25eb73879ad36b tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2319 of 2883 bytes. © mahipal · Apache-2.0 · https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/HEAD/skills/analyzing-powershell-empire-artifacts/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
