File scan report
Verdict Suspicious
Is setup.
Four engines flag the file, one of them major, naming a crack/PSEB family.
Why Suspicious? 4 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat the file as suspicious; avoid execution and delete it unless a trusted publisher can supply a signed replacement.
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 69 flagged
- Flagged 4
- No detection 65
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 4mo ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Samples built with the same import table have been labelled malicious or suspicious as crack tools.
The one detection from a major antivirus engine and four low-to-medium offensive MITRE techniques outweigh the lack of sandbox malice verdict and absence of dropped malicious files it created. Unsigned status and prior import-table fingerprint matches labelled crack reduce confidence in a clean classification. Medium prevalence and installer filename keep the file in mixed-signals territory rather than malicious.
What We Detected
Four of the 69 antivirus engines that checked it flagged the sample. GData (major) labelled it Generic.Trojan.PSEB.IVLRDN; Malwarebytes labelled it RiskWare.Crack. The file is an unsigned 5.4 MB Win32 EXE with an Inno Setup-style installer hint.
Threat Behavior
Ten files it created were inspected; none carried malicious verdicts.
What To Do Now
Do not execute the file. Keep Windows Defender and other security software enabled. If the file was downloaded from an untrusted source, delete it and scan the system with current signatures.
Where this verdict could be wrong2 caveats
- 1 major antivirus engine flagged it and major antivirus engines do not agree on one malware family — only one major antivirus engine
- No dropped file is known to be malicious and 10 children inspected with no malicious 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.
- Only one major antivirus engine flagged
- No malicious files it created
- No sandbox malicious verdict
- Unsigned executable
- Major crack-family detection
- Prior import-table fingerprint matches labelled malicious
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- 25sandbox rule tags
- 8spawned processes
- 0network 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: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
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.
Not confirmed: A sandbox rule tagged this run as downloading a file, but no download 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
8d27c67549dac53d04b1f5cc4fc13beb4f706cc35051c23dec1e4c80fbcc5bd0
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-5AO72.tmp\setup.tmp" /SL5="$4006C,4815279,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-5AO72.tmp\setup.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.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
25MITRE 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
- T1036
- T1055· Process injection
- T1059· Runs commands
- T1070· Covers its tracks
- T1071· Application protocol
- T1074
- T1082· System recon
- T1083· Scans your files
- T1105· Network file transfer
- T1129· Loads modules
- T1134
- T1202
- T1485
- T1497· Sandbox evasion
- T1497.001· Sandbox evasion
- T1529
- T1548
- T1573
- T1574· Execution hijack
- T1614
- T1614.001
Observed activity
Processes started
8Programs the file ran, with their command lines.
setup.exe"C:\Users\<USER>\Desktop\setup.exe"setup.tmp"C:\Users\<USER>\AppData\Local\Temp\is-5AO72.tmp\setup.tmp" /SL5="$4006C,4815279,140800,C:\Users\<USER>\Desktop\setup.exe"cmd.exe"C:\Windows\system32\cmd.exe" /C C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\fnr.exe arc.ini fgrplc -1fnr.exeC:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\fnr.exe arc.ini fgrplc -1FlushFileCache.exe"C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\FlushFileCache.exe"unins000.exe"C:\Games\Need for Speed - Payback\unins000.exe" /VERYSILENT
Show all 8 entries for processes started
_iu14D2N.tmp"C:\Users\<USER>\AppData\Local\Temp\_iu14D2N.tmp" /SECONDPHASE="C:\Games\Need for Speed - Payback\unins000.exe" /FIRSTPHASEWND=$4024E /VERYSILENTsetup.exeC:\Users\<USER>\AppData\Local\Temp\is-PT5NU.tmp\setup.tmp /SL5=$2018E,4815279,140800,C:\Users\<USER>\Downloads\setup.exe
Files
30Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\is-5AO72.tmp\setup.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\_isetup\_setup64.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\_isetup\_shfoldr.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\idp.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\innocallback.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\ISDone.dll
Show all 30 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\wintb.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\BASS.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\cls-lollypop.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\cls-lollypop_x64.exe - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\cls-lollypop_x86.exe - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\cls-srep_x64.exe - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\cls-srep_x86.exe - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\cls-magic2.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-6KCN0.tmp\cls-magic2_x64.exe - Deleted
C:\Games\Need for Speed - Payback\is-AJ4GE.tmp - Deleted
C:\Games\Need for Speed - Payback\_Redist\is-VF3DQ.tmp - Deleted
C:\Games\Need for Speed - Payback\_Redist\is-NCDO0.tmp - Deleted
C:\Games\Need for Speed - Payback\_Redist\is-NLNV8.tmp - Deleted
C:\Games\Need for Speed - Payback\_Redist\is-JI48O.tmp - Deleted
C:\Games\Need for Speed - Payback\is-LI7IE.tmp - Deleted
C:\Games\Need for Speed - Payback\is-KFT63.tmp - Deleted
C:\Games\Need for Speed - Payback\is-K1AOL.tmp - Deleted
C:\Games\Need for Speed - Payback\is-01U6P.tmp - Deleted
C:\Games\Need for Speed - Payback\_Redist\is-ODL3I.tmp - Deleted
C:\Games\Need for Speed - Payback\_Redist\is-FHS2O.tmp - Deleted
C:\Games\Need for Speed - Payback\is-DEDAV.tmp - Deleted
C:\Games\Need for Speed - Payback\is-KMJH8.tmp - Deleted
C:\Games\Need for Speed - Payback\_Redist\is-J4A2V.tmp - Deleted
C:\Games\Need for Speed - Payback\is-RQOMO.tmp
Mutexes
7Named locks a program uses so only one copy runs; malware families often reuse them.
Local\DirectSound DllMain mutex (0x0000137C)cversions.3.mLocal\Mutex9a4e57882f82f222.automaticDestinations-msStartMenuPinListMutexTaskbarPinListMutex\Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
Show all 7 entries for mutexes
\Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
Sandbox background — not the file
8The analysis machine's own processes and connections, recorded in every run.
- VM process
Explorer.EXEC:\Windows\Explorer.EXE - VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe
Show all 8 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 09af8004b85478e1eca0…47b449Not checkedno saved verdict
- f59eddcc9eaf545ead09…848dc5Not checkedno saved verdict
- 4a8157b2ff422c259dda…bad2d6Not checkedno saved verdict
- ef5a9ea2406e2898d4e0…b8e34aNot checkedno saved verdict
- e8f63e9b8f83e1502c24…8a54ebNot checkedno saved verdict
- d92f7c60256509f74e36…62ea29Not checkedno saved verdict
- 450b9b0ba25bf068afbc…fd0105Not checkedno saved verdict
- f84677643d9977aa1e8a…61f824Not checkedno saved verdict
- 148fa9a255bfff3f7d8a…9a3483Not checkedno saved verdict
- 19a5466ab1834f953662…6072f5Not checkedno saved verdict
Chapter 04
Technical details
4 of the 69 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.IVLRDN
- BkavW32.Malware.E1E06090
- MalwarebytesRiskWare.Crack
- Paloaltogeneric.ml
File fingerprint
- Last analyzed
- Sep 5, 2026, 8:48 PM UTC
- SHA-256
8d27c67549dac53d04b1f5cc4fc13beb4f706cc35051c23dec1e4c80fbcc5bd0- SHA-1
566f0d2922e0b61833cc9385901605e519b1ee99- MD5
cd739117fcc5e8dcd48db308f4a534b2
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
- Jun 5, 2026On VirusTotal.
- Submitted by
- 51 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Antivirus consensus
4 of 69 engines flagged this file
4 of the 73 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-235 engines1flagged
- Low-trust17 engines2flagged
View all 73 engine results
- BkavMalicious: W32.Malware.E1E06090
- GDataMalicious: Generic.Trojan.PSEB.IVLRDN
- 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
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GoogleClean
- GridinsoftClean
- huorongClean
- 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.