{
  "family": "phpw",
  "sample_count": 195,
  "category": "trojan_generic",
  "description": "Backdoor:Win32/Phpw is a unique classification of malware that bridges the gap between web-based threats (PHP webshells) and traditional Windows executable backdoors.<br><br><b>What is Phpw?</b><br>To a web administrator, a Phpw infection usually indicates a compromised web server hosting malicious PHP scripts. However, in the context of Windows endpoints, Phpw often refers to standalone Windows executables that bundle a lightweight web server and PHP interpreter. For threat hunters, this indicates the malware has essentially turned the victim's endpoint into a covert web server, allowing the attacker to interact with the machine via standard HTTP requests and execute PHP code locally.<br><br><b>Infection Vectors & Threat Hunting</b><br>Phpw variants are often dropped as secondary payloads following a successful RDP brute-force attack, or deployed by lateral movement tools within a compromised network. Once executed, the malware silently binds to a specific TCP port (often non-standard, like 8080, 4444, or high ephemeral ports) and listens for incoming connections. The attacker can then browse to the endpoint's IP address and access a fully functional web shell (like C99 or b374k) running directly on the Windows host. <br><br><b>Forensic Analysis & Impact</b><br>The impact of a Phpw backdoor is profound; it provides the attacker with a GUI-driven interface to browse the local file system, upload/download files, dump databases, and execute arbitrary command-line instructions. Incident responders should hunt for unexpected processes (like <code>php.exe</code> or lightweight web servers like <code>mongoose.exe</code>) running from user directories, and monitor firewall logs for anomalous inbound connections to non-standard ports on internal workstations.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1571",
    "T1505.003",
    "T1105",
    "T1190",
    "T1059.003"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1505.003",
      "name": "Server Software Component: Web Shell",
      "tactic": "Persistence"
    },
    {
      "id": "T1571",
      "name": "Non-Standard Port",
      "tactic": "Command and Control"
    },
    {
      "id": "T1059.003",
      "name": "Command and Scripting Interpreter: Windows Command Shell",
      "tactic": "Execution"
    },
    {
      "id": "T1105",
      "name": "Ingress Tool Transfer",
      "tactic": "Command and Control"
    },
    {
      "id": "T1190",
      "name": "Exploit Public-Facing Application",
      "tactic": "Initial Access"
    }
  ],
  "containment_steps": [
    "Isolate the endpoint by disconnecting it from the network to sever the attacker's inbound web shell access.",
    "Identify the specific port the Phpw backdoor is listening on and block it at the local and perimeter firewalls.",
    "Audit the file system for dropped web shells (typically `.php` files) hidden in obscure directories alongside the bundled interpreter.",
    "Investigate the initial infection vector; Phpw is often deployed manually by an attacker who has already compromised an administrator account."
  ],
  "what_to_avoid": [
    "Do not assume the perimeter firewall is blocking access; attackers often use reverse tunneling (like Ngrok) to expose the local Phpw web server to the internet.",
    "Avoid relying solely on file deletion; ensure the rogue web server processes are fully terminated in memory."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}