Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / C2 and post-exploitation

What Is Starkiller? The Empire C2 Web Interface Explained

The browser front end for BC Security's Empire framework: what it does, why red teams and intruders both run it, and how to find it on your network.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
Adversary emulation tool

In short

Starkiller is the web-based graphical interface for Empire, an open-source post-exploitation and adversary emulation framework maintained by BC Security. Written in Vue.js and bundled with Empire since version 5.0, it lets operators manage listeners, agents and modules from a browser. Red teams use it, and threat groups have used Empire in real intrusions.

Key takeaways

What it is
A Vue.js web application, published by BC Security under the MIT license, that serves as the front end for the Empire command and control (C2) framework.
How it works
Starkiller talks to the Empire server through its API. Operators log in, create listeners, generate agents and run post-exploitation modules from one browser console.
Why it matters
MITRE ATT&CK lists Empire use by groups such as Turla, MuddyWater, Wizard Spider and APT41. A Starkiller console can be a red-team asset or an intruder's.
What Odin Research saw
Five Starkiller nodes running multi-user Empire consoles in Monograph 22, none confirmed as hostile. Two used Empire's REST port 1337 and three used port 80.
What to do first
Register every sanctioned Empire host, put consoles behind a VPN or mutual TLS, and turn on PowerShell script block logging on Windows endpoints.

What is Starkiller?

Starkiller is the web-based graphical interface for Empire, an open-source post-exploitation and adversary emulation framework maintained by BC Security. It runs in a browser and lets one or more operators manage Empire listeners, agents and modules without the command line. Red teams use it for authorized tests, and intruders use the same software.

The project describes Starkiller as a frontend for PowerShell Empire, written in Vue.js. Empire is the backend. Starkiller holds no attack logic of its own. It is a control panel for the command and control (C2) server behind it.

Empire has a long history. MITRE ATT&CK tracks it as software S0363, with the aliases EmPyre and PowerShell Empire. A joint advisory by five national cyber security agencies says Empire was first designed as a penetration testing tool in 2015. The BC Security repository is a fork of the original EmpireProject code.

So when defenders find Starkiller, they have found an Empire server. The open question is who runs it and whether they have permission.

How Starkiller works

Starkiller sits on top of three Empire building blocks:

  1. Listeners. These are the server-side endpoints that agents call back to. Empire's README lists HTTP/S, Malleable HTTP, Foreign, Hop, SMB and Port Forward Pivot listeners.
  2. Agents. Empire generates implants in PowerShell, Python 3, C#, IronPython 3 and Go. MITRE notes that Windows agents are PowerShell and Linux and macOS agents are Python.
  3. Modules. Post-exploitation tasks such as credential theft, discovery and lateral movement, run through an agent.

The Empire server is written in Python 3. It exposes an API, and Starkiller connects to that API. Since Empire 5.0 and Starkiller 2.0, Starkiller ships inside Empire as a submodule and is served by the Empire server itself. No separate install is needed.

An operator logs in to Starkiller, creates a listener, builds an agent and delivers it to a target. Once the agent checks in, the operator picks modules from the console and reads results there. Several operators can share one server. The Starkiller README also lists a file browser, chat widget, dashboard, graph view and malleable profile management, plus extra features for project sponsors.

Because the console is a web application, the server must expose a login page. That login page is one of the clearest network signs of a Starkiller install.

Starkiller versions, license and popularity

Starkiller is MIT-licensed, with copyright held by BC Security. Empire uses the BSD-3-Clause license. The Starkiller repository had about 1,700 stars and 247 forks on 21 November 2026. The Empire repository had about 5,400 stars and 708 forks.

Empire's README lists Docker, Kali, ParrotOS, Ubuntu 22.04 and 24.04, and Debian 12 and 13 as supported platforms. Building Starkiller from source needs Node.js 22 or later and pnpm 11 or later, but most users get it bundled with Empire.

Is Starkiller legal? Yes, as software. It is a published open-source project used by red and purple teams. Using it against systems you do not own or have written permission to test is illegal in most countries.

How attackers use Starkiller and Empire

Starkiller itself is a console, so attacker use is really Empire use. MITRE ATT&CK lists many groups that have used Empire, including Turla, MuddyWater, Wizard Spider, APT41, APT33, Sandworm Team, FIN10 and the Play ransomware group.

MITRE's entry describes a wide set of capabilities:

  • Credential access: LSASS memory dumping through a Mimikatz implementation, Kerberoasting, golden and silver tickets, and pass-the-hash.
  • Lateral movement: DCOM, SSH, PsExec, WMI and PowerShell remoting.
  • Persistence: Registry Run keys, scheduled tasks, modified shortcut files and Group Policy changes.
  • C2: HTTP and HTTPS, plus Dropbox or GitHub for C2 and exfiltration.

The joint advisory AA18-284A, issued in 2018 by agencies in Australia, Canada, New Zealand, the UK and the US, named Empire among five widely used public hacking tools. It says Empire runs largely in memory through PowerShell, which helps it slip past traditional antivirus. The advisory cites a 2018 incident at a UK energy company and a 2017 APT19 phishing campaign against a law firm.

What Odin Research observed

