Shellme

Overview

Executive Summary

Technical Capabilities and Abuse

• Reverse Shell Execution: The most common implementation forces the compromised machine to initiate an outbound network connection back to an attacker-controlled listening post. This technique is highly effective at bypassing inbound firewall rules and Network Address Translation (NAT).
• Interactive Command Interface: The attacker is presented with a standard OS shell (e.g., `cmd.exe` or `/bin/bash`). They can execute any command with the privileges of the user account under which the Shellme executable was launched.
• Lateral Movement Gateway: The interactive shell is used to upload privilege escalation exploits, dump credentials (using Mimikatz), and launch further attacks against internal network resources that are otherwise isolated from the internet.

Threat Assessment

Incident Response and Remediation

• Immediate Isolation: The absolute highest priority is to sever the interactive connection. Isolate the infected machine from the network immediately.
• Forensic Triage: Do not reboot the machine, as the shell is likely running entirely in memory and the process details will be lost. Use memory forensics to identify the parent process of the shell to determine *how* the attacker initially compromised the system.
• Enterprise Credential Reset: If the shell was running under a privileged account (or if the attacker successfully escalated privileges), all domain and local credentials associated with that system must be considered compromised and reset immediately.

Known aliases

Threat reports may refer to this family under multiple names:

• HackTool.Shellme
• Backdoor.ReverseShell
• Win32/Shellme

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:

• T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.

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_SHELLME_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Shellme"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "shellme" ascii wide nocase
        $s2 = "hacktool.shellme" ascii wide nocase
        $s3 = "backdoor.reverseshell" ascii wide nocase
        $s4 = "win32/shellme" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Shellme (Ransomware) Execution & Triage
id: 4d7b84ae-48fb-535a-8a40-c18610f1f6aa
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Shellme malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/shellme
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059
- attack.t1059_003
- attack.t1090
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

rule MALWARE_WIN_SHELLME_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Shellme 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 = "shellme" 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 affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Shellme from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Shellme symmetric encryption keys or uncompiled payload components may still reside in memory.
3. Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Shellme to inhibit recovery.
4. Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Shellme binary and related persistence hooks are eradicated.

What to Avoid

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

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Shellme.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Shellme eradication is completely verified.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Nilage
• Gimemo
• Ludicrouz
• Xxybsq
• Mimilove
• Hancitor
• Stagol
• Genmaldow

Machine-readable

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