create_taskingfunction to alter what user's see - this helps with ugly large json blocks from using structured input. The original parameters can still be queried through the UI if the user wants to see the original JSON
create_taskingto help with debugging or recreating artifacts
build_stdoutfor stdout and stderr messages to make it easier to see what happened during creation. This split information is also viewable via the Created Payloads page.
mythicPyPi package) has been updated to version 0.0.19 to support these changes
opsecfunction to your C2 Profiles to check if the parameters that the operator selected pass your risk-level before even allowing a payload to be created.
MYTHIC_DEBUGenvironment variable or
debugset to true in the
mythic-docker/config.jsonfile will cause mythic to be extremely verbose in agent messages to help with debugging development
pip install mythic_payloadtype_container==0.0.42.
itsafeaturemythicrepo, update to the latest:
pip install mythic_c2_container
mythic_encrypts = Falsein the builder file for your Payload Type.
AESPSK. Instead, there is another field you can specify for any parameter that
crypto_type=True. This specifies that the resulting thing that the user selects/inputs defines what kind of crypto to use. This is simply a boolean value so that you can still leverage the C2 Parameter as normal (string input, choose one, etc) with the expectation that the final value is the type of crypto. In the case of Mythic's standard crypto, the value would be
aes256_hmac. This means that Mythic no longer auto-generates a base64 of an AES256 key when displayed to the user, this happens behind the scenes if the resulting type is
crypto_type=True, then you'll get a dictionary of values. This is split out by type, encryption key, and decryption key because you might want to leverage some pub/priv key asymmetric crypto where those pieces are different or you might want to leverage some other kind of symmetric crypto.
mythic==0.0.19package for scripting to handle the updated aspects of these objects.
ctrl+]to navigate previous/next tab in the
set description my descriptionand reset it back to the default for the payload with
set description reset
./start_apfell.sh viperwill only start the
viperpayload type container, but all of the c2 profiles and main containers will still start.