National Cyber Warfare Foundation (NCWF)login

Erebus for orchestrating initial access payload generation inside Mythic


0 user ratings
2026-11-10 21:26:58
milo
Red Team (CNA)
"Erebus

Erebus is a Mythic initial access wrapper that automates building loaders, triggers, containers, and maldocs for authorized red team engagements, this documentary analysis covers its architecture and defensive detection angles.








ToolWhispergate/Erebus — initial access payload generation wrapper for the Mythic C2 framework
Categoryoffensive security tooling / payload engineering framework
Primary UseComposing loader + trigger + container + maldoc delivery chains inside Mythic during authorized engagements, with per-build YARA/Sigma self-validation
Safe UseFor authorized penetration tests, purple-team exercises, and lab environments only; never against systems you do not own or lack written permission to test
Telemetry NoteGenerates per-build YARA + Sigma rules and automated IOC hash reports, giving blue teams a ready-made detection corpus for every artifact it produces

Erebus positions itself as a modern initial access wrapper for the Mythic command and control framework, written in Python under a BSD-2-Clause license, and its stated goal is compressing the development-to-deployment time when an authorized operator prepares engagement infrastructure. Rather than being a standalone implant, it functions as a build orchestration layer: it consumes shellcode from a Mythic agent or any external C2 (the README explicitly lists Cobalt Strike, Havoc, Sliver, and msfvenom), then packages that payload into whatever delivery artifact the operation requires. At roughly 222 stars on GitHub, it sits in that interesting tier of tooling that is mature enough to have a real changelog culture but niche enough that every capability is still documented in one README. This writeup is a documentary analysis of what the project exposes publicly, aimed at both red teamers evaluating it and defenders who will inevitably encounter its output.


Architecturally, Erebus is a Mythic payload type container, and installation follows the standard mythic-cli pattern: sudo ./mythic-cli install github https://github.com/Whispergate/Erebus, followed by sudo ./mythic-cli start erebus_wrapper if the platform is already running. Once integrated, it appears in the Mythic interface with documentation rendered under the agent documentation pane. This containerized design matters because it means all builds happen server-side through the Mythic API, which in turn enables the tool's most operator-friendly feature: matrix builds that iterate across every trigger/container combination so an engineer can survey which delivery formats survive a target's tooling before committing to one in a lab exercise.


The loader layer is where the engineering investment is most visible. The native C++ shellcode loader ships as exe, dll, or xll output and carries eleven injection techniques cataloged by type, spanning remote options like NtMapViewOfSection, EarlyCascade, two PoolParty variants, NtQueueApcThread, TxfHollow, and ProcessHollow, alongside self-injection approaches such as CreateFiber, ModuleStomp, KernelCallbackTable, and FunctionStomp. Cross-platform coverage is real rather than checkbox-deep: Linux builds get mmap_thread, memfd_exec, process_vm_writev, and ptrace injection across ELF executables and .so files suitable for LD_PRELOAD delivery, while macOS targets receive Mach-O executables and dylibs using MAP_JIT and Mach thread injection. A more exotic VM loader implements a RISC virtual machine with per-build randomized opcodes, XOR key derivation, and an encrypted instruction set, a design that guarantees no two builds share a byte pattern.


The evasion stack reads like a survey of the last several years of offensive-security research. Indirect syscalls are available through TartarusGate as the default on x64, SysWhispers3 as an alternative, and Heaven's Gate for x86 WoW64 processes issuing native 64-bit syscalls. Callstack spoofing is configurable with a gadget-host module list defaulting to ntdll, kernel32, and kernelbase. The AMSI bypass offers five tiers, including a patchless hardware-breakpoint plus vectored exception handler variant that writes no bytes to amsi.dll, and the ETW bypass covers EtwEventWrite, EtwEventWriteFull, and provider unregistration across four tiers. Sleep obfuscation ranges from none through WaitableTimer, an Ekko-lite XOR of PE sections, an Exhaustion mode combining Fibonacci burn with API hammering, and full Ekko with stack XOR and PE header wiping.


What elevates Erebus above a mere feature aggregator is its compile-time guardrail system, which bakes anti-analysis logic directly into builds. Documented checks include IsDebuggerPresent, remote debugger detection, debugger process enumeration, hardware breakpoint detection, timing anomaly checks, sandbox environment checks, and host/user/IP/domain allowlists, allowing an operator to constrain execution to precisely the authorized lab or engagement target set. There is also a PE sanitisation pass that strips MinGW fingerprints, the rich header, PE timestamps, and the debug directory, which removes many of the static tells that free compilers leave behind in student-built tooling.


