github BC-SECURITY/Empire v7.1.0

one hour ago

[7.1.0] - 2026-10-14

  • Updated Starkiller to v4.1.0

Security

  • Fixed the persistence/osx/LaunchAgent module staging its plist through a predictable /tmp path and running chown/mv via subprocess with shell=True; the plist is now written directly to the LaunchAgents directory with no shell (BC-SECURITY/Empire#828).
  • Fixed the persistence/osx/CreateHijacker module writing its patched dylib to a predictable, world-writable /tmp/<dylib name> path; it now patches a mkstemp file in place.
  • Fixed command injection through the global obfuscation command: it is no longer passed through a shell, and is validated against the Invoke-Obfuscation command grammar before use.
  • Fixed command injection through the MSF_Format option of the windows/cmd_exec stager: msfvenom is now invoked with an argument list instead of a shell command string.
  • Fixed arbitrary file write through the BinaryFile option of the linux/pyinstaller stager: the build now runs in a server-owned temporary directory and only the option's file name is used.
  • Hardened the http listener's unauthenticated ?stager= endpoint so unknown languages are rejected before any database query, and removed the temp artifacts compiled stager builds leave behind on both listeners.
  • Stopped a staging-key holder provoking a listener 500 -- and with it the IIS cover story -- by discarding routing packets whose session ID is not valid UTF-8 and rejecting invalid Diffie-Hellman peer keys in all four STAGE1 branches.
  • Confined the http_hop listener's OutFolder and the redirect listener's profile URIs to downloads/http_hop, closing an arbitrary file write available to any non-admin operator.
  • Confined the OutFile option of the PowerBreach eventlog, deaduser and resolver modules to downloads/generated-modules, closing an arbitrary file write available to any non-admin operator.
  • Rejected an OutFolder or OutFile that resolves onto the shared output directory itself, which one operator could turn into a regular file and wedge every other operator's writes.
  • Confined the ExtFile, File and Shellcode module path options to the downloads directory, closing an arbitrary file read available to any enabled operator.
  • Anchored the upload directory to the downloads root in _secure_upload_location, so a traversing user.username or subdirectory cannot place a file outside it.
  • BREAKING: STAGE1 Ed25519 signatures now cover the handshake transcript instead of the constant "SIGNATURE", so a captured certificate cannot be replayed with a substituted DH key. Re-stage all pre-7.1 agents.
  • BREAKING: The AES-CBC payload layer derives separate AES and HMAC keys from the shared key with HKDF-SHA256 (empire-enc / empire-mac) instead of reusing one key.
  • C# (Sharpire) agents now authenticate the server: the csharp staging branch sends a transcript-bound server certificate, which the agent verifies before deriving the session key.

Added

  • Added logging.file_logging (env EMPIRE_LOGGING__FILE_LOGGING) for console-only container logging, plus logging.max_bytes and logging.backup_count rotation limits.

Changed

  • persistence/osx/LaunchAgent and persistence/osx/CreateHijacker now refuse to generate while the shipped Mach-O templates link Apple's removed Python 2.7 framework, instead of planting a binary that cannot load on macOS 12.3 or later; the module descriptions say so, pending a template rebuild.
  • BREAKING: The linux/pyinstaller stager's BinaryFile option is now a bare file name defaulting to empire rather than /tmp/empire — any directory component is ignored and the built binary is no longer left on the server at that path, though it is still delivered under OutFile as before.
  • BREAKING: The http and http_malleable listeners now serve their default response instead of a Werkzeug 500 page for any error that escapes a view.
  • BREAKING: The http_hop listener's OutFolder is now relative to downloads/http_hop and defaults to redirectors; hop listeners stored with an absolute path outside it no longer start.
  • BREAKING: OpenAPI operation ids are now {tag}_{route name} (e.g. agents_read_agent) instead of FastAPI's path-and-method default, which also renames the three generated Body_* request schemas — a generated client needs no post-processing of the spec, but every method name it produces changes.
  • BREAKING: The agent-task and plugin-task routes are tagged with only their primary resource, dropping the tasks tag group.
  • BREAKING: The /api/v2/obfuscation routes moved from the keywords tag to obfuscation.
  • BREAKING: empire_server.log and listener_<name>.log now rotate at 10 MB with 5 backups, deleting older data; set logging.max_bytes: 0 for unbounded logs.
  • BREAKING: The ExtFile, File and Shellcode module options must now name a path inside the server's downloads directory; saved workflows pointing elsewhere are rejected until the file is uploaded through the API.
  • A listener's Host may now carry the public port while Port stays the bind port, for deployments behind a reverse proxy. A Host without a port still advertises the bind port. The listener-generated HTTP-family and malleable launchers and stagers use the advertised address; the windows/c_launcher stager and PIC shellcode still pair the hostname with the bind Port. The malleable listener still decides whether it serves TLS, and whether its agent comms trust a self-signed certificate, from the scheme in Host. The Port cannot be provided in a host name validation error is gone. (#808)
  • C# (Sharpire) stagers now embed the listener's server Ed25519 public key so the agent authenticates the server during staging; requires Empire-Compiler v2.0.3, which this release pins.

Fixed

  • Fixed gopire ignoring the listener's 401 (tasking polls now GET with the listener's session cookie instead of a hard-coded session) and a lost limit that never fired (0 now disables it); undecodable or empty 200s and a profile with no task URIs now count as misses.
  • Empire Compiler downloads now retry transient GitHub failures with backoff and are installed atomically; a failed or corrupt download no longer crashes server startup.
  • Fixed multi/generate_agent ignoring the Bypasses option when generating a stageless agent; bypasses matching the agent's language are now prepended to it, and IronPython drops Python bypasses as staged generation does (BC-SECURITY/Empire#778).
  • Fixed powershell/privesc/bypassuac_tokenmanipulation always emitting an empty -enc argument, so the elevated process never fetched the stager; it now encodes the cradle as UTF-16LE, assumes http:// for a bare Host, and rejects at generation time a Host carrying userinfo, a port, a path, control characters, or a non-http(s) scheme, an invalid Port, and a Stager that is empty or could break out of the single-quoted cradle (BC-SECURITY/Empire#547).
  • Fixed management/osx/shellcodeinject64 crashing on any real shellcode file (bytes passed to str.replace) and on an empty Shellcode path (directory read); both now generate or raise a validation error.
  • Fixed collection/osx/native_screenshot_mss embedding a bytes repr (b'...') in its emitted script, which the agent-side base64 decode turned into garbage.
  • Fixed the Python and IronPython agents building but never sending the error packet for a failed foreground Python task, which left the task pending forever with no output.
  • Fixed persistence/osx/LaunchAgent, persistence/osx/LaunchAgentUserLandPersistence, persistence/osx/CreateHijacker and privesc/multi/bashdoor emitting Python 2 code (octal literals, except E, e, text-mode binary I/O) that failed to compile or run on the Python 3 agent. LaunchAgentUserLandPersistence now launches with an absolute Python 3 path resolved on the agent (its own interpreter, falling back to python3 on PATH) instead of the removed python, and CreateHijacker raises on failure so a failed hijack no longer reports as a completed task.
  • Fixed a BinaryFile with an extension (agent.bin) failing the linux/pyinstaller stager with an opaque 500, and a BinaryFile of empire.py returning the plaintext launcher source in place of the compiled binary.
  • Fixed a failed pyinstaller, a missing or unrunnable msfvenom, and an unusable BinaryFile, MSF_Format or Arch value surfacing as a 500 instead of a stager-generation error naming the cause.
  • Fixed the malleable PowerShell stager splitting custom headers on commas, which broke any profile header value containing a comma, such as a Chrome User-Agent. Header entries are now separated with a dedicated marker. (#829)
  • Fixed the http, http_hop, and port_forward_pivot PowerShell stagers and comms dropping the custom headers from DefaultProfile. They are now rendered into a $Script:Headers hashtable that the stager and the agent send on every request. (#831)
  • Fixed the malleable /init/ default stager URI being added alongside the URIs a profile's http-stager block declares, so launchers could pick a URI the profile never defined. Launchers generated before this change that call /init/ against such a profile must be regenerated.
  • Fixed the malleable PowerShell launcher dropping the ? before a stager block's parameter query string (Crimeware/quantloader, Crimeware/jasperloader).
  • Fixed listener autorun failures during agent staging rolling back Stage 2 registration: a failing autorun entry is now logged and skipped, remaining autorun entries still execute, and AFTER_AGENT_CHECKIN_HOOK fires for every agent that completes staging.
  • Fixed NameError: name 'job_message_buffer' is not defined when a background Python job (e.g. python/collection/linux/xkeylogger) streams output via job_message_buffer(...), by exposing it in the exec scope used by python_job_func.
  • Fixed the PowerBreach eventlog and resolver modules reporting a successful OutFile write as "PowerBreach deaduser backdoor written to".
  • Fixed an unwritable PowerBreach OutFile surfacing as an opaque 500 instead of a 400 naming the output directory.
  • Fixed the Go staging branch intermittently rejecting valid STAGE1 bodies (~0.3%) by sizing the body with len(message) instead of the length of its repr.
  • Fixed staging desyncing (~1 in 256) when the server's DH public key had a leading zero byte; the server and every agent now use a fixed 768-byte width.
  • Sharpire stagers now receive the listener's default response; a template typo left the REPLACE_DEFAULTRESPONSE placeholder unsubstituted.

Don't miss a new Empire release

NewReleases is sending notifications on new releases.