File scan report
Verdict Suspicious
Is setup.
This unsigned installer is flagged by 10 of the 71 antivirus engines that checked it, including four major ones with crack-related and trojan labels, and one sandbox verdict was…
Read the whole reasonShow less
Why Suspicious? 10 antivirus engines flag it and one sandbox test run rated it malicious while another found nothing.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
Avoid running this installer and download the software only from its official publisher. If it has already been run, keep your security software enabled and perform a full system scan.
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
10 of 71 flagged
- Flagged 10
- No detection 61
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 8d ago
Chapter 02
Why we think so
5 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This unsigned Inno Setup installer, first seen on Oct 25, 2026, is flagged by 10 of the 71 antivirus engines that checked it. Microsoft, Ikarus, Sophos and Trellix are among them, and Malwarebytes labels it a crack-related riskware. The sandbox results were split between malicious and clean, with no confirmed injection or malicious network contact.
Four major antivirus engines flag the file, but they do not agree on a family: their labels range from a Microsoft trojan label to a reputation-based unwanted program label and a lone Meterpreter detection. Malwarebytes calls it crack-related riskware, which fits a repackaged or cracked-software installer. The combined sandbox verdict was split, and no process injection target or malicious contacted host was recorded. The file is unsigned, and although many sources submitted it, it was first seen on Oct 25, 2026. Similar installers built with the same import table were previously rated as mixed-signal files. Together this is real risk without decisive proof of malware.
What We Detected
10 of the 71 antivirus engines that checked it flagged this unsigned Windows installer. The detections include Microsoft (Trojan:Win32/Yomal!rfn), Ikarus (Trojan.Win64.Meterpreter), Sophos (a reputation-based unwanted program label), Trellix (a generic label) and Malwarebytes (RiskWare.Crack). The engines do not agree on a single malware family.
Threat Behavior
Across 7 sandbox runs, the combined verdict was split between malicious and clean. The installer unpacked an Inno Setup chain into the temporary folder, dropping helper DLLs and an executable. No named process injection was recorded, and the only network contact attributable to the sample was a standard connectivity check. The hosts that were checked showed no known-malicious reputation.
What To Do Now
Do not run this installer unless you obtained it from the software's official publisher. Crack and repack installers are a common way to deliver unwanted or malicious software. If you have already run it, keep your antivirus enabled and perform a full scan.
Where this verdict could be wrong1 caveat
- Contacted-host checks covered all observed hosts and found none malicious; no malicious dropped file was identified.
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 process injection target was recorded in the sandbox runs
- None of the checked contacted hosts is known to be malicious
- No known malware-specific rule or public malware database entry matched
- Four major antivirus engines flag the file, including a trojan label from Microsoft
- Malwarebytes labels it crack-related riskware
- One sandbox verdict was malicious, while another was clean
- The file is unsigned, so its publisher cannot be verified
- The file was first seen on Oct 25, 2026
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 7 isolated tests; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 7isolated sandbox runs
- 26sandbox rule tags
- 5spawned processes
- 2network contacts
- 24filesystem & 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: Unpacked hidden content while it ran.
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: Talked to servers over the internet during the test run.
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 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 7: FileSeen in the test run
setup.exe
dc0e3e0eff9f4fd787c9edeb0be20171b09f64002fecee358ab87ab951f3a527
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
setup.exe
"C:\Users\<USER>\Desktop\setup.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
setup.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-1ALQH.tmp\setup.tmp" /SL5="$40188,4470969,140800,C:\Users\<USER>\Desktop\setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-1ALQH.tmp\setup.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-DJDRP.tmp\_isetup\_setup64.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
www.msftncsi.com
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
23.33.22.143
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 26 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
10 of the 71 antivirus engines that checked it flag 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 10
- Ikarus (major engine)Trojan.Win64.Meterpreter
- Microsoft (major engine)Trojan:Win32/Yomal!rfn
- Sophos (major engine)Generic Reputation PUA (PUA)
- TrellixENS (major engine)Artemis!435F13CFB753
- alibabacloudTrojan:Win/Yomal.Gen
- BkavW32.Malware.2A0121B2
- GoogleDetected
- MalwarebytesRiskWare.Crack
File fingerprint
- Last analyzed
- Oct 28, 2026, 6:59 AM UTC
- SHA-256
dc0e3e0eff9f4fd787c9edeb0be20171b09f64002fecee358ab87ab951f3a527- SHA-1
2d6f042afacd7c013b26fd794880405302b1dff0- MD5
435f13cfb753de106fcb648c693b8316
About this file
setup.exe says it is Cyberpunk 2077 Setup (Cyberpunk 2077), 5.1 MB.
- Claims to be
- Cyberpunk 2077 Setup (Cyberpunk 2077)From the file's own version information, written by whoever built it.
- Type and size
- Win32 EXE · 5.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 25, 2026On VirusTotal.
- Submitted by
- 284 distinct sources
- 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?
I already downloaded and installed setup.exe — what should I do?
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.