Mythic Translation Containers

Scope

Use this skill when the main artifact is a Mythic translation container rather than an implant or C2 profile. Translation containers convert between Mythic's internal C2 message model and a custom agent wire format, and can generate or manage cryptographic keys for payload builds.

Use $mythic-profiles for listener/transport container work. Use $mythic-implant-development for payload type and agent command implementation.

Workflow

1. Decide whether translation is required

   • Required when the agent wire format is not Mythic's default JSON message format.
   • Required when custom crypto is used with mythic_encrypts = False.
   • Useful when multiple profiles/agents share a binary or service-specific envelope.

2. Wire payload type to translation container

   • Set translation_container = "<container_name>" in the payload type definition.
   • Ensure container name is lowercase-safe for Docker image naming.
   • Keep the container name stable; payload types and installed services depend on it.