MYTHIC_ADDRESSwhich points to
https://127.0.0.1:7443by default. This information is pulled from the main
/Mythic/mythic-docker/config.jsonfile. So, if you change Mythic's main UI to HTTP on port 7444, then each C2 Docker container's
MYTHIC_ADDRESSenvironment variable will have the value
http://127.0.0.1:7444. This allows your code within the docker container to always know where to forward requests so that the main Mythic server can process them.
task_id, there is some functionality they won't be able to leverage. Specifically, the main functions for C2 profiles are:
create_event_message- This is useful for a c2 profile to send an alert to operators in case something is weird
create_encrypted_message- This is useful for a c2 profile to generate encrypted messages
create_decrypted_message- This is useful for a c2 profile to decrypted messages from callbacks
serverfile as an example). These functions can be useful if you want to implement your own C2 protocol instead of JSON, but you will have to translate to/from JSON and Mythic's format at some point to interact with Mythic.
mythic/c2_functionsfolder can be any number of python files that have defined functions. These functions are automatically imported and available for RPC when the container starts. In this case, a remote container can call this C2's