Is setup.exe safe?
Three of 75 engines flagged this unsigned installer, while process-injection indicators and an unchecked direct-IP contact warrant caution despite weak detection consensus.
The unsigned installer received three detections among 75 engines, including one tier-1 generic-trojan result and a crack-related riskware label. One sandbox run mapped activity to T1055 and T1134, but produced no malicious verdict; the observed IP contact also lacks a completed reputation check.
e47a38d7c7283dd2a0…18f8d8835afd0dRecommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The unsigned installer received three detections among 75 engines, including one tier-1 generic-trojan result and a crack-related riskware label. One sandbox run mapped activity to T1055 and T1134, but produced no malicious verdict; the observed IP contact also lacks a completed reputation check.
Detection consensus is limited because only 3 of 75 engines flagged the file and just one tier-1 engine supplied the PSEB label. The crack-related Malwarebytes detection supports possible unwanted or unauthorized software, but confirmed hacktool criteria were not met. One completed sandbox run recorded T1055 and T1134, which raises concern even though its saved verdict was clean and no persistence was observed. The executable is unsigned and has no publisher history, weakening confidence in its origin. Six dropped files had no malicious finding, but their individual verdicts remain unknown, and no complete host-reputation result is available for the direct-IP contact.
What We Detected
Three of 75 engines flagged the executable. GData reported Generic.Trojan.PSEB.4OC8AM, Malwarebytes reported RiskWare.Crack, and Paloalto reported generic.ml; however, only one tier-1 engine flagged it and there is no strong family consensus. The executable is unsigned and has no established signer history.
Threat Behavior
One completed sandbox run mapped activity to T1055 and T1134, techniques associated with process injection and access-token manipulation. The run itself did not produce a malicious sandbox verdict and recorded no persistence indicators. The file contacted 162.159.36.2 directly, but contactedHosts=null means no complete reputation result is available for that address. Six dropped files were inspected without a malicious child finding, although all six individual child verdicts remain unknown.
What To Do Now
Do not run this installer on a production or personal system unless its source and expected publisher can be independently verified. Keep endpoint protection enabled, obtain the software through an official release channel, and quarantine or remove this copy if its origin cannot be confirmed.
Where this verdict could be wrong4 caveats
- Only 3/75 engines flagged the sample, while 16/17 tier-1 engines did not; the sole tier-1 family vote for PSEB is not consensus.
- behaviour.hasMaliciousSandboxVerdict=false, no persistence indicators were recorded, and droppedChildren.hasMaliciousChild=false.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false, although absence of hits does not establish benignity.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false provide no static packing signal.
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 3/75 engines flagged the sample
- 16/17 tier-1 engines did not flag it
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- peAnalysis.likelyPacked=false
- Unsigned Win32 installer with no signer history
- GData tier-1 Generic.Trojan.PSEB detection
- Malwarebytes RiskWare.Crack detection
- Runtime evidence mapped to T1055 process injection
- Runtime evidence mapped to T1134 access-token manipulation
- Direct-IP contact lacks a completed reputation check
Avoid executing this copy until its source and publisher are independently verified against an official release. Keep security software enabled and quarantine the file if that verification is unavailable.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 15MITRE ATT&CK techniques
- 3spawned processes
- 1network contacts
- 17filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
setup.exe
e47a38d7c7283dd2a0b05ad7548695b4e346d27026f269c5df18f8d8835afd0d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Users\<USER>\AppData\Local\Temp\is-667JL.tmp\setup.tmp /SL5=$110158,5738693,140800,C:\Users\<USER>\Downloads\setup.exe
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\setup.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-667JL.tmp\setup.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-PUP89.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 162.159.36.2
- Software\Microsoft\RestartManager\Session0000\Owner
- Software\Microsoft\RestartManager\Session0000\Sequence
- HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
- HKEY_CURRENT_USER\Software\Microsoft\RestartManager
- HKEY_CURRENT_USER\Software\Microsoft\RestartManager\Session0000
- C:\Users\<USER>\AppData\Local\Temp\is-667JL.tmp\setup.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-PUP89.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-PUP89.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-PUP89.tmp\idp.dll
- C:\Users\<USER>\AppData\Local\Temp\is-PUP89.tmp\innocallback.dll
- \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.
- a4c86fc4836ac728d7bd…95fd81Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never scannednever seen before
- f4fc0187491a9cb89e23…bc44bbNever scannednever seen before
- 6afa2d104be6efe3d9a2…29809fNever scannednever seen before
- c652b4b564b3c85c3991…412c74Never scannednever seen before
- 09af8004b85478e1eca0…47b449Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 3 / 75engines flagged
- 295sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 75 antivirus engines flagged the file, including GData and Malwarebytes.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 331 times from 295 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: setup.exe — e47a38d7c7283dd2a0b05ad7548695b4e346d27026f269c5df18f8d8835afd0d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Users\<USER>\AppData\Local\Temp\is-667JL.tmp\setup.tmp /SL5=$110158,5738693,140800,C:\Users\<USER>\Downloads\setup.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: setup.tmp — C:\Users\<USER>\AppData\Local\Temp\is-667JL.tmp\setup.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-PUP89.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Users\<USER>\AppData\Local\Temp\is-667JL.tmp\setup.tmp /SL5=$110158,5738693,140800,C:\Users\<USER>\Downloads\setup.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
3 of 75 engines flagged this file
View all 75 engine results
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.
Fingerprint and provenance
- File name
- setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 6.1 MB
- Last analyzed
- Oct 3, 2026, 3:36 AM UTC
e47a38d7c7283dd2a0b05ad7548695b4e346d27026f269c5df18f8d8835afd0dSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't install it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Download a fresh installer from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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?
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.