{
  "family": "shellme",
  "sample_count": 1,
  "category": "ransomware",
  "description": "<h3>Executive Summary</h3>\nShellme is a classification applied to a category of HackTools specifically designed to establish reverse shells or bind shells. While frequently utilized by authorized penetration testers and Red Teams, the detection of Shellme on a production system is a critical indicator that an attacker has achieved arbitrary command execution and established an interactive backdoor for complete, remote control of the endpoint.\n\n<h3>Technical Capabilities and Abuse</h3>\nShellme utilities are usually not distributed via spam. They are post-exploitation tools, uploaded and executed by an attacker *after* they have successfully exploited a vulnerability (like an unpatched web application flaw or a weak service password) to gain initial access.\n\nOnce executed, the tool provides direct command-line access:\n<ul>\n<li><strong>Reverse Shell Execution:</strong> 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).</li>\n<li><strong>Interactive Command Interface:</strong> 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.</li>\n<li><strong>Lateral Movement Gateway:</strong> 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.</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nThe presence of an active reverse shell (Shellme) is a \"glass break\" incident. It means an attacker has bypassed all preventative security controls and possesses interactive, real-time access to the environment. Data exfiltration, lateral movement, or ransomware deployment are imminent.\n\n<h3>Incident Response and Remediation</h3>\n<ul>\n<li><strong>Immediate Isolation:</strong> The absolute highest priority is to sever the interactive connection. Isolate the infected machine from the network immediately.</li>\n<li><strong>Forensic Triage:</strong> 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.</li>\n<li><strong>Enterprise Credential Reset:</strong> 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.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "HackTool.Shellme",
    "Backdoor.ReverseShell",
    "Win32/Shellme"
  ],
  "enrichment_level": "insufficient_information",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1059",
    "T1059.003",
    "T1090"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-07-01T17:44:33Z",
  "type": "HackTool / Reverse Shell Backdoor",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}