Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
| Component | Function |
|---|---|
| Listener | The server side that receives agent traffic over HTTP, HTTPS, SMB named pipes, or third-party services |
| Stager | A short piece of code that retrieves and launches the full agent, delivered as a one-liner, macro, HTA, or shortcut |
| Agent | The implant that beacons to the listener, asks for tasks, and returns results |
| Module | A 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.
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.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.