Mythic Profiles

Scope

Use this skill for Mythic C2 profile development: profile container layout, C2Profile definitions, parameter modeling, listener/server implementation, P2P versus egress profile decisions, and integration with Mythic payload types.

Use $mythic-implant-development instead when the primary task is implementing an agent/payload type or agent commands. Use this skill when the primary artifact is a C2 profile/listener/transport.

Workflow

1. Classify the profile

   • Egress profile: server-side code receives agent traffic and forwards to Mythic /agent_message.
   • P2P profile: no listening server; parameters define agent-to-agent connection details.
   • Translation-aware profile: coordinate with a translation container if wire format or crypto differs from Mythic messages.

2. Set up the development loop

   • Read references/remote-development.md when the task involves local/remote Mythic development, container iteration, or installed-service workflow.
   • Confirm profile folder name, C2Profile name, and Mythic installed service name align.
   • Use focused container restarts and payload-build smoke tests during iteration.