mythic-payload
05.1 — Mythic Payload
Authorized use only: Use these notes only in owned, explicitly authorized, or isolated lab environments.
Detection awareness: Assume commands, binaries, network calls, identity changes, and cloud or directory actions may be logged by endpoint tooling, audit frameworks, SIEM pipelines, proxy logs, DNS logs, auth logs, and platform telemetry.
Blue-team view: Treat every technique as a defender validation exercise too: note what artifacts it creates, what alerts or hunts could surface it, and what monitoring or hardening would prevent or contain it.
CTF/lab boundary: If a sandbox or CTF includes bypass-oriented exercises, keep them confined to that environment and translate the lesson into detection, prevention, and cleanup notes rather than real-world evasion guidance.
This file has been superseded by a full operator-grade guide.
Full coverage is in: 7.4 Mythic C2 Operator Guide
- Section 3: Agent selection matrix (Apollo, Athena, Medusa, Hannibal, Poseidon)
- Section 4: C2 profile selection (http, dns, smb, websocket)
- Section 5: Payload generation + OPSEC-tuned settings
- Section 6: Apollo deep-dive (BOF, token ops, injection, SOCKS5, lateral movement)
- Section 9–10: DNS and SMB P2P profiles
- Section 11: HTTP header customization
- Section 12: Redirector integration
- Section 16: Pre/post-engagement OPSEC checklist