Chafer malware C2 URLs with /asp.asp?ui= pattern over HTTP proxy

Flags proxy HTTP requests containing the C2 URI pattern /asp.asp?ui= associated with Chafer behavior.

FreeReviewedSigma · High · v5
Category
proxy
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2019-01-31
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

This rule matches HTTP proxy requests whose URL path contains /asp.asp?ui=. Such a pattern is used to receive data from command-and-control infrastructure, making it a high-signal indicator for suspicious outbound communications. It relies on proxy telemetry that includes the full requested URI (c-uri) for each HTTP request.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious Cobalt Strike Default Named Pipe Activity
Malicious VoidLink Kernel Rootkit C2 Endpoints via HTTP (via proxy)
Malicious EtherRAT C2 Exfiltration Endpoints via HTTP (via proxy)
Possible PlugX and NPS Proxy Command and Control Domain Lookup
Possible Backdoor Mistic Command and Control Domain Lookup
Suspicious Weaver Ant In-Memory Web Shell Marker in Web Request (via webserver)
Malicious BlueNoroff C2 Communication via cur1-agent User-Agent (via proxy)
Possible GammaSteel C2 Using Spoofed iPhone User Agent
Suspicious PolarEdge Backdoor C2 URL with Module and putdata Command (via proxy)
Chafer malware C2 URLs with /asp.asp?ui= pattern over HTTP proxy
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.