File scan report
Verdict Suspicious
Is Setup.
One generic grayware detection lacks runtime or intelligence corroboration, but the unsigned executable is too new and uncommon to establish confidently.
Read the whole reasonShow less
Why Suspicious? One antivirus engine (CrowdStrike) flags it; 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
1 of 71 flagged
- Flagged 1
- No detection 70
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 8d 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
Only 1 of the 71 antivirus engines that checked it flagged this installer, using a generic grayware label, while major engines remained silent. The test run found no high-risk technique or named injection target, but the file is unsigned and leaving its publisher and longer-term reputation unresolved.
CrowdStrike was the only engine to flag the sample, and its label describes generic grayware rather than a named malware family. The observations from the test run produced no malicious sandbox assessment, no named injection target, and no sample-generated network contact. The mapping lacks the artifact needed to establish process injection and therefore carries no adverse weight. No malicious host, malicious child, public sample-database listing, or malware-specific YARA rule corroborates the detection. However, the executable has no signature and has been submitted by only one source since it was first observed, so there is not enough provenance or history for a firm benign conclusion. Similar import hashes offer mixed, weak context because none shares a verified publisher with this sample.
What We Detected
Only 1 of the 71 antivirus engines that checked it flagged the executable. CrowdStrike used a generic grayware label, while no major antivirus engines identified malware and no engine consensus named a family.
Threat Behavior
Five completed sandbox runs produced no malicious assessment, no high-risk technique, and no named process-injection target. The T1055 mapping was recorded without an injection artifact and does not demonstrate actual injection. The sole observed domain was identified as analysis-environment background traffic, and the complete host check found no malicious or suspicious host.
Additional Context
No malware-specific YARA rule or public sample-database entry matched the hash. No inspected child was harmful, and one identified child matched a known-software reference entry. Against that, the executable is unsigned, and has very limited prevalence, so its origin cannot be authenticated.
What To Do Now
Obtain the installer from the software publisher's official release channel and verify its checksum or signature before running it. Keep security software enabled and avoid execution if the source cannot be independently verified.
Where this verdict could be wrong3 caveats
- CrowdStrike identified the executable as grayware, which may indicate unwanted installer behavior even though no other engine corroborated it.
- The executable is unsigned and only recently observed, so its publisher and longer-term reputation cannot be established.
- Four prior files sharing this import hash received cautionary assessments, although the shared hash may reflect a common installer framework rather than common authorship.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of the 71 antivirus engines that checked it flagged the file, and no major antivirus engines detected it.
- Completed the test run produced no malicious assessment or high-risk behavior.
- No named injection target was observed.
- No malicious host or harmful inspected child was identified.
- No malware-specific community rule or public sample-database entry matched the hash.
- The executable is unsigned, so its publisher cannot be authenticated.
- It was first observed very recently and has been submitted by only one source.
- CrowdStrike reported a generic grayware detection.
- Several files sharing the same import hash previously received cautionary assessments, though this may reflect a shared installer framework.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 5 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 5isolated sandbox runs
- 19sandbox 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: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
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.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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
c77c38d743e0d58cc94514da2b26a3333176ec6b2baed806a0bf34671b9580db
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-600S7.tmp\Setup.tmp" /SL5="$230048,3411790,140800,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-600S7.tmp\Setup.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-3IT6S.tmp\_isetup\_setup64.tmp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 19 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 71 antivirus engines that checked it flags it; no publisher signature.
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.
Engines that flagged it 1
- CrowdStrikewin/grayware_confidence_60% (D)
File fingerprint
- Last analyzed
- Oct 19, 2026, 12:46 AM UTC
- SHA-256
c77c38d743e0d58cc94514da2b26a3333176ec6b2baed806a0bf34671b9580db- SHA-1
28c88a28f2a289f72e4306aed31f184b781d7991- MD5
9aa59fb072a4afba9a750f4791120f26
About this file
Setup.exe says it is Uncharted: The Nathan Drake Collection Setup (Uncharted: The Nathan Drake Collection), 4.1 MB.
- Claims to be
- Uncharted: The Nathan Drake Collection Setup (Uncharted: The Nathan Drake Collection)From the file's own version information, written by whoever built it.
- Type and size
- Win32 EXE · 4.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 18, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 5.55 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.