File scan report
Verdict Safe
Is background
This validly Microsoft-signed 64-bit executable was flagged by none of the 69 antivirus engines that checked it, the sandbox runs were clean, and five earlier files with the same…
Read the whole reasonShow less
Strong evidence · A verified publisher signature, and no engine flags it.
No action is needed; this appears to be a genuine signed Microsoft component. Keep your antivirus protection enabled.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 69 flagged
- Flagged 0
- No detection 69
- No result 6
- Code signing Microsoft Windows
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 69 antivirus engines that checked it flagged this file, and it carries a valid Microsoft Windows signature. The combined sandbox verdict was clean with no injected processes or dropped files. Five similar earlier files from the same signer were all clean.
The file has a valid signature from Microsoft Windows, a publisher on our trusted list, with 6 of 6 prior samples from this signer clean. The sandbox mapped a process-injection technique but recorded no target process, which is common on clean software. Two community YARA rules matched, but both are generic and one ransomware-named rule has no supporting evidence. Similar earlier files from this signer were all judged benign.
What We Detected
No engine flagged this signed 64-bit executable. Two generic community YARA rules matched, which ordinary software also triggers.
Threat Behavior
The combined sandbox verdict was clean. No injected processes, dropped files or persistence were recorded, and the only network contact was the analysis VM's background traffic.
What To Do Now
No action is needed. Keep your security software enabled as usual.
Where this verdict could be wrong1 caveat
- A community YARA rule named for a ransomware family matched, but it is classed as generic and nothing else (engines, sandbox behaviour, dropped files) supports it.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Valid signature from Microsoft Windows, a trusted publisher
- None of the 69 antivirus engines that checked it flagged the file
- Combined sandbox verdict was clean with no injected processes
- Five earlier files from the same signer were all judged benign
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 9sandbox rule tags
- 2spawned processes
- 0network contacts
- 1filesystem & mutex artifacts
What this file did when executed
This file was detonated in 3 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
9MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1070· Covers its tracks
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1129· Loads modules
Observed activity
Processes started
2Programs the file ran, with their command lines.
executable.exe"C:\Users\<USER>\Desktop\executable.exe"executable.exe"C:\Users\user\Desktop\executable.exe"
Mutexes
1Named locks a program uses so only one copy runs; malware families often reuse them.
Global\OneSettingQueryMutex+compat+encapsulation
Sandbox background — not the file
9The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost
Show all 9 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p - VM host
cl-glcb907925.gcdn.co
Chapter 04
Technical details
None of the 69 antivirus engines that checked it flag it; signed by Microsoft Windows.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 23, 2026, 4:55 PM UTC
- SHA-256
3cb5ec15407212ab5220d6ec38c8304f834840e6e38b2b43ebe5c3bf7a161f6f- SHA-1
50b13589b2f0e59da9fe30cc902abf90af8e273f- MD5
9ffd4330ed2f9f777b6965f279a8a91c
About this file
backgroundTaskHost.exe is a Win32 EXE file of 60.8 kB.
- Claims to be
- Background Task Host (Microsoft® Windows® Operating System)From the file's own version information, written by whoever built it.
- Original name
- backgroundTaskHost.exeMatches the shared file name.
- Type and size
- Win32 EXE · 60.8 kB
- Signer
- Microsoft WindowsValid code signature.
- First seen
- Sep 22, 2026On VirusTotal.
- Submitted by
- 48 distinct sources
- Packer
- None detected
- Entropy
- 1.41 of 8
First scanned
Antivirus consensus
0 of 69 engines flagged this file
6 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-234 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaNo result
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Community YARA rules matched, but all of them are generic capability, anti-debug or compiler rules that ordinary software also matches. Worth noting, not on their own cause for alarm.
- PE_Digital_Certificategeneric
- VECT_Ransomwaregeneric
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is backgroundTaskHost.exe safe?
What is backgroundTaskHost.exe?
How many antivirus engines detected backgroundTaskHost.exe?
Is backgroundTaskHost.exe digitally signed?
What is the SHA-256 hash of backgroundTaskHost.exe?
Is it safe to run backgroundTaskHost.exe?
How up to date is this analysis of backgroundTaskHost.exe?
Community
Member reviews and reports for this exact file hash.