Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is PowerShell Empire?

PowerShell Empire is an open-source post-exploitation and command-and-control framework whose agents run inside PowerShell and .NET, making it a long-standing favourite of red teams and criminals alike.

Illustration for the cybersecurity term PowerShell Empire
Home / Blog / Cybersecurity Terms / What Is PowerShell Empire?
17 November 2026

What Is PowerShell Empire?

What Is PowerShell Empire?

PowerShell Empire is a post-exploitation framework. Once an operator has code execution on a Windows host, Empire gives them an agent that calls home, a console to drive it, and a library of modules for credential theft, privilege escalation, enumeration, and lateral movement. The original selling point was that it needed no executable on disk: everything ran inside PowerShell, which Windows trusts by default.

It was released in 2015 by researchers at Veris Group and quickly became a standard red team tool. The original maintainers retired the project in 2019, declaring that the defensive improvements in Windows 10 had done their job. BC Security forked it the same year, and Empire has been actively developed ever since, now with a .NET agent, a web interface called Starkiller, and modules that no longer depend on PowerShell at all.

How the Framework Is Structured

ComponentFunction
ListenerThe server side that receives agent traffic over HTTP, HTTPS, SMB named pipes, or third-party services
StagerA short piece of code that retrieves and launches the full agent, delivered as a one-liner, macro, HTA, or shortcut
AgentThe implant that beacons to the listener, asks for tasks, and returns results
ModuleA capability run through the agent, such as credential dumping or domain enumeration

Agents beacon on an interval with a configurable jitter so the pattern is not perfectly regular. Operators set that interval according to how much patience they have and how much noise they are willing to make. Communication is encrypted, and profiles can be shaped so the HTTP requests resemble ordinary web traffic.

What It Is Used For

Empire covers the familiar post-exploitation ground: harvesting credentials from memory, collecting Kerberos tickets, mapping Active Directory, bypassing user account control, establishing persistence through scheduled tasks and registry keys, and pivoting onwards. Many of its modules are wrappers around well-known offensive tooling, so a defender who recognises Mimikatz output or SharpHound collection is already halfway to recognising Empire.

Like every framework in this category, it does not stay in authorised hands. Empire has been reported in intrusions attributed to state-aligned groups and criminal operators, often alongside commodity loaders, precisely because it is free, documented, and does the job. Its presence on a host is therefore never evidence of an authorised test.

Why Windows Caught Up

Empire’s original advantage disappeared as Microsoft instrumented PowerShell. Four controls did most of the damage:

Combine these with endpoint detection and response and the framework becomes difficult to run undetected in default form, which is why modern operators customise heavily or move to alternatives such as Sliver.

Detecting It

Look for PowerShell launched with encoded commands, hidden windows, and execution policy bypass flags, especially when the parent process is Word, Excel, Outlook, or a browser. Watch for System.Management.Automation.dll loading into processes that are not PowerShell, which indicates a hosted runspace. On the network, default Empire profiles have recognisable URI patterns, user agents, and TLS fingerprints, and regular beaconing with consistent payload sizes stands out in Zeek or proxy logs even when individual requests look innocuous.

Named pipe listeners used for SMB-based agents are another reliable signal, since legitimate software uses a predictable set of pipe names and attacker-chosen ones rarely match.

Reducing Your Exposure

Enable script block logging and transcription everywhere and ship both to your SIEM. Keep PowerShell v2 uninstalled, because it predates AMSI and logging entirely. Deploy application control so unsigned scripts and binaries cannot run from user-writable locations, and enforce Constrained Language Mode where the business can tolerate it. Restrict outbound traffic through an inspecting proxy so a beacon cannot simply dial out on port 443.

Our Red Team Services use frameworks of this type under controlled conditions to show which of those controls actually fire in your environment.

FAQ – Frequently Asked Questions

Is PowerShell Empire Still Maintained?

Yes. The original project was retired in 2019, but BC Security forked it and has continued development since, adding a .NET agent, the Starkiller web interface, and modules that no longer rely on PowerShell. Much of the detection guidance written for the original release still applies, because the core listener, stager, agent, and module architecture is unchanged.

Should We Disable PowerShell to Stop It?

Disabling PowerShell outright is rarely practical, since administration, deployment tooling, and Windows itself depend on it, and attackers simply move to other interpreters. The effective approach is instrumentation and constraint: remove PowerShell v2, enable script block logging and transcription, apply application control with Constrained Language Mode, and restrict who can run remote sessions.

Does Antivirus Detect Empire?

Default stagers and modules are detected by most modern products, largely thanks to AMSI scanning scripts and in-memory assemblies before execution. Experienced operators obfuscate payloads and modify profiles to evade signatures, so signature detection alone is not a control. Behavioural detection of credential access, enumeration bursts, and beaconing is what catches customised deployments.

Which Event Logs Reveal Empire Activity?

Event 4104 from PowerShell script block logging is the most valuable, because it records deobfuscated code. Add events 4103 for module logging, 400 and 403 for engine start and stop, 4688 process creation with command lines, and 7045 for service creation used in persistence. Sysmon event 8 for remote thread creation and event 10 for LSASS access complete the picture.

Related Terms

You May Be Interested In These

What Are OWASP MASVS and MASTG?

Cybersecurity Terms

17 November 2026

What Are OWASP MASVS and MASTG?

Read More
What Is SIEM Cost Optimisation?

Cybersecurity Terms

17 November 2026

What Is SIEM Cost Optimisation?

Read More