{
  "family": "morto",
  "sample_count": 4,
  "category": "advanced_threat",
  "description": "Worm:Win32/Morto is a classic, highly aggressive network worm specifically designed to propagate across the internet and internal enterprise networks by attacking Remote Desktop Protocol (RDP) services. Unlike malware that relies on user interaction (phishing) or software vulnerabilities, Morto spreads entirely by brute-forcing weak or default administrator credentials on internet-exposed Windows machines.<br><br><b>Understanding Morto (RDP Worms)</b><br>To an end-user, a Morto infection might cause severe system slowdowns and a massive spike in outbound network traffic as the machine scans for new victims. For a network administrator, Morto is a loud, chaotic event that quickly saturates network bandwidth and triggers thousands of failed login alerts on domain controllers. Its primary purpose was often to install secondary payloads (like DDoS bots or adware) or simply to demonstrate the massive vulnerability of internet-facing RDP.<br><br><b>Execution and RDP Brute-Forcing Mechanics</b><br>Morto does not use software exploits. It constantly scans the local subnet and random internet IP blocks on port 3389 (RDP) (`T1046`). When it finds an active RDP service, it initiates a dictionary attack, attempting to log in using common usernames (like 'Administrator', 'admin') and a hardcoded list of weak passwords (`T1110.001`). Once it successfully authenticates, it uses the WTS (Windows Terminal Services) APIs or standard drive mapping (e.g., `\\C$`) (`T1021.002`) to copy its executable (often named `a.exe` or disguised as a Windows system file) to the remote machine and executes it (`T1570`). Upon execution, it establishes persistence by dropping a `.dll` file into the `System32` directory and registering it as a service or modifying the `Userinit` registry key (`T1543.003`).<br><br><b>Indicators of Compromise & Impact</b><br>The impact is rapid, widespread compromise of Windows servers and workstations, leading to severe network congestion. Host-based IoCs include EDR alerts for thousands of failed RDP logon events (Event ID 4625), followed by a successful logon (Event ID 4624) from an unknown IP, immediately followed by the creation of a new, anomalous Windows Service. Network IoCs are characterized by massive spikes in outbound scanning activity on port 3389.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Morto and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Morto is classified as a Advanced Threat. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments."
      }
    },
    {
      "@type": "Question",
      "name": "How does Morto establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Morto typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks."
      }
    },
    {
      "@type": "Question",
      "name": "What are the essential incident response steps for mitigating a Morto compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Morto should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups."
      }
    },
    {
      "@type": "Question",
      "name": "What lateral movement and credential access tactics does Morto leverage in enterprise intrusions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Morto frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers."
      }
    },
    {
      "@type": "Question",
      "name": "How does Morto maintain covert communications and evade perimeter network monitoring?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Morto often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1021.001",
    "T1543.003",
    "T1110.001",
    "T1046"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1110.001",
      "name": "Brute Force: Password Guessing (RDP Dictionary Attacks)",
      "tactic": "Credential Access"
    },
    {
      "id": "T1021.001",
      "name": "Remote Services: Remote Desktop Protocol",
      "tactic": "Lateral Movement"
    },
    {
      "id": "T1046",
      "name": "Network Service Discovery (Scanning for port 3389)",
      "tactic": "Discovery"
    },
    {
      "id": "T1543.003",
      "name": "Create or Modify System Process: Windows Service",
      "tactic": "Persistence"
    }
  ],
  "containment_steps": [
    "Immediately block all inbound port 3389 (RDP) traffic at the perimeter firewall; RDP should never be exposed directly to the internet without a VPN or Gateway.",
    "Segment the internal network to prevent the worm from horizontally scanning and brute-forcing internal servers.",
    "Identify all accounts (especially local 'Administrator' accounts) that use weak or default passwords and force an immediate, enterprise-wide password reset.",
    "Analyze Windows Security Event Logs for Event ID 4624 (Logon Type 10) to identify the specific machines that were compromised via RDP."
  ],
  "what_to_avoid": [
    "Do not allow local 'Administrator' accounts to remain active with the same password across multiple workstations (use LAPS instead).",
    "Avoid relying solely on changing the default RDP port (e.g., from 3389 to 3390); worms like Morto and modern port scanners will easily find the open service regardless of the port number."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "execution",
    "persistence"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}