Is setup.exe safe?
GData tier-1 detection of PSEB family, corroborated by RAG consensus, process injection, direct-IP C2, and YARA hits.
GData (tier-1) identifies this as PSEB-family malware. Two prior samples with the same imphash were verdicted malicious. The file exhibits process injection, direct-IP C2 communication, and contacted a known warez site. Community YARA rules converge on malicious patterns.
16c82723b441f048a7…8954ab90b343daRecommended 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.
GData (tier-1) identifies this as PSEB-family malware. Two prior samples with the same imphash were verdicted malicious. The file exhibits process injection, direct-IP C2 communication, and contacted a known warez site. Community YARA rules converge on malicious patterns.
The sample shows convergent malicious signals: GData tier-1 engine names PSEB family; RAG shows 2/3 prior imphash-matched samples verdicted malicious with the same family; behaviour analysis flags T1055 process injection and direct-IP C2 (15 IPs, no DNS) as high-severity indicators; yaraify matched 3 community YARA rules; contacted hosts include fitgirl-repacks.site (suspicious, warez distribution); reputation is negative; file is unsigned with no signer history. While only one tier-1 engine flagged it, the structural match (imphash), family consensus across RAG, and offensive behaviour patterns (injection + C2) establish malware classification.
What We Detected
GData (tier-1 antivirus) flagged this file as 'Generic.Trojan.PSEB.X0G340', naming the PSEB malware family. Our historical analysis (RAG) shows two prior samples with the same imphash (483f0c4259a9148c34961abbda6146c1) were verdicted malicious and attributed to PSEB. Community YARA rules (Borland, pe_detect_tls_callbacks, shellcode) matched, indicating researcher consensus on malicious patterns.
Threat Behavior
Sandbox analysis revealed process injection (T1055 — CreateRemoteThread/APC) to smuggle payload into legitimate processes and bypass antivirus hooks. The sample contacted 15 external IP addresses directly, with zero DNS domain lookups — a strong indicator of C2 communication designed to evade domain-based blocklists. The file also contacted fitgirl-repacks.site, a known warez/crack distribution platform. Temporary files were extracted and executed, consistent with installer-based malware deployment. The file is unsigned, has negative reputation (-9), and carries tags including 'overlay', 'detect-debug-environment', and 'hosts-modifier' — all adversarial indicators.
What To Do Now
Do not execute this file. Remove it from your system if present. If you downloaded it, assume your system may be compromised; run a full antivirus scan and consider credential reset if the file was executed. The PSEB family is known for information theft and system manipulation; monitor for suspicious network activity and unauthorized process execution.
Where this verdict could be wrong3 caveats
- Only 1 tier-1 engine flagged malicious (GData); 16 tier-1 engines reported clean. If GData's heuristic is overly aggressive, this could be a false positive — however, the RAG consensus (2/3 prior imphash matches verdicted malicious) and yaraify hits (3 rules) strongly counter this scenario.
- No malicious sandbox verdict recorded in behaviour.sandboxVerdicts — but the process chain and file-write patterns (temp extraction, DLL drops, process injection) are consistent with malware execution; absence of a recorded verdict may reflect sandbox analysis gaps rather than benign behaviour.
- Malwarebytes labels it 'RiskWare.Crack' (tier-2, adwarePua=true) — 'crack' tools are often PUA rather than malware. However, the combination of process injection + direct-IP C2 + PSEB family naming elevates this beyond typical PUA; it exhibits active C2 and evasion tactics.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No malicious dropped children (10 inspected, 0 malicious)
- No malicious sandbox verdict recorded (though process chain is suspicious)
- Process injection (T1055) to bypass security hooks
- Direct-IP C2 communication (15 external IPs, no DNS)
- Contact with known warez distribution site (fitgirl-repacks.site)
- Unsigned executable with negative reputation
- PSEB malware family identified by tier-1 engine
- Community YARA rules converged on malicious patterns
Block and quarantine this file immediately. The convergence of tier-1 detection, RAG consensus, process injection, C2 communication, and warez-site contact establishes malware classification. Do not execute or allow execution on any system.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 23 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete5 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
- 29MITRE ATT&CK techniques
- 15spawned processes
- 23network contacts
- 40filesystem & 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.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
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.
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
16c82723b441f048a70938670cbd7b8e59429e3c62066db7788954ab90b343da
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-A3ASQ.tmp\executable.tmp" /SL5="$D0028,3979188,140800,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-A3ASQ.tmp\executable.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-AH377.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
fitgirl-repacks.site
Saved reputation verdict: suspicious.
06Contacted-host cross-check - Contacted hostObserved
23.216.147.76
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.
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
- 192.229.211.108
- 20.99.185.48
- 20.99.133.109
- 20.99.184.37
- 23.216.147.64
- 20.99.186.246
- a83f:8110:900:3000:3000:3000:6100:3000
- a83f:8110:201:3ff:202:2ff:202:2ff
- 184.25.191.235
- http://bit.ly/fitgirl-repacks-site
- http://fitgirl-repacks.site/
- http://r3.i.lencr.org/
- C:\Users\<USER>\AppData\Local\Temp\is-A3ASQ.tmp\executable.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-AH377.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-AH377.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-AH377.tmp\idp.dll
- C:\Users\<USER>\AppData\Local\Temp\is-AH377.tmp\innocallback.dll
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB19.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERFBF4.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC23.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER170D.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER174E.tmp.csv
- Local\DirectSound DllMain mutex (0x00001A10)
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- \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 10 children at runtime. None are currently flagged malicious in our cache.
- 09af8004b85478e1eca0…47b449Never scannednever seen before
- d92f7c60256509f74e36…62ea29Never scannednever seen before
- 58045dfbe8eb137de53d…94d65dNever scannednever seen before
- 450b9b0ba25bf068afbc…fd0105Never scannednever seen before
- f84677643d9977aa1e8a…61f824Never scannednever seen before
- 19a5466ab1834f953662…6072f5Never scannednever seen before
- ed8a485b9984997306ea…c78ee9Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never scannednever seen before
- b5918c0eac32ea3fcb3a…3b1c7aNever scannednever seen before
- fbbf18f351711497ef2c…43fa39Never scannednever seen before
Servers this file contacts
This file contacts 1 host we've flagged suspicious in our own URL scanner.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 5rule hits recorded
- 3 / 74engines flagged
- 1,542sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 74 antivirus engines flagged the file, including GData and Malwarebytes.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 1,542 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: setup.exe — 16c82723b441f048a70938670cbd7b8e59429e3c62066db7788954ab90b343da
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-A3ASQ.tmp\executable.tmp" /SL5="$D0028,3979188,140800,C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: executable.tmp — C:\Users\<USER>\AppData\Local\Temp\is-A3ASQ.tmp\executable.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-AH377.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: fitgirl-repacks.site — Saved reputation verdict: suspicious.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: 23.216.147.76 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched 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.
- Borland
- pe_detect_tls_callbacks
- shellcode
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
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 · 192.229.211.108 · 20.99.185.48
3 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 4.3 MB
- Last analyzed
- Jun 25, 2026, 2:41 PM UTC
16c82723b441f048a70938670cbd7b8e59429e3c62066db7788954ab90b343daSafety & 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
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- 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.