File scan report
Verdict Suspicious
Is Setup.
Only three of the 63 antivirus engines that checked it flagged this unsigned installer, but unexplained and activity prevents treating the weak detections as harmless.
Read the whole reasonShow less
Why Suspicious? 3 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
3 of 63 flagged
- Flagged 3
- No detection 60
- No result 12
- Code signing Unsigned
- 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 detections are sparse, generic, and unsupported by any major antivirus engine or consistent malware family.
Three of the 63 antivirus engines that checked it raised alerts, but none were major and their labels disagree between grayware, a generic unsafe result, and Wacatac. One sandbox run completed without a malicious verdict, network contact, or persistence, which weighs against an active trojan finding. That run nevertheless mapped and T1134, two offensive techniques, although no injected target process was identified. The executable is unsigned and has no established publisher history, leaving those behavioral mappings insufficiently explained. Similar files sharing the import hash have mixed outcomes and different signers, so those framework-level matches provide little reassurance. No complete contacted-host reputation result is available, and the ten dropped files have no saved verdicts, leaving meaningful coverage gaps.
What We Detected
Three of the 63 antivirus engines that checked it flagged the executable. CrowdStrike described it as grayware, while Cylance and VBA32 supplied generic or inconsistent labels; no major antivirus engines detected it and there is no shared malware-family consensus.
Threat Behavior
One completed sandbox run returned clean and observed installer-style temporary processes and files, with no sample network contacts or persistence indicators. It also mapped T1055 process injection and T1134 access-token manipulation. No injected target process was recorded, so these mappings indicate concern but do not establish successful injection or malicious intent.
Evidence Limitations
The executable has no verified signature or publisher history. A complete reputation check was not available for contacted hosts, and all ten dropped files lack saved verdicts; those missing results are neutral rather than evidence of harm. Import-hash matches point to files from unrelated publishers with mixed outcomes, making them weak identity evidence.
What To Do Now
Do not run the installer until its exact download source and publisher can be independently verified. Keep security software enabled, obtain a fresh copy from the vendor's official release channel, and compare its SHA-256 before execution.
Where this verdict could be wrong3 caveats
- The single completed sandbox run returned clean and recorded no sample network contacts or persistence indicators.
- No malware-specific YARA rules or MalwareBazaar record matched the hash.
- The file has been submitted 396 times by 333 sources, which weakens the case for a narrowly distributed new threat.
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 major antivirus engines flagged the file.
- The completed sandbox run did not return a malicious verdict or observe persistence.
- No sample network contacts were recorded during the completed observation from the test run.
- No malware-specific research rules or known malware repository record matched the hash.
- The file has broad enough submission history to be inconsistent with a narrowly distributed sample.
- The Windows executable is unsigned and has no established publisher history.
- The test run mapped possible process injection and access-token manipulation.
- Three engines raised alerts, including one grayware assessment and two generic trojan-style labels.
- No complete host-reputation result is 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- 17sandbox rule tags
- 5spawned processes
- 0network contacts
- 17filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
Setup.exe
21ed9e876b225608b550699cfbae665b35140b6f1bd028f2bb70f8a2ce321048
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
Setup.exe
"C:\Users\<USER>\Desktop\Setup.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
Setup.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-A3SFP.tmp\Setup.tmp" /SL5="$150068,6949789,776704,C:\Users\<USER>\Desktop\Setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
Setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-A3SFP.tmp\Setup.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
Setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-2BLM7.tmp\Setup.tmp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 17 mapped techniques, every process, file, registry and network entry and 9 dropped files.
Show the technical evidenceChapter 04
Technical details
3 of the 63 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.
Engines that flagged it 3
- CrowdStrikewin/grayware_confidence_60% (D)
- CylanceUnsafe
- VBA32Trojan.Wacatac
File fingerprint
- Last analyzed
- Oct 17, 2026, 10:12 AM UTC
- SHA-256
21ed9e876b225608b550699cfbae665b35140b6f1bd028f2bb70f8a2ce321048- SHA-1
ce9c2dc4db0dc4a1b64be21d969e16192c3aafc9- MD5
cd944fec74e31083c7716d463cc7e314
About this file
Setup.exe is a Win32 EXE file of 7.8 MB.
- Type and size
- Win32 EXE · 7.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jun 9, 2026On VirusTotal.
- Submitted by
- 333 distinct sources
- Packer
- None detected
- Entropy
- 6.27 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Setup.exe safe, or is it malware?
What is Setup.exe?
How many antivirus engines detected Setup.exe?
What should I do if I already installed Setup.exe?
What is the SHA-256 hash of Setup.exe?
How up to date is this analysis of Setup.exe?
Community
Member reviews and reports for this exact file hash.