Suspicious php.exe Backdoor Execution from AppData Roaming

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-05-15
Updated
2026-08-28

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects the PHP interpreter running from a user AppData Roaming directory while loading extensions and a config file, which matches the Interlock PHP backdoor. The group deployed php.exe with an extension directory and config.cfg to run a resident backdoor from Roaming rather than a normal install path. A scripting interpreter running from a per-user profile path is a strong indicator of malicious code execution and persistence.

Related detections9 linkedT1059.006 — drag to rearrange
Malicious AI CLI Anti-Attribution and Permission Bypass Flags
Suspicious Python HTTP Server Staging for Payload Delivery
Suspicious Python Base64 Encoded Command Execution (via process_creation)
Suspicious __init__.py Drop in Public Directory by Slow Pisces (via file_event)
Malicious Python Reverse Shell One-Liner Execution (via process_creation)
Suspicious Silver Fox Backdoor Execution via pythonw appclient Module (via process_creation)
Suspicious Malicious MCP Package devtools-assistant Execution (via process_creation)
Malicious GitVenom Python Fernet Decrypt-and-Execute Loader via process_creation
Suspicious Python Executing Script from var root Library Caches on macOS (via process_creation)
Suspicious php.exe Backdoor Execution from AppData Roaming
Pivot detection · T1059.006 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.