File scan report
Verdict Safe
Is svchost.
All 69 antivirus engines that checked it remained silent, while verified Microsoft signing, broad prevalence, and the absence of a malicious sandbox finding strongly support…
Read the whole reasonShow less
Strong evidence · A verified publisher signature, and no engine flags it.
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 69 flagged
- Flagged 0
- No detection 69
- No result 6
- Code signing Microsoft Windows Publisher
- Test run Completed
- First seen 4mo ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The executable carries a verified Microsoft Windows Publisher signature, and none of the 69 antivirus engines that checked it flagged it. One sandbox recorded a potentially sensitive technique, but issued no malicious finding, created no persistence, dropped no files, and observed no network contacts.
The strongest evidence is the complete absence of detections across 75 antivirus engines, including no major flags. The executable is signed by Microsoft Windows Publisher, and the signature verifies against the curated Microsoft publisher identity. It has also been submitted 8,859 times by 2,060 sources, which is inconsistent with an isolated impersonation attempt. One sandbox associated the run with T1562.001, but reported no malicious outcome, persistence, dropped files, or network contacts. The code section is not unusually entropic and packing was not identified. A separate contacted-host reputation result was not available, so no claim of a completed network-reputation check is made.
What We Detected
The file has a verified signature from Microsoft Windows Publisher, with the publisher identity matching Microsoft. It also has substantial prevalence: 8,859 submissions from 2,060 sources.
Threat Behavior
One completed sandbox run produced no malicious sandbox verdict. Static PE analysis found neither high-entropy code nor likely packing. No separate contacted-host reputation result was saved, so complete network-reputation coverage cannot be claimed.
What To Do Now
Confirm that the signature remains valid in Windows file properties and that the file resides in the expected Windows system directory. Keep security software enabled; investigate further if the signature fails, the file is outside a normal Windows path, or its hash changes.
Where this verdict could be wrong3 caveats
- The sandbox's offensive-technique list includes T1562.001, which can indicate impairment of security controls, although the single sandbox issued no malicious verdict.
- The missing contacted-host reputation result means no completed reputation check is available for network hosts, though the observed run listed no contacts.
- This signer has no saved history, so there is no hash-corpus history for this signer within the provided evidence.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/69 antivirus detections.
- Verified Microsoft Windows Publisher signature.
- Curated trusted-publisher match for Microsoft.
- No malicious sandbox verdict.
- No packing or high-entropy code identified.
- Sandbox mapping includes offensive technique T1562.001.
- The filename svchost.exe is commonly imitated by malware, making the file path and signature important.
- No completed contacted-host reputation cross-check is available.
- No internal historical signer statistics were available.
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 10sandbox rule tags
- 2spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
Includes 10 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
None of the 69 antivirus engines that checked it flag it; signed by Microsoft Windows Publisher.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 11, 2026, 3:43 AM UTC
- SHA-256
1222a44a5fdb4efde4dfcb41093648627950e7ec02d8667f1c26ccae31d922e2- SHA-1
0bac26fca769fbecab983e3cfba95140d55e0855- MD5
07fe1be55d1049c7b48e270c466502d4
About this file
svchost.exe is a Win32 EXE file of 88.3 kB.
- Type and size
- Win32 EXE · 88.3 kB
- Signer
- Microsoft Windows PublisherValid code signature.
- First seen
- Jun 23, 2026On VirusTotal.
- Submitted by
- 2,060 distinct sources
- Packer
- None detected
- Entropy
- 7.50 of 8
First scanned Updated
Includes every engine result (75), PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is svchost.exe safe?
What is svchost.exe?
How many antivirus engines detected svchost.exe?
Is svchost.exe digitally signed?
What is the SHA-256 hash of svchost.exe?
Is it safe to run svchost.exe?
How up to date is this analysis of svchost.exe?
Community
Member reviews and reports for this exact file hash.