Skip to content
Mythic C2 Detected – 154.198.49.31154[.]198[.]49[.]31:7443

Mythic C2 Detected – 154.198.49.31154[.]198[.]49[.]31:7443

Redpacketsecurity •admin • September 13, 2026

The host exposes a Mythic web interface on HTTPS port 7443. The portal redirects to /new/login and presents a self-signed-style certificate issued to Mythic.

Why this matters and what to do now

What : A Mythic management portal is publicly reachable from the internet on port 7443.

Why : Unauthorised access could expose operator functions, payload management, tasking, and victim-related data if authentication or the host is compromised.

Do now : Validate whether 154[.]198[.]49[.]31 is authorised and identify the system owner.

Do now : Restrict port 7443 to approved administration networks through firewall or VPN controls.

Do now : Review Mythic, nginx, operating system, and authentication logs for suspicious access.

Do now : Rotate credentials and review administrator accounts, tokens, and API access.

Do now : Preserve the host and container evidence, then assess for payloads, implants, and unauthorised changes.

The exposed service is strongly consistent with a Mythic command-and-control management portal. The product title, React application paths, /new/login route, Mythic favicon, and certificate organisation provide mutually supporting evidence. The login gate indicates an administrative interface rather than an unauthenticated payload service. The data does not prove that the host is currently operating an active campaign or that it is controlled by a specific threat actor. It may be a legitimate test, research, or privately operated Mythic deployment. The public exposure of the management interface is nevertheless a material risk, particularly if authentication, access controls, or underlying host security are weak.

proxy, firewall, and DNS logs for outbound or inbound connections to 154[.]198[.]49[.]31:7443.

Alert on access to /new/login and related /new/static/ paths from untrusted networks.

Cluster TLS telemetry using the observed JARM, JA3S, and certificate SHA-256 values.

Hunt for administrative sessions, API activity, and unusual tasking involving the exposed Mythic host.

Remove direct internet exposure and allow administration only through a VPN or dedicated management network.

Apply current Mythic, container, nginx, operating system, and dependency security updates.

Enforce strong unique credentials and multi-factor authentication where supported.

Restrict administrative roles and review all Mythic users, agents, payloads, and tasking history.

Terminate unauthorised sessions and rotate credentials, tokens, and certificates if compromise is suspected.

Use network monitoring and egress controls to identify possible Mythic agent communications.

High, The Mythic title, product identification, application paths, favicon, and Mythic TLS certificate provide consistent service-level evidence.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

Extracted Entities

IP Addresses (1)