Ursnif dropper download URLs matching PHP l= parameter ending in CAB

Flags proxy responses where a request URI contains /.php?l= and ends with .cab, returning HTTP 200.

FreeReviewedSigma · High · v5
Category
proxy
Author
Thomas Patzke (SigmaHQ), DRL 1.1
Published
2019-12-19
Updated
2026-07-31

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

Identifies proxy web requests that return HTTP 200 where the requested URL contains '/'' and the PHP query parameter 'php?l=', and ends with a '.cab' file extension. This pattern is characteristic of malware delivery over HTTP, where attackers retrieve executable payloads disguised as files. The rule relies on proxy telemetry capturing the full request URI and the response status code.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious Encrypted Reverse Shell via Netcat and GPG on Linux
Malicious axios NPM Supply Chain C2 Domain Resolution
Suspicious Reverse Shell via Dev TCP or Netcat
Malicious HarborWatch RAT Command and Control Beacon by User Agent (via proxy)
Suspicious UAT-10608 Credential Harvesting C2 Beacon via HTTP
Malicious BadIIS C2 Communication via lwxatisme User-Agent
Possible PS1Bot C2 Beacon With Drive Serial URI Pattern (via proxy)
Suspicious WarmCookie C2 Beacon With Fixed Firefox User-Agent
Malicious Renamed Python Interpreter Executing nvidia.py RAT
Ursnif dropper download URLs matching PHP l= parameter ending in CAB
Pivot detection · T1071.001 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.