Windows BITS Client Job Downloads From Uncommon Remote TLDs

Alerts on BITS transfers (EventID 16403) to remote domains with uncommon or suspicious TLD patterns.

FreeReviewedSigma · Medium · v2
Product
windows
Service
bits-client
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-06-10
Updated
2026-07-31

ATT&CK techniques

Execution → Defense Evasion
  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. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies BITS client activity (EventID 16403) where the remote FQDN for a BITS transfer uses a domain suffix that is uncommon or not in a small allowlist. Attackers can use BITS jobs to stage content or perform follow-on actions while blending into normal Windows background transfer behavior. The detection relies on Windows BITS-Client telemetry that records the remote destination (RemoteName) associated with the transfer event.

Related detections9 linkedT1197 — drag to rearrange
Suspicious Remote Script Transfer via Bitsadmin (via process_creation)
Suspicious File Download Via Bitsadmin Transfer
Suspicious Executable Download via bitsadmin Transfer (via process_creation)
BITS Job Persistence via Bitsadmin Notify Command (via process_creation)
BITS Payload Downloaded via Commandline (via process_creation)
BITS Payload Downloaded via PowerShell (via powershell)
Malicious mshta.exe Spawning bitsadmin via ClickFix Phantom Meet
Suspicious BITSAdmin File Transfer Download (via process_creation)
Suspicious sLoad Payload Download via BITSAdmin LOLBin Transfer (via process_creation)
Windows BITS Client Job Downloads From Uncommon Remote TLDs
Pivot detection · T1197 · 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.