Webserver: Successful IIS shortname fuzzing scan using "~1" parameter

Alerts on successful IIS probing requests containing ~1 and ending with a.aspx using GET/OPTIONS.

FreeReviewedSigma · Medium · v2
Category
webserver
Author
frack113 (SigmaHQ), DRL 1.1
Published
2021-10-06
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 identifies HTTP requests made to a web server that include a shortname-style path fragment ("~1") in the query string and target an ending of "a.aspx". It only matches responses with status codes 200 or 301, indicating the scan reached content and/or was redirected successfully. Attackers may use this behavior to enumerate accessible directories or files on IIS instances that are vulnerable due to legacy handling of shortname patterns. Telemetry relied on is HTTP request fields (URI query, method) and HTTP response status (sc-status).

Related detections9 linkedT1190 — drag to rearrange
Malicious MS-SQL Server Spawning Command Shell via Mallox
Malicious ActiveMQ CVE-2023-46604 Payload Download via curl or wget
Malicious WordPress Core SQL Injection Scanner via User-Agent
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Malicious Command Shell or PowerShell Spawned by Tomcat via Process Creation (via process_creation)
Suspicious Shell Script Execution From Temp Directory on SonicWall SMA1000 Appliance (via process_creation)
Possible TP-Link Command Injection via WlanNetworkRpm Endpoint (via webserver)
Malicious SharePoint ToolPane Exploitation via SignOut Referer
Suspicious Tomcat Session Deserialization Trigger via Crafted JSESSIONID
Webserver: Successful IIS shortname fuzzing scan using "~1" parameter
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.