Yuri

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Interactive Shell Access: The RAT provides the attacker with a hidden, interactive command-line interface (reverse shell). The attacker can execute arbitrary system commands, manipulate the registry, and manage running processes as if they were sitting at the keyboard.
• Surveillance and Espionage: Yuri typically includes modules for live audio/video capture (hijacking the webcam and microphone), capturing desktop screenshots, and a built-in keylogger to steal passwords and monitor user activity in real-time.
• Lateral Movement Platform: A compromised machine running a RAT acts as a perfect beachhead for lateral movement. The attacker can utilize Yuri's file management capabilities to upload port scanners, credential dumping tools (like Mimikatz), and additional exploits to attack other servers within the corporate network.

Threat Assessment

Incident Response and Remediation

• Immediate Network Isolation: Severing the C2 connection is the absolute highest priority. Disconnect the infected machine from the network immediately to cut off the attacker's interactive access.
• Hunt for Lateral Movement: Assume the attacker has already used the RAT to pivot. Incident responders must analyze network traffic logs (NetFlow, firewall logs) originating from the infected IP address to identify other potentially compromised internal hosts.
• Bare-Metal Re-imaging: Due to the extensive, interactive control a RAT provides, it is impossible to guarantee that a system has been "cleaned" manually. The attacker likely installed secondary backdoors. The only secure remediation is a complete bare-metal wipe and re-image from a trusted backup.

Known aliases

Threat reports may refer to this family under multiple names:

• Backdoor.Yuri
• RAT.Yuri
• Win32/Yuri

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
• T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
• T1125: Restrict access to local camera or microphone APIs. Utilize endpoint protection that monitors hardware access.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

rule MALWARE_WIN_YURI_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Yuri"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "yuri" ascii wide nocase
        $s2 = "backdoor.yuri" ascii wide nocase
        $s3 = "rat.yuri" ascii wide nocase
        $s4 = "win32/yuri" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Yuri (Trojan) Execution & Triage
id: 59518bf9-557a-506b-b3ce-a4c25ba87e80
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Yuri malware family. Detects suspicious execution from temporary user directories
  with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/yuri
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059
- attack.t1105
- attack.t1056_001
- attack.t1125
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

rule MALWARE_WIN_YURI_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Yuri tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "yuri" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}

Containment & Response Steps

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

1. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Yuri from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Yuri into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Yuri persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Yuri execution timeframe.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Yuri dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Yuri until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• Search "yuri" on VirusTotal (External Analysis)
• Search "yuri" on Any.Run (Sandbox Sandbox)
• Search "yuri" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Extenbro
• Mepaow
• Harvester
• Disfa
• Lsslogger
• Dapato
• Vesenlosow
• Autohit

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/yuri.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.