Mythic/C2_Profiles
will be treated like a docker container specific to C2 profiles (more on this in the C2 section).Mythic/Payload_Types
will be treated like a docker container specific to a payload type (such as apfell, atlas, etc)sudo ./mythic-cli c2 stop {c2_profile_name}
or sudo ./mythic-cli c2 stop
to stop all of them.sudo ./mythic-cli payload stop {payload_type_name}
or sudo ./mythic-cli payload stop
to stop all of them.sudo ./mythic-cli database reset
.sudo ./mythic-cli payload start {payload_type_name}
and just that container will start/restart. If you want to start multiple, just do spaces between them: sudo ./mythic-cli payload start {payload type 1} {payload type 2}
.root
if any ports under 1024 need to be used.mythic-cli
and list out what's registered in the docker-compose file vs what you have available on your system:Sanic
, python3 web server. This main Mythic server connects to a PostgreSQL database where information about the operations lives. Each of these are in their own docker containers. When Mythic needs to talk to any payload type container or c2 profile container, it does so via RabbitMQ, which is in its own docker container as well.itsafeaturemythic
DockerHub repository: https://hub.docker.com/search?q=itsafeaturemythic&type=image.