The trigger catalog is unusually broad and worth enumerating for defensive readers precisely because these are the lures analysts will see. On Windows, twenty-three trigger types are listed, from classics like LNK, HTA, CHM, and OneNote to newer social-engineering patterns such as ClickFix (a clipboard-lure fake CAPTCHA), HTML and SVG smuggling, geofenced HTML variants that gate on country codes, password-gated encrypted HTML using PBKDF2, a VSCode extension .vsix trigger, and LOLBAS delivery via CMSTP, Regsvr32/Squiblydoo, XSL transforms, and InstallUtil. Linux offers four triggers and macOS eight, including .command files, AppleScript, PKG installers, app bundles both unsigned and ad-hoc signed, and DMG images. Container formats span ISO, VHD, 7z, Zip, MSI, an Electron fake NSIS installer with interaction-gated guardrails, and AppInstaller/MSIX, with support for two-layer chains wrapping an inner container in an outer ISO or VHD transport.


The maldocs subsystem demonstrates the same depth. Excel output covers XLSM, XLSX, XLAM, and native XLL add-in DLLs; Word covers DOCM, DOC, and DOCX with remote template injection fetching a DOTM on open; PowerPoint covers PPTM and PPAM. Four VBA loader techniques are implemented, and notably VBA is compiled natively on Linux without Office installed, which makes the build pipeline container-friendly. A staged HTTP mode uploads RC4-encrypted shellcode to the Mythic file store at build time so that the document contains no shellcode bytes and no plaintext URLs. The obfuscation pipeline, derived from Shellcrypt by 0xLegacyy, chains compression (LZNT1/RLE), encryption (RC4/XOR/AES-ECB/AES-CBC), and encoding (BASE64, ASCII85, ALPHA32, WORDS256) with per-build keys.


From a defensive perspective, the most commendable design decision in Erebus is its self-hunt rule generation: every build emits per-build YARA and Sigma rules intended for operator validation, and an automated IOC tracker collects hashes and generates reports. This turns each artifact into a paired offensive/defensive dataset, which is exactly the kind of symmetry purple teams ask for and rarely get. Blue teams can use the generated rules to validate EDR coverage against each loader variant, test AMSI and ETW telemetry assumptions, and exercise their phishing pipeline against the documented trigger formats, all inside their own lab ranges.


The supporting capabilities round out the operational picture without crossing into anything this analysis needs to operationalize. Donut integration converts PE and .NET assemblies to shellcode; MSI backdooring injects payloads into existing installers; redirector configuration generation emits Apache .htaccess, Nginx, Caddyfile, and Terraform stubs; and a phishing page generator supports credential capture with redirects and GoPhish webhooks, with decoy document inclusion for social engineering scenarios. Persistence modules cover registry run keys, scheduled tasks, COM hijacking (T1546.015), WMI event subscriptions (T1546.003), and macOS LaunchAgent (T1543.001), all mapped to MITRE ATT&CK identifiers, which again signals an audience that writes reports rather than causes chaos.


The changelog shows a genuinely active project. Version v0.0.1 fixed build steps and loader decompression; v0.0.2 improved error handling and added the MSC GrimReaper trigger plus support for larger shellcodes such as Apollo and Athena; v0.1.0 was a major refactor into the plugin architecture and introduced HTML/SVG smuggling, callstack spoofing, and cross-platform loaders; v0.2.0 moved to async build calls so the container no longer appears offline during compilation, added the patchless AMSI bypass, the VSCode and OneNote triggers, the LOLBAS triggers, injection techniques nine through eleven, and full Ekko sleep obfuscation. Known issues are honestly documented, including a broken VBA address-of-entry-point injection, mangled C++ export names occasionally skipped in DLL proxy generation, and CHM/OneNote triggers requiring a deferred Erebus.Helper build on Windows.


The plugin architecture deserves its own note: drop-in Python plugins for triggers, containers, loaders, and persistence require no core code changes, which means an authorized team can extend Erebus with proprietary techniques without maintaining a fork. The contributions section credits Mgeeky, 0xLegacyy for Shellcrypt, and Cody Thomas for the Mythic framework itself and the Apollo agent and service_wrapper, which tells you the project is well-connected within the operator community it serves.


Erebus is best understood as an opinionated framework for the least glamorous but highest-stakes phase of an authorized engagement: getting the first payload to execute. Its breadth, from Heaven's Gate syscalls to geofenced HTML lures, reflects how high the defensive bar has climbed, and its self-hunt rule generation reflects a maturity that treats detection validation as a first-class output. For defenders, studying its public capability catalog is a free curriculum in modern initial access tradecraft; for authorized operators, it is a well-structured, actively maintained option that trades some silver-bullet ambition for honest documentation of what it does and does not do.



Official project repository for Whispergate/Erebus.

Download Tool

Educational analysis for authorized security professionals. Use only in controlled, authorized environments.






Source: OffensiveSec
Source Link: https://www.offsecblog.com/2026/11/erebus-for-orchestrating-initial-access.html


Comments
new comment
Nobody has commented yet. Will you be the first?
 
Forum
Red Team (CNA)



Copyright 2012 through 2026 - National Cyber Warfare Foundation - All rights reserved worldwide.