Is setup_we_happy_few_88966_(64bit)_(34773).exe safe?
No antivirus engine detected a threat, and the verified GOG signature, long-established prevalence, and matching installer history strongly support legitimate game software.
The file is signed with a verified GOG Sp. z o.o. certificate, and none of 74 antivirus engines flagged it. One sandbox recorded direct-IP traffic and T1134, but produced no malicious verdict or persistence; because host reputation was not checked, protection should remain enabled during installation.
59c38d1cde4c6cd0d9…8a25f2504e75a4Recommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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 file is signed with a verified GOG Sp. z o.o. certificate, and none of 74 antivirus engines flagged it. One sandbox recorded direct-IP traffic and T1134, but produced no malicious verdict or persistence; because host reputation was not checked, protection should remain enabled during installation.
None of 74 antivirus engines reported a detection, including all 17 participating tier-1 engines. The executable has a verified GOG Sp. z o.o. signature and has circulated broadly for more than six years. A signer-matched installer with the same imphash also received a prior clean assessment, while unrelated imphash matches were given little weight. The completed sandbox run produced no malicious verdict or persistence, though it observed T1134 and several direct-IP contacts. Those hosts were not reputation-checked, so the network evidence remains an unresolved limitation rather than proof of benign traffic. Overall, the established distribution, verified publisher identity, and complete absence of engine detections outweigh the isolated behavioral concerns.
What We Detected
None of 74 antivirus engines flagged the executable, and all 17 participating tier-1 engines reported no detection. The file carries a verified signature from GOG Sp. z o.o. and has been submitted 112 times by 104 sources over more than six years. A prior installer sharing both the imphash and GOG signer was also assessed as clean.
Threat Behavior
One completed sandbox run recorded the T1134 technique and connections to several external IP addresses without associated application domains. It did not produce a malicious sandbox verdict, persistence indicators, or a known malicious dropped child. The contacted hosts were not checked against the reputation cache, and all three inspected child files lack individual verdicts, so those areas remain incompletely resolved.
What To Do Now
Use the installer only if it came from GOG or another trusted purchase library, and verify that Windows still reports GOG Sp. z o.o. as the valid signer. Keep antivirus and endpoint protection enabled during installation, particularly if the file came from a mirror or file-sharing service.
Where this verdict could be wrong4 caveats
- MalwareTips.Synth.DirectIpC2 fired after six external IP contacts without an application domain, but contactedHosts=null leaves their reputation unverified.
- T1134 was observed in the sandbox; it can indicate token manipulation, although no malicious sandbox verdict or persistence accompanied it.
- All three dropped children have unknown individual verdicts despite droppedChildren.hasMaliciousChild=false.
- signing.signerStats.totalSamples=1 provides only limited historical support for the GOG certificate.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/74 antivirus engines reported a detection.
- 17 tier-1 engines reported no detection.
- Verified digital signature from GOG Sp. z o.o.
- Observed across 104 sources and 112 submissions over 2444 days.
- A signer-co-matched similar installer previously received a safe assessment.
- Sandbox observed T1134, a technique that can be associated with access-token manipulation.
- Six external IP contacts triggered MalwareTips.Synth.DirectIpC2.
- contactedHosts=null, so no complete reputation result is available for observed network contacts.
- Three dropped child files were inspected but retain unknown individual verdicts.
- Signer history contains only one prior sample.
Prefer a fresh copy downloaded directly through GOG and confirm the GOG Sp. z o.o. signature before running it. Keep endpoint protection enabled and avoid copies obtained from untrusted mirrors.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial7 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 13MITRE ATT&CK techniques
- 15spawned processes
- 7network contacts
- 33filesystem & mutex artifacts
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_we_happy_few_88966_(64bit)_(34773).exe
59c38d1cde4c6cd0d9dcb8cac800095966c9945cdd47fcb6578a25f2504e75a4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\59c38d1cde4c6cd0d9dcb8cac800095966c9945cdd47fcb6578a25f2504e75a4.exe
02Isolated runtime analysis - ProcessObserved
Observed process
%USERPROFILE%\AppData\Local\Temp\is-5P13E.tmp\59c38d1cde4c6cd0d9dcb8cac800095966c9945cdd47fcb6578a25f2504e75a4.tmp
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
996E.tmp
C:\Documents and Settings\Administrator\Local Settings\Temp\is-EBAIJ.tmp\996E.tmp
04Isolated runtime analysis - Written fileObserved
Setup Log 2020-01-12 #001.txt
C:\Documents and Settings\Administrator\Local Settings\Temp\Setup Log 2020-01-12 #001.txt
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:0:0:100:0:1800:0
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.186.246
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.
- a83f:8110:0:0:100:0:1800:0
- 20.99.186.246
- 192.229.211.108
- 20.99.133.109
- 104.112.185.183
- 192.168.0.29
- 23.55.140.42
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-EBAIJ.tmp\996E.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\Setup Log 2020-01-12 #001.txt
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-8QMI0.tmp\996E.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\Setup Log 2020-01-19 #001.txt
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-FMV2P.tmp\996E.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER26EC.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER27F5.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2825.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER341C.tmp.WERInternalMetadata.xml
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- oleacc-msaa-loaded
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- a3fbeee9b84b8387d43c…f23b50Never scannednever seen before
- c25cd627baf58b030895…56b837Never scannednever seen before
- 388a796580234efc95f3…136f95Never 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.
- 1rule hit recorded
- 0 / 74engines flagged
- 104sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 104 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from GOG Sp. z o.o..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: setup_we_happy_few_88966_(64bit)_(34773).exe — 59c38d1cde4c6cd0d9dcb8cac800095966c9945cdd47fcb6578a25f2504e75a4
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\59c38d1cde4c6cd0d9dcb8cac800095966c9945cdd47fcb6578a25f2504e75a4.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %USERPROFILE%\AppData\Local\Temp\is-5P13E.tmp\59c38d1cde4c6cd0d9dcb8cac800095966c9945cdd47fcb6578a25f2504e75a4.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 996E.tmp — C:\Documents and Settings\Administrator\Local Settings\Temp\is-EBAIJ.tmp\996E.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Setup Log 2020-01-12 #001.txt — C:\Documents and Settings\Administrator\Local Settings\Temp\Setup Log 2020-01-12 #001.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:0:0:100:0:1800:0 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.99.186.246 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidencea83f:8110:0:0:100:0:1800:0 · 20.99.186.246 · 192.229.211.108
0 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_we_happy_few_88966_(64bit)_(34773).exe
- Format
- Win32 EXE
- Code signing
- Signature valid: GOG Sp. z o.o.
- Size
- 946.3 KB
- Last analyzed
- Sep 19, 2026, 9:16 PM UTC
59c38d1cde4c6cd0d9dcb8cac800095966c9945cdd47fcb6578a25f2504e75a4Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Install it only when it came from the developer's official site or an official app store.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is setup_we_happy_few_88966_(64bit)_(34773).exe safe?
What is setup_we_happy_few_88966_(64bit)_(34773).exe?
How many antivirus engines detected setup_we_happy_few_88966_(64bit)_(34773).exe?
Is setup_we_happy_few_88966_(64bit)_(34773).exe digitally signed?
What is the SHA-256 hash of setup_we_happy_few_88966_(64bit)_(34773).exe?
Is it safe to install setup_we_happy_few_88966_(64bit)_(34773).exe?
How up to date is this analysis of setup_we_happy_few_88966_(64bit)_(34773).exe?
Community
Member reviews and reports for this exact file hash.