PAGES
← all tools
◆ Exploitation & C2

Mythic

v3.1.0 open-source

Mythic is a cross-platform, post-exploit, red teaming framework providing a collaborative, web-based interface for operators managing command and control operations.

Summary

Mythic is an open-source command-and-control platform for red teaming operations, free to use. It runs as a self-hosted set of Docker containers behind a reverse proxy, with a React web UI, a GoLang backend, and Postgres and RabbitMQ handling data and messaging, all controlled through the mythic-cli binary; agents and C2 profiles are installed separately from GitHub rather than bundled in the core repository. It targets red team operators and the managers who need reporting across an engagement, tracking payload provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build., task history, and network artifacts for OpSec and deconfliction. The README describes it as a cross-platform, post-exploit framework built for collaborative, multiplayer use rather than solo operation. First committed in 2018 and backed by SpecterOps sponsorship, it has 34 contributors and over 300 commits in the past year, with its latest release about ten months old.

Mythic is a cross-platform, post-exploit, red teaming framework providing a collaborative, web-based interface for operators managing command and control operations.

How Mythic helps

What footprint has this operation left on the target network so far?

agents and commands can record process creates, file writes, API calls, and network connections as artifacts, either when a task is issued or as agents report them back, building an OpSec-relevant trail

Are two operators about to collide on the same host without knowing it?

shared tracking of callbacks, tasking, and network artifacts across the team surfaces overlapping footprints so deconfliction is based on recorded activity rather than memory

Which ATT&CK techniques has this engagement actually exercised?

ties tasked commands to MITRE ATT&CK mappings, giving a technique-level view of coverage across the operation for reporting

all 8 features, with the evidence for each →

Languages

Not documented

Features

8 capabilities · 5 backed by code, an API document or a real run

Built from Mythic's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What Mythic offers you

  • Command-line interface1
  • Outbound webhooks (the product notifies you)1
All capabilities 8 capabilities
Update checking verified Checks whether updates are available for the Mythic platform. 4 other sources · first seen Dec 2025

docs

  • Cross-platform, post-exploit red teaming framework with a web UI for collaborative operator management, payload types, and C2 profiles.

command line

example

  • Check for available Mythic updates ./mythic-cli update
  • Check updates against a specific branch ./mythic-cli update -b [branch name]
Component uninstall and cleanup verified Uninstalls Mythic components such as mythic_sync and removes associated files and dangling images from disk. 2 other sources · first seen Dec 2025

command line

Custom webhook notifications shipped Allows agent payloads to send custom alerts via webhooks with structured metadata. 1 release · 1 other source · first seen Oct 2023

Also counts toward: Outbound webhooks (the product notifies you)

release

  • Adds new send_webhook boolean and webhook_alert dictionary fields to agent alert responses for custom webhook notifications v3.1.0 · Oct 2023 · source · release history

example

  • Send a custom webhook alert from an agent payload with specific metadata. { "alert": "Warning: suspicious process", "send_webhook": true, "webhook_alert": { "severity": "high", "custom_id": "12345" } } v3.1.0 · Oct 2023 · source
Typed parameter support for commands shipped Enables the definition of command parameters with specific data types (e.g., integers, strings) to support generic BoF/COFF tasking. 1 release · 1 other source · first seen Oct 2023

release

  • Adds TypedArray parameter type for commands and build parameters to support generic BoF/COFF style tasking with typed data tuples v3.1.0 · Oct 2023 · source · release history

example

  • Define a parameter that accepts typed data (e.g., integers and strings) for a custom BoF command. "my_bof_args": { "type": "TypedArray", "value": [ ["int", 5], ["char*", "testing"], ["wstring", "this is my string"] ] } v3.1.0 · Oct 2023 · source
Service connection testing verified Tests connectivity to Mythic's internal services to verify they are reachable. 1 other source · first seen Dec 2025

command line

Version inspection verified Reports the current versions of mythic-cli and the Mythic platform. 1 other source · first seen Dec 2025

command line

  • version — Print information about the mythic-cli and Mythic versions v3.4.0.28 · Dec 2025 · command-line history
Volume management verified Provides commands to inspect and interact with Mythic's Docker volumes. 1 other source · first seen Dec 2025

Also counts toward: Command-line interface

command line

File serving via RPC shipped Allows C2 profiles to serve files through RPC channels using the host_file_through_c2 option. 1 release · first seen Oct 2023

release

  • Adds host_file_through_c2 option available for all payloads and files to let the C2 profile serve files via RPC v3.1.0 · Oct 2023 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Mythic, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Mythic puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

1 entry

  1. October 20231
    Show

    1 entry

    Project health

    Issue, contributor and maintainer activity in its-a-feature/Mythic, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 10 +5 vs prior 12 months
    2. Maintainers 1 +0 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 1.5 days first maintainer reply 18 hours
    6. Open backlog 28 of 316 issues ever filed
    1. Issues opened / month 3 · 0 communitymaintainers
    2. Open backlog 28
    3. Contributors / month 1
    4. Commits / month 1
    5. Stars 4,775
    Issue themes, last 12 months
    • bugs 14%
    • other 86%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Articles

    1 article · updated Nov 4, 2026

    Where Mythic turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.

    Breach post-mortems & incident response 1

    Ships a vulnerable library

    What its latest release locks, checked against known advisories.

    browserslist 4.24.4 in its MythicReactUI image

    high

    Mythic 3.4.0.5 builds its MythicReactUI image from MythicReactUI/package-lock.json, which locks browserslist 4.24.4. That version has GHSA-73wf-gq98-2v4g and 1 other high or critical flaw.

    Fixed in browserslist 4.28.7. No Mythic release includes it yet.

    GHSA-73wf-gq98-2v4g advisory Checked Nov 4 against Mythic 3.4.0.5

    fast-uri 3.0.6 in its MythicReactUI image

    high

    Mythic 3.4.0.5 builds its MythicReactUI image from MythicReactUI/package-lock.json, which locks fast-uri 3.0.6. That version has GHSA-4c8g-83qw-93j6 and 7 other high or critical flaws.

    Fixed in fast-uri 3.1.7. No Mythic release includes it yet.

    GHSA-4c8g-83qw-93j6 advisory Checked Nov 4 against Mythic 3.4.0.5

    nanoid 3.3.11 in its MythicReactUI image

    high

    Mythic 3.4.0.5 builds its MythicReactUI image from MythicReactUI/package-lock.json, which locks nanoid 3.3.11. That version has GHSA-28wg-ghj8-5hjv and 2 other high or critical flaws.

    Fixed in nanoid 3.3.18. No Mythic release includes it yet.

    GHSA-28wg-ghj8-5hjv advisory Checked Nov 4 against Mythic 3.4.0.5

    postcss 8.4.49 in its MythicReactUI image

    high

    Mythic 3.4.0.5 builds its MythicReactUI image from MythicReactUI/package-lock.json, which locks postcss 8.4.49. That version has GHSA-6g55-p6wh-862q and 1 other high or critical flaw.

    Fixed in postcss 8.5.18. No Mythic release includes it yet.

    GHSA-6g55-p6wh-862q advisory Checked Nov 4 against Mythic 3.4.0.5

    react-router 7.5.2 in its MythicReactUI image

    high

    Mythic 3.4.0.5 builds its MythicReactUI image from MythicReactUI/package-lock.json, which locks react-router 7.5.2. That version has GHSA-2w69-qvjg-hvjx and 6 other high or critical flaws.

    Fixed in react-router 7.18.0. No Mythic release includes it yet.

    GHSA-2w69-qvjg-hvjx advisory Checked Nov 4 against Mythic 3.4.0.5

    serialize-javascript 6.0.2 in its MythicReactUI image

    high

    Mythic 3.4.0.5 builds its MythicReactUI image from MythicReactUI/package-lock.json, which locks serialize-javascript 6.0.2. That version has GHSA-5c6j-r48x-rmvq.

    Fixed in serialize-javascript 7.0.3. No Mythic release includes it yet.

    GHSA-5c6j-r48x-rmvq advisory Checked Nov 4 against Mythic 3.4.0.5

    source-map-js 1.2.1 in its MythicReactUI image

    high

    Mythic 3.4.0.5 builds its MythicReactUI image from MythicReactUI/package-lock.json, which locks source-map-js 1.2.1. That version has GHSA-68fv-2mgg-jv7q.

    Fixed in source-map-js 1.2.2. No Mythic release includes it yet.

    GHSA-68fv-2mgg-jv7q advisory Checked Nov 4 against Mythic 3.4.0.5

    turbo-stream 2.4.0 in its MythicReactUI image

    high

    Mythic 3.4.0.5 builds its MythicReactUI image from MythicReactUI/package-lock.json, which locks turbo-stream 2.4.0. That version has GHSA-rxv8-25v2-qmq8.

    Fixed in turbo-stream 3.0.0. No Mythic release includes it yet.

    GHSA-rxv8-25v2-qmq8 advisory Checked Nov 4 against Mythic 3.4.0.5

    We check the lockfiles its release builds images from: 1 npm. Go modules, other lockfiles and vendored code aren't checked.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →