BITS Jobs
Also called Background Intelligent Transfer Service Abuse.
Using Windows' background transfer service to fetch or run payloads.
What it is
Abusing the Background Intelligent Transfer Service, a built-in Windows mechanism for resilient file transfers, to download payloads or execute commands. Jobs persist across reboots and run under a trusted system service.
Why it matters
BITS traffic resembles ordinary update activity and survives logoff and restart, giving attackers a low-profile channel for download, execution, and persistence. Its job queue and dedicated logs are evidence sources defenders frequently miss.
In practice
An investigation finds a long-lived BITS job quietly re-downloading a payload from an external host hours after the original file was deleted.
What to look for
- BITS jobs created by bitsadmin or PowerShell outside normal update activity.
- Jobs with a notify command that runs a program when the transfer finishes.
- Event logs in Microsoft-Windows-Bits-Client showing downloads from unusual hosts.
Common mistake
Treating BITS traffic as Windows Update. The service is legitimate, so check the job's source URL and its notify command.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
- Hunt Query Builder
Build a hunting query in KQL, SPL, LogScale or PowerQuery against documented field names, or start from a prebuilt hunt.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Atomic Red Team Open source
Small, scripted tests mapped to ATT&CK techniques, used to check whether a detection fires.
-
ATT&CK Navigator Open source
Lays techniques out on the ATT&CK matrix so teams can mark coverage, gaps and threat profiles.
-
Microsoft Defender for Endpoint Commercial
Tags its alerts with the ATT&CK techniques it observed on the host.
-
Sysmon Free
Supplies the host telemetry that most technique detections are written against. Our notes.
Read next
- Signed Binary Proxy Execution: Hiding code execution behind a trusted, signed system binary.
- Service Execution: Creating or hijacking a system service to run attacker code.
- Indicator Removal: Deleting the traces an intrusion leaves behind to evade detection.