Morto

Overview

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.

Understanding Morto (RDP Worms)
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.

Execution and RDP Brute-Forcing Mechanics
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`).

Indicators of Compromise & Impact
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.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_MORTO {
    meta:
        description = "Detects Morto (advanced_threat)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "morto" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Morto Activity
id: 3703a207dd8f1fde219278b82a053970
status: experimental
description: Detects generic indicators of the morto malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*morto*"
    condition: selection
level: medium

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. 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.
2. Segment the internal network to prevent the worm from horizontally scanning and brute-forcing internal servers.
3. Identify all accounts (especially local 'Administrator' accounts) that use weak or default passwords and force an immediate, enterprise-wide password reset.
4. 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

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not allow local 'Administrator' accounts to remain active with the same password across multiple workstations (use LAPS instead).
2. 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.

References & External Analysis

• Search "morto" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: advanced_threat)

Explore other malware families in the same category:

• Pennybee
• Woozlist
• Iobit
• Nottotrack
• Patchupplus

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/morto.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.