Yunsip

Category: infostealer · Aliases: PWS:Win32/Yunsip, Trojan:Win32/Yunsip, PWS:Win32/Yunsip.A, Trojan.Yunsip, Win32/Yunsip · Sample count (EMBER 2018): 280 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: InfostealerStatus: Automated SignatureFirst seen: 2013Motivation: Financial Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Yunsip (tracked across security vendor definitions as PWS:Win32/Yunsip, Trojan:Win32/Yunsip, and PWS:Win32/Yunsip.A) is an aggressive credential-stealing trojan and secondary loader targeting Windows endpoints since 2013.

Table of Contents

Overview

Yunsip (tracked across security vendor definitions as PWS:Win32/Yunsip, Trojan:Win32/Yunsip, and PWS:Win32/Yunsip.A) is an aggressive credential-stealing trojan and secondary loader targeting Windows endpoints since 2013. Designed to harvest authentication material from infected workstations, Yunsip systematically scans web browser data stores (including Google Chrome, Mozilla Firefox, and Internet Explorer/Edge), email clients, and FTP configuration files to locate saved passwords, session cookies, and user autofill databases. In addition to credential extraction, Yunsip establishes persistent communication with remote command-and-control servers over HTTP/HTTPS, enabling attackers to deploy secondary malware payloads such as keyloggers, remote access backdoors, or cryptominers. The malware achieves persistence by creating autostart registry entries under HKCU\Software\Microsoft\Windows\CurrentVersion\Run and registering scheduled tasks disguised as legitimate Windows update services.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Win32 Credential Stealer Family

Known Derivatives & Downstream Variants: Yunsip.A · Yunsip.B · Yunsip.Gen

MITRE ATT&CK Techniques

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

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

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

MITRE D3FEND™ Defensive Countermeasures

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

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
D3-CVHCredential Vault HardeningHardenT1555.003Enable DPAPI master key audit logging and isolate browser SQLite database files within virtualization-based security containers.

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

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

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Yunsip (Infostealer) Execution & Triage
id: b3c959ad-f644-5249-b248-fbbc07eacd34
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Yunsip malware family. Detects browser credential database harvesting,
  master key queries, and DPAPI extraction routines typical of modern infostealers.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/yunsip
- https://malware-families-catalog.systemhelpdesk.com/defensive/infostealer-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.infostealer
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1555_003
- attack.t1056_001
- attack.t1547_001
- attack.t1071_001
- attack.t1027
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \rundll32.exe
    CommandLine|contains:
    - \Google\Chrome\User Data\Default\Login Data
    - \AppData\Roaming\Mozilla\Firefox\Profiles
    - \AppData\Local\Microsoft\Edge\User Data
    - vaultcmd.exe /list
    - dpapi
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_YUNSIP_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Yunsip 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 = "yunsip" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

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

  1. Disconnect the affected host from corporate networks immediately to halt credential exfiltration.
  2. Identify and kill active Yunsip processes running from %APPDATA% or %TEMP% directories.
  3. Remove persistence entries under HKCU\Software\Microsoft\Windows\CurrentVersion\Run\Yunsip.
  4. Enforce immediate enterprise-wide password rotations for all user and administrative accounts used on the machine.

What to Avoid

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

  1. Do not allow users to store unencrypted corporate or banking passwords in web browsers.
  2. Avoid opening unverified email attachments purporting to be invoices or delivery documents.

References & External Analysis

Frequently Asked Questions

What is the Yunsip malware family?

Yunsip is a password-stealing trojan and secondary payload loader that extracts stored credentials from browsers, email clients, and FTP tools.

What data does Yunsip target on compromised systems?

Yunsip targets saved login passwords, browser cookies, autofill records, FTP access profiles, and system configuration data.

How does Yunsip communicate with attacker infrastructure?

It exfiltrates stolen credentials and receives secondary tasking over encrypted HTTP/HTTPS POST requests to remote C2 servers.

How does Yunsip achieve persistence on Windows?

It writes executable startup paths to Windows registry Run keys and configures recurring scheduled tasks masquerading as system updates.

What remediation steps should be taken if Yunsip is detected?

Isolate the endpoint from the network, terminate active trojan processes, delete registry startup keys, and immediately rotate all saved account passwords.

How do I remove the Yunsip Infostealer from Windows?

Manual removal of Yunsip is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Yunsip a virus or a Infostealer?

Yunsip is classified as a Infostealer. Unlike traditional viruses that infect files, modern malware like Yunsip typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Yunsip infection?

Symptoms of Yunsip can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Infostealers

Want to prevent Yunsip and similar threats from compromising your organization? Read our comprehensive defensive guide: InfoStealer Protection & Remediation.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

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