File scan report
Verdict Safe
Is setup.
This unsigned Windows Installer package drew no detections from any of 75 antivirus engines, and the combined sandbox verdict across three runs was clean.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The evidence shows no threat, but install it only if it came from the vendor you expect, since the package is unsigned. Keep your security software enabled during installation.
Good practice2 tips
We found nothing harmful in this file.
Install 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 62 flagged
- Flagged 0
- No detection 62
- No result 13
- Code signing Unsigned
- Test run Completed
- First seen 18d ago
Chapter 02
Why we think so
1 point against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 62 antivirus engines that checked it flagged this installer, including all 18 major antivirus engines. During sandbox execution it ran only standard Windows Installer processes, with no high-risk techniques and no injection targets.
None of the 62 antivirus engines that checked it flagged the file, and all 18 major antivirus engines among the 62 that analysed it returned clean results. Activity was limited to msiexec installation steps and techniques common in legitimate software. Public malware-sample databases and community rule sets returned no matches. The package is unsigned and moderately shared, with 41 submitters since it was first seen on Oct 7, 2026, so the publisher identity cannot be confirmed.
What We Detected
None of the 62 antivirus engines that checked it flagged this Windows Installer package; the major antivirus engines that reported, including Kaspersky, ESET, Microsoft and BitDefender, returned clean results. It has no matches in public malware-sample databases or community rule sets. The package carries no digital signature.
Threat Behavior
The combined sandbox verdict was clean. The installer ran through msiexec with standard installation activity and showed no high-risk techniques. No process injection target and no network contacts of its own were recorded. A complete reputation check of contacted hosts was not available.
What To Do Now
If you obtained this installer from the software vendor you intended, the evidence does not indicate a threat. Because it is unsigned, confirm the download source, and keep your antivirus protection enabled while installing.
Where this verdict could be wrong2 caveats
- The installer is unsigned, so no publisher identity backs it. A clean engine and sandbox result cannot rule out a fresh, undetected payload.
- The contacted-host reputation check was not available, and our own static analysis of the contents was not run.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No detections from any of the 75 antivirus engines, including all major antivirus engines that reported.
- The combined sandbox verdict across three runs was clean, with only standard installer activity.
- No matches in public malware-sample databases or community malware rules.
- The installer package has no digital signature, so the publisher cannot be confirmed.
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 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 9sandbox rule tags
- 3spawned processes
- 0network contacts
- 10filesystem & 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.
- T1033· Reads user info
- T1036
- T1055· Process injection
- T1069
- T1082· System recon
- T1091· USB spreading
- T1120
- T1485
- T1497· Sandbox evasion
Observed activity
Processes started
3Programs the file ran, with their command lines.
msiexec.exe"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\install.msi" /qb ACCEPTEULA=1 LicenseAccepted=1slui.exeC:\Windows\System32\slui.exe -Embeddingmsiexec.exe"C:\Windows\System32\msiexec.exe" /i "C:\Users\user\Desktop\install.msi"
Files
8Files the file created, changed or deleted.
- Written
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp - Written
C:\MSIadf6f.tmp - Written
C:\ProgramData - Written
C:\ProgramData\Microsoft\Windows\Templates - Written
C:\Windows\Fonts - Written
C:\Windows\system32\catroot
Show all 8 entries for files
- Written
C:\Windows\system32\catroot2 - Deleted
C:\MSIadf6f.tmp
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
Global\_MSIExecute\BaseNamedObjects\Local\SM0:7132:304:WilStaging_02
Sandbox background — not the file
7The 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 LocalService -s W32Time
Show all 7 entries for sandbox background — not the file
- VM process
msiexec.exeC:\Windows\System32\msiexec.exe C:\Windows\system32\msiexec.exe /V
Chapter 04
Technical details
None of the 62 antivirus engines that checked it flag it; no publisher signature.
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
- Oct 26, 2026, 9:59 AM UTC
- SHA-256
4395572a5b8f8ed32d8569f28788c85e4e901ad7688afc6cb73b3f9164e18ecf- SHA-1
28ebf076c9af85daed0bfab6821f5e4d05fc478a- MD5
0148bb057c2460c03678a105ae4822a0
About this file
setup.msi is a Windows Installer file of 10.7 MB.
- Type and size
- Windows Installer · 10.7 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 7, 2026On VirusTotal.
- Submitted by
- 41 distinct sources
First scanned
Antivirus consensus
0 of 62 engines flagged this file
13 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-233 engines0flagged
- Low-trust11 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaNo result
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticNo result
- 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
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootNo result
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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)
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 6 questions people ask most about this file.
Is setup.msi safe?
What is setup.msi?
How many antivirus engines detected setup.msi?
What is the SHA-256 hash of setup.msi?
Is it safe to install setup.msi?
How up to date is this analysis of setup.msi?
Community
Member reviews and reports for this exact file hash.