Is setup.exe safe?
Six high-trust engines flagged this unsigned installer, with three independently agreeing on Yomal and runtime evidence indicating possible process manipulation.
The strongest evidence is agreement among three high-trust engines on the Yomal trojan family, within 24 detections across 74 engines. The unsigned executable also exhibited techniques mapped to process injection and token manipulation, while no complete reputation check is available for its observed IP contact.
0ecf9fcd79f064dd72…2fea8db35db2abRecommended next actions
Before installing
Do not install it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already installed it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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 strongest evidence is agreement among three high-trust engines on the Yomal trojan family, within 24 detections across 74 engines. The unsigned executable also exhibited techniques mapped to process injection and token manipulation, while no complete reputation check is available for its observed IP contact.
Twenty-four of 74 engines detected the executable, including six high-trust detections. Microsoft, Ikarus, and TrendMicro independently converge on the Yomal family, producing strong family consensus rather than an isolated generic alert. One sandbox run mapped activity to T1055 process injection and T1134 access-token manipulation, which reinforces the engine findings but does not establish the exact implementation. The executable is unsigned and has no publisher history to offset those signals. Some major engines remained silent, no sandbox issued an explicit malicious verdict, and researcher-curated sources returned no match, but these counter-signals do not outweigh the high-trust family consensus.
What We Detected
Twenty-four of 74 antivirus engines flagged setup.exe. Six detections came from high-trust engines, and Microsoft, Ikarus, and TrendMicro independently named the Yomal trojan family. This three-engine family agreement is substantially stronger than a collection of unrelated generic heuristic alerts.
Threat Behavior
A completed sandbox run mapped activity to T1055 (Process Injection) and T1134 (Access Token Manipulation), both associated with potentially hostile process manipulation. The sample also contacted 162.159.36.2, but the host-reputation cross-check was not completed or retained, so the contact cannot be characterized as benign or malicious. No persistence indicator or explicit malicious sandbox verdict was recorded, and nine dropped files remain without conclusive child verdicts.
What To Do Now
Do not run the installer. Quarantine or remove it while keeping endpoint protection enabled, and obtain the intended software again from its publisher's official download channel. If it already ran, perform a full system scan and review active processes, accounts, and recent security alerts for signs of process manipulation.
Where this verdict could be wrong5 caveats
- Ten tier-1 engines did not detect the file, including Avast, AVG, Avira, BitDefender, and DrWeb.
- behaviour.hasMaliciousSandboxVerdict=false, and no persistence indicators were recorded in the single completed sandbox run.
- droppedChildren inspected 9 files without a confirmed malicious child, although all nine child verdicts remain unknown.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false, so researcher-curated sources did not independently corroborate the family.
- The sample is relatively prevalent, with prevalence.uniqueSources=689 and prevalence.timesSubmitted=756.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Ten tier-1 engines did not detect the sample
- No explicit malicious sandbox verdict was recorded
- No persistence indicators were observed
- No confirmed malicious dropped child was found
- No CIRCL or YARAify match was returned
- 24/74 antivirus detections
- Six high-trust engine detections
- Strong three-engine Yomal family consensus
- Unsigned Windows executable
- Runtime mapping to T1055 process injection
- Runtime mapping to T1134 access-token manipulation
Quarantine or delete this installer and keep endpoint protection enabled. If it has already executed, run a full scan and replace it only with a copy obtained directly from the official publisher.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete24 of 74 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
- 19MITRE ATT&CK techniques
- 3spawned processes
- 1network contacts
- 22filesystem & 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: Decoded or unpacked concealed content while running.
Note: Listed running processes; both legitimate software and malware may do this.
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.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
0ecf9fcd79f064dd72f8cc5437346694e2265d7dee822c30332fea8db35db2ab
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Users\<USER>\AppData\Local\Temp\is-I2549.tmp\setup.tmp /SL5=$110116,5814546,153088,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-I2549.tmp\setup.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-PRFL4.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
- C:\Users\<USER>\AppData\Local\Temp\is-I2549.tmp\setup.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-PRFL4.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-PRFL4.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-PRFL4.tmp\VclStylesInno.dll
- C:\Users\user\AppData\Local\Temp\is-FQVTM.tmp\5eaeab3e1d0e58f6d4a7c16e41220252.tmp
- Local\MSCTF.Asm.MutexDefault1
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- WSjuQKBxmd_mut
- DefaultTabtip-MainUI
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- e153bde25d0a3f8180ac…f71600Never scannednever seen before
- a4c86fc4836ac728d7bd…95fd81Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never scannednever seen before
- c2debfb2a38bc839365f…94b721Never scannednever seen before
- dacdf8f9b8b1ab51a83a…26a11eNever scannednever seen before
- 88160915cd065e25bc0b…8d4f16Never scannednever seen before
- a8d979460e970e84eacc…81b021Never scannednever seen before
- b9bdc4a0309aa47613a7…1dbe9dNever scannednever seen before
- 65a7e7fb213007ba2e28…c87bc0Never 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
- 24 / 74engines flagged
- 689sources 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
24 of 74 antivirus engines flagged the file, including alibabacloud and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 756 times from 689 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: setup.exe — 0ecf9fcd79f064dd72f8cc5437346694e2265d7dee822c30332fea8db35db2ab
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Users\<USER>\AppData\Local\Temp\is-I2549.tmp\setup.tmp /SL5=$110116,5814546,153088,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-I2549.tmp\setup.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-PRFL4.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: generic-trojan
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-I2549.tmp\setup.tmp /SL5=$110116,5814546,153088,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
24 of 74 engines flagged this file
View all 74 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 6.1 MB
- Last analyzed
- Sep 19, 2026, 9:00 AM UTC
0ecf9fcd79f064dd72f8cc5437346694e2265d7dee822c30332fea8db35db2abSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't install this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already installed it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Download a fresh installer from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.