sudo ./mythic-cli database reset
and then pull in the updates and sudo ./mythic-cli mythic start
again../mythic-cli install github <url> [branch] [-f]
command to remove the old version and pull in the new version.sudo ./mythic-cli database reset
and delete your Mythic/.env
file../mythic-cli install
script and point it to the address for an agent or c2 profile:itsafeaturemythic/csharp_payoad:0.0.11
Docker image, this is where you'll find that.mythic_payloadtype_container
PyPi package hosted on PyPi.mythic_c2_container
PyPi package hosted on PyPi.mythic_translator_container
PyPi package hosted on PyPi.mythic
(and right now specifically the mythic_rest
) scripting capabilities and hosted on PyPi.mythic-cli
, with the source code available to all at the Mythic_CLI repository.mythic-cli
binary instead of the support scripts, but if you find a place that doesn't, be sure to report it.docker run
commands for the agents and c2 profiles. This worked initially, but now that more and more environment variables are randomized and configurable, there needs to be a way to centrally configure everything. So, starting with Mythic 2.2.4, all configuration happens within the Mythic/.env
file and all containers are in the Mythic/docker-compose.yml
file. When you install agents, Mythic will automatically parse and update this docker-compose file to add in the necessary information. Similarly, you can add/remove agents/c2 profiles at any time from this file via mythic-cli {payload|c2} {add|remove} [name]
. If you already have agents installed that you want to register, the add
command will allow you to update your docker-compose file without having to re-install your agent or c2 profile. You can also use the mythic-cli {payload|c2} list
feature to show what containers exist within your docker-compose file and which ones exist on disk.sudo ./mythic-cli database reset
, you can go to the Payloads page and select to export a payload configuration. This takes all the information as needed to generate a payload and saves it as a new JSON file through your browser. Then, at some time later, on the Payloads creation page, there's a new button on the top right to import a configuration. You can load in this JSON file and automatically trigger a new build of that payload.build
function as:process_response
key in your post_response messages (Process Response) and have your own custom messages sent back to your Command's Python file and then use Mythic's RPC functionality to register the same information. This really does give you the ability to do pretty much everything custom, while still hooking into Mythic.MYTHIC_DEBUG=True
when starting Mythic, then all of these stages will send event messages to the event feed with context and information. This can be extremely helpful during development, but will be very overwhelming during production.https://mythic_ip:7443
, but now your connections are transparently proxied back to the documentation container and the graphql container for you./new/login
then you'll be presented the login for the new UI and can start seeing where Mythic is going in the future. We've already started implementing some of our newer features in this React UI such as: