Smheist

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Browser Exfiltration and Web Injection: Smheist targets Chromium and Gecko-based browsers to extract saved passwords and autofill data. Advanced variants may utilize "web injects"—injecting malicious HTML or JavaScript directly into the user's browser when they visit specific banking URLs to steal 2FA tokens or intercept transactions in real-time.
• Cryptocurrency Targeting: The malware actively searches the filesystem for desktop cryptocurrency wallets and attempts to steal the `wallet.dat` files and associated authentication tokens.
• Data Exfiltration: It collects extensive system details, captures keystrokes (keylogging) while the user is on targeted financial sites, and packages all stolen data into a compressed archive. This archive is then exfiltrated via encrypted HTTP POST requests to an attacker-controlled drop server.

Threat Assessment

Incident Response and Remediation

• Immediate Financial Lockout: The absolute highest priority is a complete password reset and the notification of financial institutions. ALL banking, corporate finance, and cryptocurrency credentials must be changed immediately from a *different, clean device*.
• MFA Token Revocation: Assume session cookies were stolen. Force an immediate sign-out of all active sessions for critical web applications to invalidate the stolen tokens.
• Endpoint Eradication: The extent of the data breach necessitates a full forensic review. Re-imaging the machine from a trusted baseline is required to ensure no secondary backdoors or persistent web injects remain on the system.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan.Smheist
• Banker.Smheist
• PWS.Heist

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.

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_SMHEIST_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Smheist"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "smheist" ascii wide nocase
        $s2 = "trojan.smheist" ascii wide nocase
        $s3 = "banker.smheist" ascii wide nocase
        $s4 = "pws.heist" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Smheist (Backdoor) Execution & Triage
id: b69252c6-d734-515f-b375-7d4c774898af
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Smheist malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/smheist
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1555_003
- attack.t1056_001
- attack.t1189
- attack.t1048
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_SMHEIST_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Smheist 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 = "smheist" 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. Immediately isolate the compromised host from internal LAN and WAN environments to cut off interactive remote shell sessions established by Smheist.
2. Inspect active socket listeners and outbound established network connections ('netstat -ano') to identify and sever covert TCP/UDP channels used by Smheist.
3. Scan Windows Services, Scheduled Tasks, and Startup folders to locate and eliminate persistent backdoor listeners configured by Smheist.
4. Invalidate all active VPN profiles, local administrator credentials, and session tokens that may have been harvested by the Smheist operator.
5. Re-image the affected host using a validated golden image prior to reconnecting it to enterprise network segments.

What to Avoid

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

1. Do not attempt to interact with or send messages through the Smheist remote terminal, as this alerts the attacker and may cause them to execute destructive anti-forensic commands.
2. Avoid relying solely on static file signatures, as Smheist payloads frequently execute reflectively in memory without writing binaries to disk.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Backdoor)

Explore other documented threats in the same operational category:

• Back_Orifice
• Mytob
• Flux
• Shadowhammer
• Darkhotel
• Orcusrot
• Hacdef
• Removewga

Machine-readable

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