{
  "family": "shell",
  "sample_count": 1,
  "category": "backdoor",
  "description": "<h3>Executive Summary</h3>\n\"Shell\" is a broad, generic classification used by security engines to identify a malicious script or executable designed to provide an attacker with interactive, command-line access to a compromised system. This category primarily encompasses Web Shells (e.g., PHP, ASPX) deployed on compromised web servers, and Reverse/Bind Shells deployed on traditional endpoints. The detection of a \"Shell\" indicates a severe, post-exploitation scenario where the attacker has achieved active remote control.\n\n<h3>Infection Vector and Technical Capabilities</h3>\nShells are almost exclusively deployed *after* an initial vulnerability has been exploited. On web servers, this is often a File Upload vulnerability or a Remote Code Execution (RCE) flaw. On endpoints, shells are dropped by exploit kits, malicious macros, or lateral movement tools like PsExec.\n\nOnce deployed, a Shell grants the attacker extensive capabilities:\n<ul>\n<li><strong>Interactive Command Execution:</strong> The core function is to allow the attacker to execute arbitrary operating system commands (`cmd.exe` or `/bin/sh`) as the user account running the shell (e.g., the web service account like `www-data` or `IIS_IUSRS`).</li>\n<li><strong>File System Manipulation:</strong> Attackers utilize the shell to traverse directories, download data (exfiltration), upload additional malware (like privilege escalation exploits), and alter configuration files.</li>\n<li><strong>Persistence and Pivoting:</strong> A shell serves as the primary beachhead. The attacker will immediately attempt to escalate privileges to `SYSTEM` or `root`, install a more permanent backdoor, and utilize the compromised machine to scan and attack other systems on the internal network.</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nThe detection of a Shell is a critical incident. It is not an automated infection; it means a human attacker (or a sophisticated automated framework) has active, interactive control over the system and is actively executing commands.\n\n<h3>Incident Response and Remediation</h3>\n<ul>\n<li><strong>Immediate Isolation:</strong> The compromised server or endpoint must be immediately isolated from the network to sever the attacker's interactive connection.</li>\n<li><strong>Forensic Analysis of Command History:</strong> If dealing with a web shell, analyze the web server access logs to determine *how* the shell was uploaded and what commands the attacker executed via HTTP requests.</li>\n<li><strong>Vulnerability Patching and Rebuild:</strong> Simply deleting the shell script is insufficient, as the vulnerability that allowed its upload still exists. The underlying vulnerability must be patched, and in most cases, the system should be rebuilt from a known-good backup to ensure no hidden persistence mechanisms remain.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "HackTool.Shell",
    "WebShell.Generic",
    "Backdoor.Shell",
    "Trojan.ReverseShell"
  ],
  "enrichment_level": "insufficient_information",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1505.003",
    "T1059",
    "T1105"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-07-02T07:30:48Z",
  "type": "HackTool / Web Shell / Backdoor",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}