File scan report
Verdict Malicious
Is setup. exe safe? No, we rate this exact file malicious.
23 of the 71 antivirus engines that checked it flag the file, including five major detections on crack/hacking tool labels.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already installed it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't installed it
Don't install this file. Delete it, then empty the Recycle Bin.
If you already installed it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (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
23 of 71 flagged
- Flagged 23
- No detection 48
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 2y ago
Chapter 02
Why we think so
4 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The file is unsigned and contacts known suspicious hosts.
Five major antivirus engines independently label the sample as a crack or hacking tool, satisfying the hacktoolConfirmed rule. The unsigned status removes any trusted-publisher defence. Observed MITRE techniques T1055, and are offensive and corroborated by sandbox data. Five YARAify rules add community-researcher consensus. Similar-hash history shows four of five prior matches rated suspicious or malicious, outweighing the two dissenting signals of zero malicious hosts and unknown files it created.
What We Detected
23 of the 71 antivirus engines that checked it report the file malicious. Major detections include Microsoft (HackTool:Win32/crack), GData (Generic.Trojan.PSEB), Sophos (Generic Reputation unwanted program), Symantec (Trojan.Gen.MBT) and TrendMicro (Trojan.Win32.ZYX.USBLE826). YARAify matched five rules covering shellcode, TLS-callback anti-debug and obfuscation patterns.
Threat Behavior
The sample wrote multiple temporary DLLs and executables typical of Inno Setup installers used to deliver cracks. It contacted 16 IP addresses and two suspicious domains (fitgirl-repacks.site, bit.ly) already flagged in our cache.
What To Do Now
Do not execute the file. Keep security software enabled. If the file was downloaded from an untrusted source, delete it and scan the system for additional artefacts. Report the hash to your security vendor if further analysis is required.
Where this verdict could be wrong2 caveats
- contactedHosts.maliciousHosts.length=0 — no confirmed malicious hosts in cache
- No dropped file is known to be malicious — all 10 files it created returned unknown verdicts
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 malicious files it created detected
- no complete contacted-host reputation result was available in contacted-host cache
- Unsigned executable
- Five major hacking tool detections
- Contacts suspicious domains
- YARAify community rules triggered
6 sources checked · 5 complete · 1 partial. 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- 29sandbox rule tags
- 15spawned processes
- 8network contacts
- 37filesystem & 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: Used an unusual way to talk to a server.
Moderate concern: Downloaded a file during the test run.
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.
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 recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change 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.
Threat context
How cracked-software installers work
A crack or patch installer is one of the most common ways to spread trojans. Even if the program seems to work, it can install malware in the background.
Bottom line:There is no safe copy of a cracked installer: delete it, and get the software from its real publisher.
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
5c4105123bf84673cb3aeff2400fffbde35f3fc048ccbfe8a72614e7c76854d0
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
software.exe
"C:\Users\<USER>\Desktop\software.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
software.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-UQBTG.tmp\software.tmp" /SL5="$60034,6446506,140800,C:\Users\<USER>\Desktop\software.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
software.tmp
C:\Users\<USER>\AppData\Local\Temp\is-UQBTG.tmp\software.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-I8DEG.tmp\_isetup\_setup64.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
23.62.210.8
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
23.44.253.134
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 29 mapped techniques, every process, file, registry and network entry, 10 dropped files and contacted-host reputation.
Show the technical evidenceChapter 04
Technical details
23 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 23
- GData (major engine)Generic.Trojan.PSEB.1P9XTU
- Microsoft (major engine)HackTool:Win32/crack
- Sophos (major engine)Generic Reputation PUA (PUA)
- Symantec (major engine)Trojan.Gen.MBT
- TrellixENS (major engine)Artemis!80F64A1964F4
- TrendMicro (major engine)Trojan.Win32.ZYX.USBLE826
- TrendMicro-HouseCall (major engine)Trojan.Win32.ZYX.USBLE826
- alibabacloudTrojan:Win/Crack.Gen
File fingerprint
- Last analyzed
- Sep 2, 2026, 10:20 PM UTC
- SHA-256
5c4105123bf84673cb3aeff2400fffbde35f3fc048ccbfe8a72614e7c76854d0- SHA-1
d9799b4761f9277abfd535ebb3882697f7a148f7- MD5
80f64a1964f441134509a6992c538578
About this file
setup.exe is a Win32 EXE file of 7.1 MB.
- Type and size
- Win32 EXE · 7.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 24, 2024On VirusTotal.
- Submitted by
- 3,447 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Includes every engine result (75), 6 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is setup.exe a virus?
What is setup.exe?
How many antivirus engines detected setup.exe?
What should I do if I already installed setup.exe?
How do I remove setup.exe?
What kind of malware is 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.