Microsoft BITS Proxy Requests to Uncommon Server IP Hosts

Identifies Microsoft BITS proxy connections where the destination host ends with a single-digit, indicating uncommon IP-style addressing.

FreeReviewedSigma · High · v2
Category
proxy
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-06-10
Updated
2026-07-31

ATT&CK techniques

Execution → C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. Exfiltration

  12. Impact

What it detects

This rule flags proxy traffic where the user agent indicates Microsoft BITS and the destination host ends with a single-digit value (1–9) rather than an FQDN. Using an IP-based or atypical host format for BITS transfers can help attackers blend in or avoid straightforward domain-based detections. It relies on proxy telemetry fields for the HTTP user agent and the requested host value.

Related detections9 linkedT1071.001 — drag to rearrange
Microsoft BITS Proxy Activity to Uncommon Top-Level Domains
Malicious HarborWatch RAT Command and Control Beacon by User Agent (via proxy)
Suspicious Remote Script Transfer via Bitsadmin (via process_creation)
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
Suspicious File Download Via Bitsadmin Transfer
Microsoft BITS Proxy Requests to Uncommon Server IP Hosts
Pivot detection · T1071.001 · 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.