Skip to content
← Back to briefing

Threat intelSource date: 2026-10-22

MythicRatatoskr: command and control hidden in a mesh network

New research on a 2025 incident: what to examine when the real communication destination is not a conventional C2 domain.

Topic

Threat intelligence · Endpoint · IPv6 overlay · Egress

Original source

ESET Research ↗

In focus

Research published in October · Incident from 2025

What was reported

On October 22, ESET published an analysis of a backdoor using Yggdrasil for command-and-control communication. The investigated case concerns a company in Ukraine and activity from 2025.

Applicability and impact

The research informs application control and outbound visibility. Yggdrasil has legitimate uses; its presence alone does not establish an attack, and the report does not demonstrate a widespread campaign.

What to check and remediate

  1. Check: inventory approved remote-access, proxy and mesh utilities. Correlate installed processes and services with outbound flows and the application owner.
  2. Triage: for an unexpected installation, preserve the process tree, connections and logs before removal. Assess endpoint and network evidence together.
  3. Contain: isolate confirmed affected systems under the incident procedure. For legitimate applications, explicitly define required destinations and services before imposing restrictions.
  4. Prevent: review application allowlisting, local privileges and egress policy. A domain blocklist alone does not cover applications using overlays or proxies.
  5. Validate: simulate a benign unapproved connection in a test environment and confirm the expected alert or block. Separately verify that authorized applications still work.
What to keep in mind

The useful criterion is process → connection → control-decision correlation. Encrypted traffic or a historical indicator alone does not establish compromise.

How we can help

How weownit.net can help

We can review available logs, outbound policy and application dependencies, then define a synthetic verification scenario. Malware reverse engineering and extended threat hunting require a dedicated scope.

Proposed deliverables
  • Relevant application and outbound-flow inventory
  • Visibility gaps and justified proposed rules
  • Benign detection scenario and outcome evidence
Discuss assessment and remediation ↗

Availability and scope are agreed before work starts. This form is not an emergency channel.

Sources and boundaries

ESET Research ↗

Editorial synthesis of the cited research. Applicability, checks and proposed deliverables are weownit.net recommendations, separate from the source findings. No assessment of your systems has been performed.