File scan report
Verdict Suspicious
Is setup.
This unsigned installer is labelled by engines as a software crack, with 4 of the 70 antivirus engines that checked it flagging it, including one major antivirus engine using a…
Read the whole reasonShow less
Why Suspicious? 4 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Avoid running this installer and get the software from the publisher's official website. Keep your security software enabled.
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
4 of 70 flagged
- Flagged 4
- No detection 66
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Four of the 70 antivirus engines that checked it flagged this unsigned setup file. Malwarebytes labels it risky crack software and GData uses a generic trojan label. The sandbox run showed typical installer activity and no network contacts. Cracked software is a common carrier for unwanted or harmful payloads, and nothing here establishes a trustworthy source.
The file is an unsigned Windows installer first seen on Aug 1, 2026, and only a handful of sources have submitted it. Four of the 70 antivirus engines that checked it flagged it. Malwarebytes calls it crack riskware, while GData, one of the major antivirus engines, applies a generic trojan label with no named family. Sixteen other major antivirus engines reported nothing. The sandbox run showed the installer unpacking its setup components, with no network contacts and no injected processes. With no signature or wide prevalence to vouch for it, and a crack-style label attached, the file warrants caution rather than trust.
What We Detected
4 of the 70 antivirus engines that checked it flagged this file. Malwarebytes reports risky crack software, GData reports a generic trojan, and two less reliable engines give generic or machine-learning labels. No engine names a malware family. The file carries no digital signature.
Threat Behavior
In the sandbox summary, the installer extracted its temporary setup program and helper libraries, which is the typical pattern of a scripted Windows installer. No network contacts, persistence or process injection were recorded. A complete reputation check of contacted hosts was not available. The crack-style labels suggest the installer may package pirated or modified software, which commonly carries unwanted extras.
What To Do Now
Do not run this installer unless you obtained it from the official software publisher. Keep your antivirus enabled, and get the software from its official source instead.
Where this verdict could be wrong1 caveat
- Sixteen major antivirus engines reported no detection, and the sandbox run showed only ordinary installer activity with no network contacts or injected processes, so the generic trojan label may be a false positive on a crack-style installer.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Sixteen major antivirus engines reported no detection
- The sandbox run recorded no network contacts and no injected processes
- No listing in public malware databases or malware-specific rule matches
- Malwarebytes labels the file as risky crack software
- GData, a major antivirus engine, applies a generic trojan label
- The installer is unsigned, so its publisher cannot be identified
- Only a few sources have submitted it, so there is little reputation history
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- 15sandbox rule tags
- 3spawned processes
- 0network contacts
- 15filesystem & 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.
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
69953dbb09b0a6a8f6531c5b7865fdcf9754b92ba28b04eed146026948929301
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
setup.exe
C:\Users\<USER>\AppData\Local\Temp\is-LDB56.tmp\setup.tmp /SL5=$100116,4826238,140800,C:\Users\<USER>\Downloads\setup.exe
Test run - Evidence 3 of 5: ProcessSeen in the test run
setup.exe
"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-LDB56.tmp\setup.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-F1G52.tmp\_isetup\_setup64.tmp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
15MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1134
- T1497.001· Sandbox evasion
- T1529
- T1614
- T1614.001
Observed activity
Processes started
3Programs the file ran, with their command lines.
setup.exeC:\Users\<USER>\AppData\Local\Temp\is-LDB56.tmp\setup.tmp /SL5=$100116,4826238,140800,C:\Users\<USER>\Downloads\setup.exesetup.exe"C:\Users\user\Desktop\setup.exe"setup.tmp"C:\Users\user\AppData\Local\Temp\is-Q7HI8.tmp\setup.tmp" /SL5="$10402,4826238,140800,C:\Users\user\Desktop\setup.exe"
Files
13Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\is-LDB56.tmp\setup.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\is-F1G52.tmp\_isetup\_setup64.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\is-F1G52.tmp\_isetup\_shfoldr.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-F1G52.tmp\idp.dll - Written
C:\Users\user\AppData\Local\Temp\is-Q7HI8.tmp - Written
C:\Users\user\AppData\Local\Temp\is-Q7HI8.tmp\setup.tmp
Show all 13 entries for files
- Written
C:\Users\user\AppData\Local\Temp\is-SM3TS.tmp - Written
C:\Users\user\AppData\Local\Temp\is-SM3TS.tmp\ISDone.dll - Written
C:\Users\user\AppData\Local\Temp\is-SM3TS.tmp\_isetup - Written
C:\Users\user\AppData\Local\Temp\is-SM3TS.tmp\_isetup\_setup64.tmp - Written
C:\Users\user\AppData\Local\Temp\is-SM3TS.tmp\_isetup\_shfoldr.dll - Written
C:\Users\user\AppData\Local\Temp\is-SM3TS.tmp\idp.dll - Written
C:\Users\user\AppData\Local\Temp\is-SM3TS.tmp\innocallback.dll
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
\Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511\Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache. 6 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 09af8004b85478e1eca0…47b449Not checkedno saved verdict
- a4c86fc4836ac728d7bd…95fd81Not checkedno saved verdict
- 9884e9d1b4f8a873ccbd…360d87Not checkedno saved verdict
- f4fc0187491a9cb89e23…bc44bbNot checkedno saved verdict
- c652b4b564b3c85c3991…412c74Not checkedno saved verdict
- 6afa2d104be6efe3d9a2…29809fNot checkedno saved verdict
Chapter 04
Technical details
4 of the 70 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 4
- GData (major engine)Generic.Trojan.PSEB.IULN58
- BkavW32.Malware.E1E06090
- MalwarebytesRiskWare.Crack
- Paloaltogeneric.ml
File fingerprint
- Last analyzed
- Sep 12, 2026, 12:10 AM UTC
- SHA-256
69953dbb09b0a6a8f6531c5b7865fdcf9754b92ba28b04eed146026948929301- SHA-1
619125ef5c99e57861263e6e0552647259657940- MD5
32515e149540bbbdcfb70d6619a5c8af
About this file
setup.exe is a Win32 EXE file of 5.4 MB.
- Type and size
- Win32 EXE · 5.4 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 1, 2026On VirusTotal.
- Submitted by
- 5 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Antivirus consensus
4 of 70 engines flagged this file
5 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-117 engines1flagged
- Tier-236 engines1flagged
- Low-trust17 engines2flagged
View all 75 engine results
- BkavMalicious: W32.Malware.E1E06090
- GDataMalicious: Generic.Trojan.PSEB.IULN58
- MalwarebytesMalicious: RiskWare.Crack
- PaloaltoMalicious: generic.ml
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- 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)
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
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.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.