In short
Mythic C2 is an open-source, cross-platform command-and-control framework for red-team operations. Operators run it as Docker containers and control agents on Windows, Linux and macOS through a shared web interface. Agents and C2 profiles install separately, so teams can mix transports such as HTTPS, WebSocket and SMB. Threat actors have adopted it too.
Key takeaways
- What it is
- An open-source, multi-user C2 framework written in Go, run as Docker containers, with agents for Windows, Linux and macOS.
- How it works
- Operators install agents and C2 profiles separately. Agents send Base64 messages that join a UUID with an encrypted JSON body over HTTPS, WebSocket, SMB, TCP or even GitHub and Discord.
- Why it matters
- Kaspersky reported in December 2025 that groups such as Mythic Likho and GOFFEE use Mythic, and MITRE notes Mythic servers in potentially malicious infrastructure.
- What Odin Research saw
- 54 Mythic endpoints on 46 hosts, 2 confirmed, mostly on DigitalOcean and AWS. Both confirmed listeners used the default port 7443.
- What to do first
- Deconflict with your red team, then hunt for default Mythic certificates, UUID-prefixed Base64 traffic and unexpected SMB pipe links.
What is Mythic C2?
Mythic C2 is an open-source, cross-platform command-and-control (C2) framework built for red-team operations. It runs as a set of Docker containers behind a browser-based interface that several operators share. Its agents run on Windows, Linux and macOS, and new agents and communication channels plug in without changes to the core.
The project is published on GitHub under the its-a-feature account. The repository describes Mythic as a cross-platform, post-exploit red teaming framework built with Go, Docker, docker-compose and a web browser UI. It states that the software is meant for authorized security assessments and research. On 21 November 2026 the repository had about 4,900 stars and 632 forks.
MITRE ATT&CK tracks Mythic as software S0699. Its entry notes that deployed Mythic C2 servers have been observed as part of potentially malicious infrastructure. That makes Mythic a dual-use tool: the same command-and-control server serves a contracted penetration test and a real intrusion.
How Mythic C2 works
Mythic separates the server from the parts that touch a target. According to its documentation, teams can add payload types, C2 profiles, translation services, eventing functions and chat integrations without rebuilding the core server.
- The server and interface. A React web interface talks to a Go server through GraphQL. PostgreSQL stores operation data and RabbitMQ moves messages between services. Each service runs in its own container, on one host or on remote container hosts.
- Payload types (agents). The core repository ships no agents. Operators install them separately from GitHub with the
mythic-clitool. Kaspersky counted more than a dozen agents, written in Go, Python and C#, for Windows, macOS and Linux. - C2 profiles (transports). Profiles define how an agent talks home. Kaspersky describes direct HTTP, HTTPS and WebSocket channels, peer-to-peer links over SMB named pipes and TCP, and covert channels through Discord and GitHub.
Kaspersky reports that agent messages are Base64-encoded and join an agent UUID with an AES-256-encrypted JSON body. The framing changes with the protocol, for example length-prefixed messages over TCP.
Mythic also tracks the whole operation. The documentation lists the payload, build settings, C2 configuration, issuing operator, tasks, artifacts, credentials and files. Commands can carry MITRE ATT&CK technique mappings, which appear in matrix and ATT&CK Navigator views. MITRE maps Mythic to techniques such as Application Layer Protocol (T1071), Encrypted Channel (T1573), Protocol Tunneling (T1572) and Proxy (T1090), including domain fronting.
Mythic C2 requirements, versions and popularity
The GitHub README says Mythic runs as Docker containers managed with docker-compose. The mythic-cli binary is built from the repository and then starts the stack and checks for updates. The documentation describes Mythic 4.0 additions such as scoped API tokens, operation and AI chat, operator aliases, interactive eventing approvals and resumable file transfers.
The README credits several contributors besides the repository owner, including djhohnstein, xorrior and Airzero24. With about 4,900 GitHub stars, Mythic is smaller than the best-known commercial frameworks but widely used by red teams and trainers.
Is Mythic legal? Downloading and running it is legal. Using it against systems you do not own or have written permission to test is not. Keep it inside a documented engagement scope.
How attackers use Mythic C2
In December 2025, Kaspersky reported that several threat actors had adopted Mythic. It named the groups Mythic Likho (also tracked as Arcane Wolf) and GOFFEE (also tracked as Paper Werewolf), and said the framework keeps appearing in APT and other attacks.
Attackers like Mythic for the same reasons red teams do:
- It is free and modular. An operator can pick an agent per platform and swap transports without changing tools.
- Its traffic blends in. HTTPS and WebSocket channels look like web traffic, and the Discord and GitHub profiles ride on services many networks allow.
- Peer-to-peer links hide internal hosts. SMB and TCP agents relay through each other, so only one host needs to reach the internet. This supports lateral movement with little outbound traffic.
Kaspersky also notes that encrypted SMBv3 and TLS traffic without decryption make signature detection hard, and that behavioral analysis then produces more false positives.
What Odin Research observed
Odin Research mapped Mythic servers in Monograph 19, a study of evasive C2 frameworks and GPU cracking servers. Addresses that are not confirmed stay withheld.
- 54 endpoints on 46 hosts, 2 confirmed. Mythic was the fifth-largest of six evasive frameworks in the study, after Brute Ratel C4, Cobalt Strike, DarkSword and Overlord.
- Default port first. The report notes that Mythic runs its admin and C2 service on port 7443 by default. The endpoints used ports 80 (18), 443 (14), 7443 (13), 4443 (3) and 8443 (3). Both confirmed listeners sat on 7443 and shared one TLS fingerprint.
- Mainstream clouds. DigitalOcean (13) and AWS (8) hosted the most Mythic endpoints. Four more sat on subscriber telecom networks, where addresses pass between customers.
- Shared hosts. One confirmed Mythic host also ran HexStrike AI. Other hosts paired Mythic with AdaptixC2. One of the 35 multi-listener hubs in the study was a Mythic hub.
- Not every server is hostile. Some Mythic servers carried third-party training certificates and likely belong to trainers, consultants or hobbyists.
The lesson: a Mythic banner tells you what software runs, not who runs it. Block confirmed listeners and treat the rest as hunting leads.
How to detect Mythic C2
- Default TLS certificates. Kaspersky reports that default Mythic certificates can identify its HTTPS traffic. Check certificate subjects on outbound sessions to rare hosts, especially on port 7443.
- Message structure. Base64 bodies that begin with a UUID and carry an encrypted JSON blob are a Mythic trait across several transports, per Kaspersky.
- SMB pipe names. Agent UUIDs can appear in named pipe names on peer-to-peer links. Hunt for random-looking pipes between workstations.
- Service abuse. Frequent API sessions to GitHub or Discord from servers that have no reason to use them deserve a look. Expect noise and tune per environment.
- Your own hosts. Alert on Mythic containers or
mythic-clioutside approved red-team machines.
Odin Research publishes rules for these patterns. Monograph 19 carries a Suricata signature for Mythic agent check-ins (it needs TLS inspection) and a YARA rule for Mythic agent stubs. Both are in the Defense Kit. For rule formats, see YARA and Sigma rules.
How to respond to Mythic C2 activity
- Deconflict first. Ask whether a red team or vendor test is running. Many Mythic sightings are authorized.
- Contain the host. If no test explains it, isolate the endpoint and capture memory before reboot. Agents often live only in memory.
- Block confirmed listeners, not ports. Ports 80, 443 and 7443 carry plenty of legitimate traffic.
- Look sideways. Search for peer-to-peer SMB or TCP links from the first host. Use EDR telemetry and threat hunting to find relayed agents.
- Limit egress. Segment networks so servers cannot open direct sessions to the internet. Follow your incident response plan.
Mythic C2 compared with other C2 frameworks
| Framework | Endpoints in Monograph 19 | Confirmed | What stood out |
|---|---|---|---|
| Mythic | 54 | 2 | Default port 7443; modular agents and transports |
| Brute Ratel C4 | 690 | 4 | 507 hits were commercial VPN exits sharing one TLS fingerprint |
| Cobalt Strike | 391 | 35 | Multi-port hubs with reused certificate templates |
| Overlord | 107 | 4 | Almost half on port 5173 |
| Havoc | 25 | 0 | Mostly on 443 and 8443 |
For another open-source option often seen next to Mythic, see Sliver.
Frequently asked questions about Mythic C2
What is Mythic C2?
Mythic C2 is an open-source, cross-platform command-and-control framework for red-team operations. It runs as Docker containers with a shared web interface and supports pluggable agents and transports for Windows, Linux and macOS.
Is Mythic malware?
No. Mythic is a legitimate red-team framework meant for authorized assessments. It is dual-use: Kaspersky has reported threat actors using it, and MITRE notes Mythic servers in potentially malicious infrastructure.
Is Mythic legal to use?
Yes, on systems you own or are authorized to test. Running it against anyone else's systems without written permission is illegal in most countries.
Who made Mythic?
Mythic is published on GitHub by the its-a-feature account. The README also credits contributors such as djhohnstein, xorrior and Airzero24.
What port does Mythic C2 use?
Odin Research notes that Mythic runs its admin and C2 service on port 7443 by default. In Monograph 19, Mythic endpoints also used ports 80, 443, 4443 and 8443.
Which threat actors use Mythic?
Kaspersky reported in December 2025 that Mythic Likho (Arcane Wolf) and GOFFEE (Paper Werewolf) adopted the framework, and that it continues to appear in APT and other attacks.
How do I detect Mythic C2?
Look for default Mythic TLS certificates, Base64 messages that start with an agent UUID, UUID-like SMB pipe names and unusual API sessions to GitHub or Discord. Odin Research publishes a Suricata and a YARA rule for Mythic in its Defense Kit.
Mythic vs Cobalt Strike: what is the difference?
Mythic is free and open source, with agents and transports installed as separate modules. In Monograph 19, Odin Research counted 54 Mythic endpoints against 391 Cobalt Strike endpoints, so Mythic is far less common on the internet.
Sources
- its-a-feature, Mythic repository, GitHub. github.com/its-a-feature/Mythic (checked 21 November 2026)
- Mythic documentation. docs.mythic-c2.net/ (checked 21 November 2026)
- MITRE ATT&CK, Mythic, S0699. attack.mitre.org/software/S0699/ (checked 21 November 2026)
- Kaspersky Securelist, "Detecting Mythic in network traffic", 11 December 2025. securelist.com/detecting-mythic-in-network-traffic/118291/ (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 Havoc?
Havoc is an open-source post-exploitation C2 framework with a Windows implant called Demon.
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.