Our call: Is setup.exe safe?Malicious
Unsigned installer flagged by tier-1 engine for PSEB family; sandbox observed process injection, credential dumping, and direct-IP C2 contact.
- 1 high-confidence signature or behavior rule matched this file.Derived · Signature and behavior rules
- 4 of 75 antivirus engines flagged the file, including Bkav and GData.Observed · Antivirus analysis
- The hash has been submitted 92 times from 76 sources.Derived · Saved report facts
9b7c34eefa6dc1db16…12931d6edfRecommended 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
Complete4 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 3 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 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
9b7c34eefa6dc1db16cd458326e532ddc393ef86c4dd09d41ea2b912931d6edf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-6IOSJ.tmp\setup.tmp" /SL5="$501A6,8320176,140800,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-6IOSJ.tmp\setup.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-BVSDD.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
184.28.3.247
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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
4 of 75 antivirus engines flagged the file, including Bkav and GData.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 92 times from 76 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: setup.exe — 9b7c34eefa6dc1db16cd458326e532ddc393ef86c4dd09d41ea2b912931d6edf
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-6IOSJ.tmp\setup.tmp" /SL5="$501A6,8320176,140800,C:\Users\<USER>\Desktop\setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: setup.tmp — C:\Users\<USER>\AppData\Local\Temp\is-6IOSJ.tmp\setup.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-BVSDD.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 184.28.3.247 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — 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.
GData (tier-1) identifies this as PSEB malware. Sandbox analysis detected process injection into Explorer.exe, LSASS credential dumping (Mimikatz-like behaviour), and direct-IP C2 communication bypassing DNS reputation systems. Malwarebytes flags it as cracking tooling. The combination of named family detection and offensive MITRE techniques (T1055, T1134, T1485, T1548) indicates malicious intent.
This unsigned setup.exe is flagged by GData (tier-1) as Generic.Trojan.PSEB.WTN8JB, establishing a named family detection with tier-1 authority. While only 1 of 17 tier-1 engines flagged it malicious, the remaining tier-1 engines' silence does not contradict the detection — they may lack PSEB signatures. The sandbox behaviour is unambiguous: process injection into Explorer.exe (T1055), credential dumping from LSASS (Mimikatz-shape), and direct-IP C2 to two external IPs with zero DNS queries. These are not installer false positives; they are offensive techniques used by malware to evade detection and steal credentials. Malwarebytes' 'RiskWare.Crack' label suggests cracking/keygen tooling, which is classified as malware under most policies. The file's medium prevalence (92 submissions) and lack of external intel hits do not override the tier-1 family detection and sandbox-observed offensive behaviour.
What We Detected
GData (tier-1 antivirus) identified this file as Generic.Trojan.PSEB.WTN8JB, a named malware family. Malwarebytes flagged it as RiskWare.Crack, indicating cracking or keygen tooling. Three additional engines (Bkav, Paloalto) reported generic malware signatures. The file is unsigned and has no publisher history.
Threat Behavior
Sandbox analysis revealed four offensive MITRE techniques:
- T1055 (Process Injection): The sample injected code into Explorer.exe using CreateRemoteThread or reflective-DLL techniques, a classic evasion method to hide malicious activity inside a legitimate process.
- T1134 (Process Hollowing): Process memory was manipulated to execute injected code.
- T1485 (Data Destruction): Destructive operations were observed, consistent with ransomware or wiper behaviour.
- T1548 (Privilege Escalation): The sample attempted to elevate privileges.
- Credential Dumping: The sample targeted LSASS (Windows credential store), mimicking Mimikatz behaviour to extract cached credentials.
- Direct-IP C2: The sample contacted two external IP addresses (184.28.3.247, 162.159.36.2) directly, bypassing DNS reputation systems and domain-based blocklists — a strong indicator of malware command-and-control.
The file dropped 10 child processes (all currently unknown verdict) and wrote temporary files to the system temp directory, consistent with installer unpacking but paired with the offensive techniques above.
What To Do Now
Do not execute this file. If already run, assume credential compromise and change passwords for all accounts used on that system. Scan the system with a full antivirus suite and consider professional incident response if the file was executed with administrative privileges. The PSEB family and cracking tooling classification indicate this is not legitimate software.
Where this verdict could be wrong4 caveats
- Only 1 tier-1 engine (GData) flagged malicious; 11 tier-1 engines silent — could indicate false positive if PSEB family is misclassified. However, the combination of process injection + credential dumping + direct-IP C2 is not a typical false-positive signature.
- Malwarebytes' 'RiskWare.Crack' label suggests cracking/keygen rather than malware proper — but cracking tools are classified as PUA/malware in most policies and the offensive MITRE techniques (T1055, T1485) exceed typical keygen behaviour.
- Dropped children are all unknown verdict, not malicious — but the parent's own offensive behaviour is sufficient to classify without relying on child verdicts.
- No external intel hits (CIRCL, YARAify) — could reflect rule-coverage gaps or genuine absence of researcher corroboration, but does not override the sandbox-observed offensive techniques.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Contacted URLs are legitimate Microsoft Visual C++ redistributable endpoints (aka.ms/vs/17/release/vc_redist.*)
- Dropped children (10 inspected) show no malicious verdicts in our cache
- No malicious or suspicious hosts in our URL cache cross-reference
- No external intel hits (CIRCL, YARAify) — though absence of researcher corroboration does not override tier-1 detection
- Tier-1 engine (GData) identifies named malware family PSEB
- Process injection into legitimate process (Explorer.exe) to evade detection
- LSASS credential dumping (Mimikatz-like behaviour) — credential theft risk
- Direct-IP C2 communication bypassing DNS reputation systems
- Privilege escalation attempt (T1548)
- Data destruction techniques observed (T1485)
Block and quarantine this file immediately. The tier-1 family detection (PSEB) combined with sandbox-observed process injection, credential dumping, and direct-IP C2 communication confirms malicious intent. If executed, assume credential compromise and initiate incident response.
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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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.
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.
- 184.28.3.247
- 162.159.36.2
- https://aka.ms/vs/17/release/vc_redist.x64.exe
- https://aka.ms/vs/17/release/vc_redist.x86.exe
- C:\Users\<USER>\AppData\Local\Temp\is-6IOSJ.tmp\setup.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-BVSDD.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-BVSDD.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-BVSDD.tmp\idp.dll
- C:\Users\<USER>\AppData\Local\Temp\is-BVSDD.tmp\innocallback.dll
- C:\Games\Jurassic World Evolution 3\is-GRJG5.tmp
- C:\Games\Jurassic World Evolution 3\_Redist\is-4C8R9.tmp
- C:\Games\Jurassic World Evolution 3\_Redist\is-13551.tmp
- C:\Games\Jurassic World Evolution 3\is-01IH4.tmp
- C:\Games\Jurassic World Evolution 3\is-MOSLR.tmp
- Local\DirectSound DllMain mutex (0x00000E5C)
- cversions.3.m
- Local\Mutex238415d2de6d946f.automaticDestinations-ms
- StartMenuPinListMutex
- TaskbarPinListMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 09af8004b85478e1eca0…47b449Never scannednever seen before
- f59eddcc9eaf545ead09…848dc5Never scannednever seen before
- 493ed2a17bb27ae6a0f2…b6a661Never scannednever seen before
- d92f7c60256509f74e36…62ea29Never scannednever seen before
- 58045dfbe8eb137de53d…94d65dNever scannednever seen before
- 450b9b0ba25bf068afbc…fd0105Never scannednever seen before
- f84677643d9977aa1e8a…61f824Never scannednever seen before
- 5491e20f601185a8bdb6…5c4b10Never scannednever seen before
- aa6b7213ecf2e90913af…985eefNever scannednever seen before
- 148fa9a255bfff3f7d8a…9a3483Never 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.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.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.
Evidence184.28.3.247 · 162.159.36.2
4 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
- 8.5 MB
- Last analyzed
- Jun 11, 2026, 11:16 AM UTC
9b7c34eefa6dc1db16cd458326e532ddc393ef86c4dd09d41ea2b912931d6edfSafety & 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.
If you typed any passwords while it was open, change them from a device you trust.
Download a fresh installer from the developer's official site or an official app store.