In short
Havoc C2 is an open-source post-exploitation command-and-control framework, first released on GitHub in October 2022. Operators run a server and deploy an implant called Demon on Windows hosts. Red teams use it for authorized testing. Threat actors, from spam-call intruders to the WIRTE group, have used it to control breached systems.
Key takeaways
- What it is
- An open-source post-exploitation C2 framework, first released in October 2022 and tracked by MITRE ATT&CK as software S1229.
- How it works
- Operators control a server; the Demon implant on a Windows host checks in over HTTP or HTTPS and runs tasks such as shell commands, process injection and file transfer.
- Why it matters
- Zscaler and Huntress have documented Havoc in real intrusions, including a 2026 help-desk impersonation campaign across five organizations.
- What Odin Research saw
- 25 Havoc endpoints on 23 hosts in Monograph 19, none confirmed as hostile. Most listen on port 443 or 8443 on large cloud providers.
- What to do first
- Hunt for Demon's memory-evasion behavior with EDR and YARA, and treat unsolicited IT support calls that end in remote access as a serious alert.
What is Havoc C2?
Havoc C2 is an open-source post-exploitation command-and-control framework. Its author, C5pider, first released it on GitHub in October 2022. Operators run a server and plant an implant called Demon on target hosts. Red teams use it for authorized tests. Threat actors use it to control breached systems.
MITRE ATT&CK tracks Havoc as software S1229. ATT&CK describes it as maintained with community contributions and used by multiple threat actors. It lists the WIRTE group as one known user.
Havoc sits in the same family as Cobalt Strike, Sliver and Mythic. Like them, it gives an operator a remote control channel after the first foothold. See our glossary entry on command and control for the general model.
Because the code is free and public, Havoc is a dual-use tool. A Havoc server on the internet may belong to a penetration testing team. It may also belong to an intruder. The server alone does not tell you which.
How Havoc C2 works
A Havoc deployment has two sides. The operator controls a server that holds listeners. The Demon implant runs on a breached Windows host and calls back to a listener.
- Listener. The operator opens an HTTP or HTTPS listener. Odin Research saw most public Havoc listeners on ports 443 and 8443.
- Check-in. Zscaler ThreatLabz reported that Demon checks in over HTTP and sends AES-encrypted metadata about the host.
- Tasking. The operator queues tasks. ATT&CK lists PowerShell and Windows command shell use, process discovery, screen capture, file transfer, token theft, DLL and PE injection, and proxying.
- Sleep. Between check-ins, Demon hides in memory.
That last step is what makes Havoc evasive. Zscaler documented indirect syscalls, return-address stack spoofing and sleep obfuscation techniques named Ekko and FOLIAGE. Odin Research describes the same pattern in Monograph 19. Timer callbacks switch Demon's memory to read-write, encrypt it with the Windows SystemFunction032 (RC4) routine during sleep, and make it runnable again on wake-up.
The result: a memory scan during sleep finds encrypted bytes, not a readable implant. User-mode API hooks used by many EDR tools see fewer direct calls. For the technique involved, see Process Injection (T1055).
Havoc origin, versions and status
According to MITRE ATT&CK, Havoc was first released in October 2022 by C5pider (Paul Ungur). It runs against Windows, Linux and macOS environments, although public reporting focuses on the Windows Demon implant.
Huntress reported in March 2026 that the public Havoc repository was archived on 20 February 2026. An archived repository is read-only. That does not remove the tool from use. The source stays available, and Huntress found operators building their own customized Demon versions from it.
Is Havoc legal? The framework is legal to download and use for authorized testing. Running it against systems without written permission is illegal in most countries.
How attackers use Havoc C2
Public research shows Havoc used by very different actors:
- Government target, 2023. On 14 February 2023, Zscaler ThreatLabz described a campaign against a government organization. A ZIP archive carried a downloader and a lure document. The final payload was Demon, loaded by shellcode that patched ETW event logging.
- Help-desk impersonation, 2026. On 2 March 2026, Huntress reported intrusions at five partner organizations in February 2026. Attackers flooded inboxes with spam, then called users posing as IT support. They gained remote access through Quick Assist or AnyDesk and delivered a customized Demon.
- Espionage. MITRE ATT&CK lists the WIRTE group as a Havoc user, for access maintenance and C2.
The Huntress case shows how operators modify the code. Huntress found a registry-based fallback C2 list, encrypted with ChaCha20, that stock Havoc does not have. It also found indirect syscalls through Hell's Gate and Halo's Gate, plus scheduled tasks that rebuilt the implant at boot.
Huntress did not attribute the activity. It noted overlap with a January 2025 Sophos report that linked similar campaigns to Black Basta and FIN7. The phone step is classic vishing.
What Odin Research observed
Havoc appears in Monograph 19, which studied six evasive C2 frameworks over a two-week window ending 18 November 2026. Havoc was the smallest of the six.
- 25 endpoints, none confirmed. Havoc ran on 25 endpoints across 23 hosts. Five were suspected, 19 were candidates and one was an open directory. No Havoc address was published for blocking.
- Mainstream cloud hosting. The endpoints sat on AWS, DigitalOcean, Oracle and Hostinger. Thirteen listened on port 443 and four on 8443.
- A placeholder certificate. One suspected server in Vietnam presented a placeholder certificate on port 8443, a common sign of an unconfigured listener.
- Shared hosts. On at least one host not published in the report, Havoc ran next to a HexStrike AI tool bridge.
For comparison, the same report counted 391 Cobalt Strike endpoints with 35 confirmed. Havoc is far less common on the open internet, and its servers were harder to confirm. The report notes that Havoc, Mythic, Brute Ratel C4 and Cobalt Strike all have legitimate red-team users.
How to detect Havoc C2
Detection should focus on the host, where Demon's tricks leave traces:
- Sleep-mask code. Look for
SystemFunction032,CreateTimerQueueTimerandNtContinueused together in one binary or memory region. - Unbacked call stacks. Return-address spoofing and indirect syscalls produce call stacks that point into memory with no file behind it. Kernel call-stack telemetry can flag this.
- ETW tampering. A process that patches
EtwEventWriteis hiding its own events, as Zscaler documented in the 2023 loader. - Injection into odd hosts. Zscaler and Huntress both saw injection into processes such as
notepad.exe. A notepad process with network traffic is worth a look. - Help-desk chain. Quick Assist or AnyDesk sessions that follow a spam flood, followed by an unsigned DLL side-load, match the Huntress pattern.
On the network, a self-signed or placeholder certificate on 443 or 8443 is a lead, not a verdict. Pair it with a JARM fingerprint and host data.
Monograph 19 publishes a YARA rule for the Havoc Demon sleep mask, plus a Sigma rule for unbacked call stacks touching LSASS. They are in the report and in the Defense Kit.
How to defend against Havoc C2
- Harden the help desk path. Tell staff that IT will not cold-call them to fix spam. Restrict Quick Assist and unapproved remote tools with application control.
- Turn on deep endpoint telemetry. Enable kernel call-stack telemetry, Credential Guard and LSA protection, as Monograph 19 recommends.
- Watch scheduled tasks and registry. Huntress saw persistence through scheduled tasks and C2 lists stored in the registry.
- Limit egress. Servers and workstations that never need arbitrary HTTPS should go through a proxy that logs destinations.
- Respond fully. If you find Demon, assume credential theft. Reset affected accounts and check for lateral movement before you close the case.
Havoc C2 compared with other C2 frameworks
| Framework | Implant | Endpoints in Monograph 19 | Confirmed | Notes |
|---|---|---|---|---|
| Havoc C2 | Demon | 25 | 0 | Open source; sleep obfuscation; mostly ports 443 and 8443 |
| Cobalt Strike | Beacon | 391 | 35 | Commercial; reused certificate templates helped confirm many servers |
| Brute Ratel C4 | Badger | 690 | 4 | Most hits were VPN exits sharing a Go TLS fingerprint |
| Mythic | Several agents | 54 | 2 | Default admin and C2 port 7443 |
Source for counts: Monograph 19.
Frequently asked questions about Havoc C2
What is Havoc C2?
Havoc C2 is an open-source post-exploitation command-and-control framework, first released on GitHub in October 2022. Operators run a server and control breached hosts through an implant called Demon.
Is Havoc malware?
Havoc is a dual-use tool. It was built for red teams, but MITRE ATT&CK tracks it as software S1229 because multiple threat actors use it. A Demon implant you did not deploy should be treated as malware.
Is Havoc legal to use?
Yes, for authorized testing on systems you own or have written permission to test. Using it against other systems is illegal in most countries.
Who made Havoc?
MITRE ATT&CK credits C5pider (Paul Ungur) with the first release in October 2022. The project was maintained with community contributions. Huntress reported that the repository was archived on 20 February 2026.
What is the Havoc Demon?
Demon is Havoc's implant. It runs on a breached Windows host, checks in to the operator's listener, runs tasks and hides in memory between check-ins using sleep obfuscation.
Which threat actors use Havoc?
MITRE ATT&CK lists the WIRTE group. Zscaler documented a 2023 campaign against a government organization, and Huntress documented 2026 help-desk impersonation intrusions that it did not attribute to a named group.
How do I detect Havoc C2?
Look for sleep-mask code that combines SystemFunction032, CreateTimerQueueTimer and NtContinue, unbacked call stacks, ETW patching and odd process injection. Odin Research publishes a YARA rule for the Demon sleep mask in its Defense Kit.
Havoc vs Cobalt Strike: what is the difference?
Both are post-exploitation C2 frameworks. Cobalt Strike is commercial and far more common: Odin Research counted 391 endpoints against 25 for Havoc. Havoc is free and open source, which makes it easy for anyone to modify.
Sources
- MITRE ATT&CK, Havoc, S1229. attack.mitre.org/software/S1229 (checked 21 November 2026)
- Zscaler ThreatLabz, "Havoc Across the Cyberspace", 14 February 2023. www.zscaler.com/blogs/security-research/havoc-across-cyberspace (checked 21 November 2026)
- Huntress, "Exorcising Demons: Fake Tech Support Delivers Havoc Command & Control", 2 March 2026. www.huntress.com/blog/fake-tech-support-havoc-command-control (checked 21 November 2026)
- Salesforce Engineering, "Easily Identify Malicious Servers on the Internet with JARM". engineering.salesforce.com/easily-identify-malicious-servers-on-the-internet-with-jarm-e095edac525a/ (checked 21 November 2026)
Related tools and terms
What is Sliver?
Sliver is an open-source command-and-control (C2) framework from Bishop Fox, written in Go. Red teams use it for adversary emulation, and criminal and state operators use it as a free alternative to Cobalt Strike.
C2 frameworkWhat is Brute Ratel C4?
Brute Ratel C4 is a commercial red-team C2 framework built to evade endpoint detection. Leaked copies have been used by criminal operators.
C2 frameworkWhat is Mythic?
Mythic is an open-source, multi-user C2 platform with pluggable agents and transports, built for red-team operations.
Offensive frameworkWhat is Metasploit?
Metasploit is an open-source penetration testing framework maintained by Rapid7. It bundles exploits, payloads and the Meterpreter post-exploitation agent.
Offensive frameworkWhat is Viper?
Viper is an open-source browser front end for Metasploit. It adds a multi-operator web interface and a module runner on top of the Metasploit RPC service.
Adversary emulationWhat is Caldera?
Caldera is MITRE's open-source adversary emulation platform. It plans and runs ATT&CK techniques through agents such as Sandcat.
Odin Research
Get the rules, not just the definition
Every Odin Research report ships with verified indicators and detection rules you can load today.