Msilperseus

Category: infostealer · Aliases: Trojan:MSIL/Perseus!rfn, Trojan.MSIL.Perseus, MSIL/Perseus, Trojan:MSIL/Perseus.A, Win32/Perseus.Stealer · Sample count (EMBER 2018): 596 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: InfostealerStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2017Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Financial Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
MSIL/Perseus (identified in endpoint telemetry as Trojan:MSIL/Perseus, Trojan.MSIL.Perseus, and MSIL/Perseus.A) is a modular .NET-based information stealer and Remote Access Trojan documented by Microsoft Defender, Trend Micro, and ESET.

Table of Contents

Overview

MSIL/Perseus (identified in endpoint telemetry as Trojan:MSIL/Perseus, Trojan.MSIL.Perseus, and MSIL/Perseus.A) is a modular .NET-based information stealer and Remote Access Trojan documented by Microsoft Defender, Trend Micro, and ESET. Written in Microsoft Intermediate Language (MSIL), Perseus targets sensitive user credentials, browser artifacts, and cryptocurrency wallet databases on infected Windows hosts. The malware executes through multi-stage obfuscation, frequently leveraging process hollowing techniques to inject unmanaged shellcode or .NET assemblies into trusted legitimate binaries such as RegSvcs.exe, MSBuild.exe, or svchost.exe. Once active in memory, Perseus extracts stored passwords, autofill data, and session cookies from Chromium- and Gecko-based browsers (including Google Chrome, Microsoft Edge, and Mozilla Firefox), enumerates local file systems for cryptocurrency wallet files, and transmits harvested intelligence via TLS-encrypted HTTP POST requests to remote C2 infrastructure.

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: Msil_Infostealer_Framework

Known Derivatives & Downstream Variants: Perseus.A · Perseus!Rfn · Msil/Perseus

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-EDAExecutable Deobfuscation AnalysisDetectT1027.002Deploy static entropy scanners and dynamic memory-unpacking heuristics to identify obfuscated and packed PE structures.
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-PMAPassword Manager Access ControlHardenT1555Enforce device compliance checks and multi-factor biometric authentication before unlocking stored credential vaults.

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_MSILPERSEUS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Msilperseus"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "msilperseus" ascii wide nocase
        $s2 = "trojan:msil/perseus!rfn" ascii wide nocase
        $s3 = "trojan.msil.perseus" ascii wide nocase
        $s4 = "msil/perseus" ascii wide nocase
        $s5 = "trojan:msil/perseus.a" ascii wide nocase
        $s6 = "win32/perseus.stealer" 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 - Msilperseus (Infostealer) Execution & Triage
id: e3bdb01f-76d2-5ab5-89cf-77b9ad7f9ada
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Msilperseus 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/msilperseus
- 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.t1059_001
- attack.t1055_012
- attack.t1547_001
- attack.t1056_001
- attack.t1555_003
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_MSILPERSEUS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Msilperseus 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 = "msilperseus" 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. Immediately isolate the endpoint from the network to sever the attacker's interactive, remote-control session.
  2. Capture a full RAM image of the endpoint; memory forensics is critical for extracting the un-obfuscated .NET Perseus configuration.
  3. Decompile the extracted .NET payload to identify the specific C2 IP address/domain and implement immediate blocks at the perimeter firewall.
  4. Assume total endpoint compromise; perform a clean OS rebuild and force password resets for all accounts that accessed 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 leave the machine connected to the network during triage; the attacker has live access and will likely destroy evidence or deploy ransomware.
  2. Avoid relying solely on static file analysis, as the heavy .NET obfuscation (ConfuserEx) will yield minimal intelligence without memory dumping.

References & External Analysis

Frequently Asked Questions

What is MSIL/Perseus malware?

MSIL/Perseus is a .NET-based information stealer and trojan documented by Microsoft Defender and Trend Micro that specializes in harvesting credentials, session tokens, and cryptocurrency wallets.

What techniques does MSIL/Perseus use to evade detection?

Perseus utilizes process hollowing (T1055.012) into legitimate .NET utilities such as RegSvcs.exe or MSBuild.exe alongside ConfuserEx or custom .NET obfuscation tools.

What data is targeted by the MSIL/Perseus stealer?

Perseus targets browser SQLite databases containing stored credentials, cookies, autofill histories, desktop cryptocurrency wallet dat files, and system configuration telemetry.

Which vulnerabilities are leveraged to deliver MSIL/Perseus?

Attackers deploy MSIL/Perseus via weaponized Office documents exploiting CVE-2017-0199 and CVE-2017-11882 to execute multi-stage .NET downloaders.

How can organizations detect MSIL/Perseus activity?

Security analysts can detect Perseus by monitoring anomalous child processes spawned from RegSvcs.exe or MSBuild.exe, auditing browser profile access, and blocking unauthorized outbound HTTP POST connections.

How do I remove the Msilperseus Infostealer from Windows?

Manual removal of Msilperseus 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 Msilperseus a virus or a Infostealer?

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

What are the main symptoms of a Msilperseus infection?

Symptoms of Msilperseus 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 Msilperseus 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/msilperseus.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.