Tutorial Shows Mythic C2 Relayed Through Discord to Evade Firewall Restrictions
· 28:28 · Watch on YouTube ↗
Summary
The tutorial configures Mythic’s Discord profile and Athena agent to relay commands and callbacks through Discord when a lab host cannot directly reach the external C2 server.
Key points
- The lab scenario features an internal SQL host that cannot directly reach the external Mythic server but can make outbound connections to Discord.
- A Discord server and bot serve as a bidirectional broker for agent messages, operator commands, and callbacks.
- The demonstration installs Mythic’s Discord C2 profile and Athena agent, then configures the bot token and channel ID.
- The presenter builds a self-contained Windows payload with Discord communications and sets a five-second callback interval with 10% jitter.
- The payload is transferred through the segmented lab network and run on the restricted SQL host.
- The first callback fails because the bot was not added to the server; after the bot is authorized, callbacks arrive and a `whoami` command works.
- The presenter says the technique depends on the internal host being able to reach the third-party service and discusses other services and redirectors as possible relays.
Article Details
- Topics
- [00:00] Discord introduced as a broker for C2 traffic blocked by a firewall
- [01:03] Lab network layout and outbound firewall restrictions
- [04:25] Internal and external redirector options
- [07:53] Discord demonstrated as a bidirectional C2 channel
- [09:26] Installing the Mythic Discord profile and Athena agent
- [16:01] Building a Windows payload with Discord C2 settings
- [23:43] Running the agent and verifying Discord-relayed callbacks
- [26:59] Other third-party services discussed as potential C2 channels
