Webserver User-Agent Identifies Known Recon and Scanning Tool Strings

Alerts on web requests with User-Agent values containing known recon/scanner tool identifiers.

FreeReviewedSigma · Medium · v2
Category
webserver
Author
Nasreddine Bencherchali (Nextron Systems), Tim Shelton (SigmaHQ), DRL 1.1
Published
2022-07-19
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  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 flags webserver requests whose User-Agent contains strings commonly associated with reconnaissance and scanning tools. Attackers often use automated scanners to enumerate services, discover vulnerabilities, or identify targets before exploitation. It relies on webserver telemetry that records HTTP request headers, specifically the User-Agent field, and matches against a set of predefined substrings.

Reporting behind it

Related detections9 linkedT1190 — drag to rearrange
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious IIS Worker Process Spawning Command Shell Reconnaissance
Potential StyleSmuggler (CVE-2026-75650) Exploitation Attempt - Magento GraphQL Styles Parameter (via webserver)
Cisco IOS XE Configuration Change by Web UI WSMA User
Possible React2Shell CVE-2025-55182 Prototype Pollution Exploitation
Possible Next.js Middleware Auth Bypass via X-Middleware-Subrequest Header (CVE-2025-29927)
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Ivanti Pulse Connect Secure Auth Bypass via TOTP Backup Code Path Traversal (via webserver)
Possible Citrix Bleed Session Token Leak via OpenID Configuration Endpoint (CVE-2023-4966) (via webserver)
Webserver User-Agent Identifies Known Recon and Scanning Tool Strings
Pivot detection · T1190 · 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.