Suspicious Command Execution via Web Server on Linux

hello@craftedsignal.io — Mon, 01 Jun 2026 16:46:26 +0000

This detection identifies suspicious command executions originating from web server processes on Linux systems. Attackers may exploit vulnerabilities in web applications to execute commands, potentially leading to the deployment of backdoors for persistent access. The rule focuses on detecting shell commands executed by web server processes (e.g., nginx, Apache) that exhibit characteristics commonly associated with exploitation attempts, such as discovery commands, credential access, payload decoding, or reverse shell setup. This activity is anomalous because web servers typically do not need to spawn shell commands, thus warranting further investigation.

Attack Chain

An attacker identifies a vulnerability in a web application running on a Linux server.
The attacker crafts a malicious HTTP request to exploit the vulnerability, injecting a command into a vulnerable parameter or input field.
The web server process (e.g., nginx, Apache) executes the injected command via a shell interpreter (e.g., bash, sh).
The executed command performs reconnaissance activities, such as reading system files (/etc/passwd, /etc/shadow) or enumerating network configurations (/etc/hosts, /etc/resolv.conf).
The attacker leverages encoding techniques (e.g., base64) to obfuscate malicious payloads or commands within the exploited application.
The attacker establishes a reverse shell connection to an external attacker-controlled server using tools like netcat or socat.
The attacker modifies system files, such as cron jobs or SSH authorized keys, to establish persistence on the compromised system.
The attacker deploys a web shell or backdoor file in the web server’s document root, enabling future code execution.

Impact

A successful attack could lead to unauthorized access to sensitive data, system compromise, and persistent control of the web server. This may result in data breaches, service disruption, and further lateral movement within the compromised network. The severity depends on the exploited vulnerability and the attacker’s objectives.

Recommendation

Deploy the Sigma rule “Detect Suspicious Command Execution via Web Server” to your SIEM and tune for your environment.
Enable Elastic Defend integration to monitor process executions.
Review and harden web application configurations to prevent command injection vulnerabilities.
Implement strong input validation and output encoding mechanisms in web applications.
Regularly scan web applications for vulnerabilities and apply necessary patches.

Suspicious Command Execution via Web Server on Linux

hello@craftedsignal.io — Mon, 01 Jun 2026 15:45:01 +0000

This detection rule identifies suspicious command executions initiated by web servers on Linux systems. Attackers may exploit web application vulnerabilities to execute arbitrary commands, gaining remote shell access and establishing persistence. The rule focuses on detecting shell commands with suspicious patterns, often indicative of vulnerability exploitation or malicious activity, such as reverse shells, file access to sensitive configuration files, and attempts to download or execute malicious payloads. The rule relies on process execution data collected by Elastic Defend. While network monitoring tools can exhibit similar behaviors, defenders should investigate any matched events to determine maliciousness.

Attack Chain

The attacker identifies a vulnerable web application running on a Linux server.
The attacker exploits a vulnerability (e.g., command injection, file upload) in the web application.
The web server (e.g., Apache, Nginx) executes a shell command (e.g., bash, sh) to facilitate the exploit.
The shell command includes suspicious patterns, such as reverse shell attempts (e.g., /dev/tcp, nc), file access to sensitive system files (e.g., /etc/passwd, /etc/shadow), or attempts to download remote payloads (e.g., curl, wget).
The attacker gains initial access to the system through the executed command or reverse shell.
The attacker attempts to establish persistence by modifying cron jobs or SSH configurations.
The attacker performs further reconnaissance and lateral movement within the compromised network.

Impact

Successful exploitation can lead to unauthorized access to sensitive data, modification of system configurations, installation of malware, and further compromise of the network. This can result in data breaches, system downtime, and reputational damage. Given the wide variety of web server platforms and web application technologies, the potential victim pool is vast.

Recommendation

Deploy the provided Sigma rules to your SIEM and tune for your environment, focusing on reducing false positives by allowlisting legitimate processes and commands.
Ensure that Elastic Defend is properly configured on all Linux endpoints to collect process execution data as required by the provided Sigma rules.
Investigate any alerts triggered by the Sigma rules, focusing on the command line arguments and the parent process to determine the legitimacy of the activity.
Review and harden web application configurations to prevent command injection and file upload vulnerabilities.
Implement strong input validation and output encoding mechanisms to mitigate web application vulnerabilities.

Mongrel_rails — CraftedSignal Threat Feed

Suspicious Command Execution via Web Server on Linux

Attack Chain

Impact

Recommendation

Suspicious Command Execution via Web Server on Linux

Attack Chain

Impact

Recommendation