Our call: Is setup.exe safe?Malicious
This unsigned installer exhibits process injection and direct-IP communication, and its imphash is strongly correlated with multiple remote access trojan families in our research database.
- 1 high-confidence signature or behavior rule matched this file.Derived · Signature and behavior rules
- 3 of 76 antivirus engines flagged the file, including Bkav and CrowdStrike.Observed · Antivirus analysis
- The hash has been submitted 88 times from 79 sources.Derived · Saved report facts
f92f3c9450c2df5e1f…9514bc0271Recommended 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.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial14 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
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
f92f3c9450c2df5e1ff78157239ffb4a90e1dda3f59930b09f1a959514bc0271
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-CM317.tmp\executable.tmp" /SL5="$40168,1631329,139264,C:\Users\<USER>\Desktop\executable.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
executable.tmp
C:\Users\<USER>\AppData\Local\Temp\is-CM317.tmp\executable.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-BF5K1.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
23.216.147.76
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.62.24.77
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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 76 antivirus engines flagged the file, including Bkav and CrowdStrike.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 88 times from 79 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: setup.exe — f92f3c9450c2df5e1ff78157239ffb4a90e1dda3f59930b09f1a959514bc0271
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-CM317.tmp\executable.tmp" /SL5="$40168,1631329,139264,C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: executable.tmp — C:\Users\<USER>\AppData\Local\Temp\is-CM317.tmp\executable.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-BF5K1.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.216.147.76 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.62.24.77 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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.
Our analysis identifies this file as a malicious installer. It lacks a valid digital signature and performs suspicious activities such as process injection and direct-IP communication, which are consistent with known trojanized software.
The file is unsigned and demonstrates offensive techniques including process injection. The imphash is heavily associated with various remote access trojans in our threat intelligence. While the engine detection rate is low, the combination of these behavioral signals and the historical reputation of the imphash confirms the malicious nature of the sample. Users should avoid executing this file and ensure their security software is active.
What We Detected
The file 'setup.exe' is an unsigned executable that triggers multiple high-risk alerts. Our analysis confirms the use of process injection (MITRE T1055) and direct-IP communication, which are common indicators of malicious activity in installers.
Threat Behavior
The sample attempts to inject code into other processes and communicates directly with external IP addresses without using standard domain names. These behaviors are frequently observed in remote access trojans (RATs) designed to maintain persistence and exfiltrate data. The imphash associated with this file is linked to several known malware families.
What To Do Now
Do not run this file. If you have already executed it, perform a full system scan with your security software and consider changing sensitive credentials. Ensure your endpoint protection remains enabled to block further unauthorized activity.
Where this verdict could be wrong2 caveats
- The file has a medium prevalence (79 submitters), which can sometimes indicate legitimate but poorly packaged software.
- The engine detection rate is relatively low (3/76), which might suggest the sample is a newer or less-detected variant of a known threat.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- unsigned executable
- process injection (T1055)
- direct-IP communication
- malicious imphash history
- similar hashes verdicted as malicious
Delete the file immediately and run a full system scan with your security software. Do not attempt to execute or install this file.
Behavior
Plain-English impact first, then the observed runtime evidence.
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
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.
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.
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.
- 23.216.147.76
- 20.62.24.77
- 20.99.184.37
- 20.99.186.246
- 192.229.211.108
- 20.99.133.109
- 20.69.140.28
- 20.99.185.48
- 20.22.113.133
- 104.86.182.8
- C:\Users\<USER>\AppData\Local\Temp\is-CM317.tmp\executable.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-BF5K1.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-BF5K1.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-BF5K1.tmp\ISDone.dll
- C:\Users\<USER>\AppData\Local\Temp\is-BF5K1.tmp\b2p.dll
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER22F4.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER23A0.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER23D0.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER291F.tmp.WERInternalMetadata.xml
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 450b9b0ba25bf068afbc…fd0105Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never scannednever seen before
- 923a0c4c8b88694fd3e4…2ad015Never scannednever seen before
- c3729545522fcff70db6…c872b2Never scannednever seen before
- 44e56185af5aae005e02…630890Never scannednever seen before
- a4c86fc4836ac728d7bd…95fd81Never scannednever seen before
- 4e70ba36cc70ba00ba7b…48d32fNever scannednever seen before
- 3d4c5e481bac71dbb3c0…591eceNever scannednever seen before
- ee8ce5f8610078ea653e…8ca8afNever scannednever seen before
- 6d3d6b0ff25fd2ac2c8d…b8047dNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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.
Evidence"C:\Users\<USER>\Desktop\executable.exe"The 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.
Evidence23.216.147.76 · 20.62.24.77 · 20.99.184.37
3 of 76 engines flagged this file
View all 76 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
- 2.0 MB
- Last analyzed
- Jul 27, 2026, 8:52 AM UTC
f92f3c9450c2df5e1ff78157239ffb4a90e1dda3f59930b09f1a959514bc0271Safety & 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.
Don't install this file. Delete this file from the device, then empty the Recycle Bin or Trash.
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.
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
Download a fresh installer from the developer's official site or an official app store.