SkillAgentSearch skills...

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),…

Install / Use

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Security

Supported Platforms

Universal

Our assessment of analyzing-powershell-empire-artifacts

analyzing-powershell-empire-artifacts scores 86/100 on our quality scale, 713th of 1,108 Security skills we index.

Its SKILL.md is 2.8 KB long, split into 6 sections and no code examples: a solid amount of guidance for an agent.

With 36,115 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
19/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so analyzing-powershell-empire-artifacts is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-25. Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

analyzing-powershell-empire-artifacts compared with similar skills

All 4 of these similar skills score higher than analyzing-powershell-empire-artifacts; compare them before choosing.

SkillScoreStarsUpdatedFormat
analyzing-powershell-empire-artifacts (this skill)by mukul9758636.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install analyzing-powershell-empire-artifacts?
Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-powershell-empire-artifacts. The install tabs above show the steps for each supported agent.
Which AI agents does analyzing-powershell-empire-artifacts work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is analyzing-powershell-empire-artifacts safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is analyzing-powershell-empire-artifacts still maintained?
The repository was last updated about 3 months ago, so analyzing-powershell-empire-artifacts is actively maintained.

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.

Related Skills

View on GitHub
GitHub Stars36.1k
CategorySecurity
Updated2mo ago
Forks4.4k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions