This detection identifies adversaries deploying a PHP web shell named simple-backdoor.php to establish a persistent foothold and execute commands on compromised web servers. Proactive hunting for this indicator in Azure Sentinel is critical because web shells often serve as an initial entry point that can escalate privileges or pivot to other systems before triggering broader alerting mechanisms.
rule webshell_simple_backdoor {
meta:
description = "Web Shell - file simple-backdoor.php"
license = "Detection Rule License 1.1 https://github.com/Neo23x0/signature-base/blob/master/LICENSE"
author = "Florian Roth (Nextron Systems)"
date = "2014/01/28"
score = 70
hash = "f091d1b9274c881f8e41b2f96e6b9936"
id = "393e738a-b4c2-5630-a55f-c3caee4ff75e"
strings:
$s0 = "$cmd = ($_REQUEST['cmd']);" fullword
$s1 = "if(isset($_REQUEST['cmd'])){" fullword
$s4 = "system($cmd);" fullword
condition:
2 of them
}
This YARA rule can be deployed in the following contexts:
This rule contains 4 string patterns in its detection logic.
Here are 5 specific false positive scenarios for the Web Shell - file simple-backdoor.php detection rule, including suggested filters and exclusions:
Scenario: Automated CMS Security Patch Deployment
simple-backdoor.php as part of a standard hardening package for the WordPress or Drupal instances.source_host_ip IN [10.20.5.1, 10.20.5.2] AND event_time BETWEEN '02:00' AND '04:00'.Scenario: Development Environment Staging by DevOps Engineers
simple-backdoor.php represents a legitimate utility script used for temporary debugging of API endpoints, not a malicious backdoor.environment_tag = 'Staging' AND user_account IN ['svc-devops-01', 'j.doe'].Scenario: Scheduled Backup Verification Job