Windows Webshell Command Strings in Webserver GET Requests

Identifies GET requests with URL-encoded Windows command strings consistent with webshell behavior.

FreeReviewedSigma · High · v2
Category
webserver
Author
Florian Roth (Nextron Systems), Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-02-19
Updated
2026-07-31

ATT&CK techniques

Persistence
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  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 flags webserver HTTP GET requests whose query strings contain URL-encoded command fragments commonly seen in Windows webshells. Attackers use these command strings to execute reconnaissance and system administration actions via an injected or hosted webshell. Detection relies on webserver request logs capturing the HTTP method (GET) and the full request content needed to match the specified keyword patterns in the URL.

Related detections9 linkedT1505.003 — drag to rearrange
Possible Ivanti Connect Secure Webshell Access
Malicious Shell Spawned by SharePoint Worker Process w3wp
Suspicious SD-WAN Compromise JSP Webshell Access
Malicious AquaShell Webshell Access on Cisco Secure Email Gateway by UAT-9686
Malicious IIS Worker Process Spawning Command Shell Reconnaissance
Malicious StyleSmuggler (CVE-2026-75650) Web Shell Dropped In Magento Product Image Cache (via file_event)
Suspicious Web Shell File Written to IIS wwwroot Directory
Possible Citrix ShareFile Unauthenticated Upload Path Traversal Webshell (CVE-2023-24489) (via webserver)
Possible Unauthenticated Admin Creation in Dynamicweb CVE-2022-25369
Windows Webshell Command Strings in Webserver GET Requests
Pivot detection · T1505.003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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