Censys Finds 131 Internet-Exposed Mythic C2 Hosts, Including a Cluster Developing Custom Implants

· Original article ↗

Summary

Censys identified 131 internet-exposed Mythic hosts and analyzed their fingerprints and infrastructure. One cluster showed evidence of custom implant development and Discord-based C2; the article also outlines detection opportunities for defenders.

Key points

  • As of September 11, 2026, Censys tracked 131 hosts exposing Mythic; 115 had default Mythic certificate subject organizations.
  • Common fingerprints include a self-signed certificate identifying Mythic, the default internal certificate chain, and an HTTP 502 response on port 7443.
  • Ten hosts also exposed another C2 framework, including Sliver or Adaptix C2; one multi-framework cluster appeared consistent with a lab or training fleet.
  • A separate cluster used telemetry-update[.]services and exposed staged payload builds, Rust source for another implant family, and scripts indicating Discord-based C2 development.
  • Censys recommends monitoring for Mythic certificate details, port 7443 connections, default internal certificate names, and unexpected Mythic Docker containers or agent behaviors.

Article Details

Attack Vectors
  • Mythic supports remote command execution and shell access through its agents.
  • Mythic agents can use HTTP/HTTPS, WebSocket, TCP, SMB named pipes, and DNS transport profiles.
  • The reported cluster used a Discord-based C2 transport with steganographic staging.
  • The reported staging server exposed Windows PE builds of the nyx payload family, Rust source and archive files for fys2, and a /serve/ directory containing build outputs staged for victim download.
  • Mythic supports SMB pipe-based agent pivoting and SOCKS proxy chaining.
Defensive Notes
  • Alert on TLS connections to servers whose certificate subject organization is O=Mythic or O=Mythic C2.
  • Flag outbound connections to port 7443 on dedicated VPS or cloud IPs without a known legitimate service, particularly when the TLS certificate is self-signed.
  • Monitor servers your organization communicates with for the default internal PKI names CN=operators and CN=multiplayer.
  • Alert on unexpected Docker Compose deployments containing mythic_nginx, mythic_rabbitmq, or mythic_server container names.
  • Look for unexpected scheduled tasks, launch agents, or systemd units that point to binaries in temporary or user directories.
  • On Windows targets, monitor process injection and LSASS access from non-system processes.
  • Cross-reference Censys results for Mythic hosts with egress telemetry to identify internal hosts communicating with suspected Mythic infrastructure.

Indicators of compromise

TypeIndicatorContext
DOMAINtelemetry-update[.]servicesCustom domain used by the reported Mythic-only cluster; the article says it was built to blend with Windows telemetry traffic.
IPV4142[.]93[.]52[.]11Host in the reported Mythic-only cluster associated with the domain telemetry-update[.]services.
IPV4170[.]64[.]183[.]242Host in the reported Mythic-only cluster associated with the domain telemetry-update[.]services.
IPV4194[.]26[.]192[.]117Host in the reported Mythic-only cluster associated with the domain telemetry-update[.]services.
IPV465[.]87[.]7[.]11Publicly accessible staging server hosting payload builds and files staged for victim download.

MITRE ATT&CK

Malware

Tools

Countries

Related Articles