Odin Research covered Starkiller in Monograph 22, a study of shared team C2 consoles. Addresses stay withheld because none of these hosts is confirmed as hostile.

  • Five Starkiller nodes. Each ran a multi-user console for Empire. Operators log in through the Empire v2 user login API path.
  • Two port patterns. Two nodes used Empire's REST port 1337, one in the United States and one in Finland. Three used port 80 on OVH in France.
  • Grouped with Caldera. The report places Starkiller with MITRE Caldera as emulation planners. Together they account for 262 endpoints, and none of them is confirmed.
  • Dual use is the norm. Purple teams and attack-simulation vendors run the same unmodified Empire servers. The report lists all five Starkiller servers in that group and keeps them on watchlists, not block lists.

The lesson is simple. A Starkiller login page tells you which tool is running. Your own asset register tells you whether it should be there.

How to detect Starkiller

Look for Starkiller and Empire from two sides:

  • The console. Outbound or inbound HTTP requests that post to the Empire v2 user login path point to a Starkiller session. Treat this as a policy alert, since your own red team may cause it.
  • Exposed servers. Scan your own attack surface for Empire consoles on port 1337 or on plain web ports. Any server you did not register is worth a look.
  • The agents. Empire's Windows agents run PowerShell, often in memory. The joint advisory recommends full PowerShell logging, including script block logging and transcripts, and removing old PowerShell versions that bypass newer logging.
  • Web beacons. Empire's HTTP listeners fall under Application Layer Protocol. Regular check-ins from a workstation to a new external server deserve review.

Monograph 22 publishes a Suricata file with a signature for Starkiller and Empire v2 operator logins, marked as dual-use. It also ships a Microsoft Sentinel query that covers console URIs. Both are in the Defense Kit.

How to defend against Empire and Starkiller misuse

  1. Keep a register of sanctioned servers. List every approved Empire, Caldera and Metasploit host in your SIEM allowlists, so a real hit stands out.
  2. Lock down your own consoles. Put Starkiller behind mutual TLS or a VPN. Do not leave an emulation console open to the internet.
  3. Constrain PowerShell. The joint advisory recommends code integrity features, script signing, application allowlisting and constrained language mode, tested first.
  4. Watch, then block. A Starkiller banner alone is weak evidence. Route unknown consoles to analysts and block only when a second signal appears.
  5. Hunt credential abuse. Empire modules wrap tools such as Mimikatz. Watch for LSASS access and unusual Kerberos ticket requests.

Starkiller compared with other team C2 consoles

ConsoleWhat it frontsDefault sign seen by OdinOdin handling
StarkillerEmpire, multi-operator post-exploitationEmpire v2 login API, port 1337 or 80Watchlist (dual-use)
MITRE CalderaAutomated planners with Sandcat and Manx agentsAgent download and beacon pathsWatchlist (dual-use)
AdaptixC2Plugin teamserver with swappable listenersDefault adaptix or localhost certificatesWatchlist unless confirmed
SuperShellBrowser shell console with reverse SSHSelf-signed certificate named after port 3232Block when confirmed

Frequently asked questions about Starkiller

What is Starkiller?

Starkiller is the web-based graphical interface for Empire, an open-source post-exploitation and adversary emulation framework maintained by BC Security. It lets operators manage listeners, agents and modules from a browser.

Is Starkiller malware?

No. Starkiller is a legitimate, MIT-licensed console for an adversary emulation framework. It is dual-use: threat groups have used Empire in real intrusions, so defenders track Starkiller servers they did not approve.

What is the difference between Starkiller and Empire?

Empire is the server, written in Python 3, that runs listeners, agents and modules. Starkiller is the Vue.js web front end that connects to Empire's API. Since Empire 5.0, Starkiller is bundled with Empire.

Who made Starkiller?

BC Security publishes and maintains Starkiller and its own fork of Empire. The original Empire project came from the EmpireProject repository, which BC Security's version forks.

Is Starkiller legal to use?

Yes, on systems you own or have written permission to test. Running Empire or Starkiller against systems without authorization is illegal in most countries.

Which threat groups use Empire?

MITRE ATT&CK lists Turla, MuddyWater, Wizard Spider, APT41, APT33, APT19, Sandworm Team, FIN10 and the Play ransomware group, among others, as users of Empire.

How do I detect Starkiller on my network?

Look for HTTP posts to the Empire v2 login path, unregistered Empire consoles on port 1337 or web ports, and in-memory PowerShell agents. Odin Research publishes a Suricata signature and a Sentinel query for these signs in its Defense Kit.

Should I block every Starkiller server I find?

No. Red and purple teams run the same software. Odin Research keeps Starkiller servers on watchlists and acts only when a second, independent signal points to hostile use.

Sources

  1. BC Security, Starkiller repository, GitHub. github.com/BC-SECURITY/Starkiller (checked 21 November 2026)
  2. BC Security, Empire repository, GitHub. github.com/BC-SECURITY/Empire (checked 21 November 2026)
  3. MITRE ATT&CK, Empire (S0363). attack.mitre.org/software/S0363/ (checked 21 November 2026)
  4. CISA and partners, joint advisory AA18-284A on publicly available hacking tools. www.cisa.gov/news-events/cybersecurity-advisories/aa18-284a (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit