its-a-feature/mythicA collaborative, multi-platform, red teaming framework
A cross-platform, post-exploit, red teaming framework built with GoLang, docker, docker-compose, and a web browser UI. It's designed to provide a collaborative and user friendly interface for operators, managers, and reporting throughout red teaming.
Mythic is controlled via the mythic-cli binary. To generate the binary, run sudo make from the main Mythic directory.
From there, you can run sudo ./mythic-cli start to bring up all default Mythic containers.
More specific setup instructions, configurations, examples, screenshots, and more can be found on the Mythic Documentation website.
The Mythic repository itself does not host any Payload Types or any C2 Profiles. Instead, Mythic provides a command, ./mythic-cli install github <url> [-b branch name] [-f], that can be used to install agents into a current Mythic instance.
Payload Types and C2 Profiles can be found on the overview page.
To install an agent, simply run the script and provide an argument of the path to the agent on GitHub:
sudo ./mythic-cli install github https://github.com/MythicAgents/apfell
The same is true for installing C2 Profiles:
sudo ./mythic-cli install github https://github.com/MythicC2Profiles/http
This allows the agents and c2 profiles to be updated at a much more regular pace and separates out the Mythic Core components from the rest of Mythic.
Use the ./mythic-cli update command to check for available updates across mythic-cli, mythic_server, and mythic_react's UI.
This will NOT do the update for you, but let you know if an update exists. To check for updates against a specific branch, use ./mythic-cli update -b [branch name].
Mythic uses Docker and Docker-compose for all of its components, which allows Mythic to provide a wide range of components and features without having requirements exist on the host. However, it can be helpful to have insight into how the containers are configured. All of Mythic's docker containers are hosted on DockerHub under itsafeaturemythic.
Additionally, Mythic uses a custom PyPi package (mythic_container) and a custom Golang package (https://github.com/MythicMeta/MythicContainer) to help control and sync information between all the containers as well as providing an easy way to script access to the server.
Dockerfiles for each of these Docker images can be found on MythicMeta.
The mythic-container PyPi package source code is available on MythicMeta and is automatically installed on all of the mythic_python_* Docker images.
This PyPi package is responsible for connecting to RabbitMQ, syncing your data to Mythic, and responding to things like Tasking, Webhooks, and configuration updates.
The github.com/MythicMeta/MythicContainer Golang package source code is available on MythicMeta.
This Golang package is responsible for connecting to RabbitMQ, syncing your data to Mythic, and responding to things like Tasking, Webhooks, and configuration updates.
All documentation for the Mythic project is being maintained on the docs.mythic-c2.net website. The backing code for the documentation is in the Mintlify_Dcumentation repository in MythicMeta.
A bunch of people have suffered through bug reports, changes, and fixes to help make this project better. Thank you!
The following people have contributed a lot to the project. As you see their handles throughout the project on Payload Types and C2 Profiles, be sure to reach out to them for help and contributions:
This is an open source project meant to be used with authorization to assess the security posture and for research purposes.
