Is Step 3 - Setup_Install_Game.exe safe?
Fifty of 75 engines flagged this unsigned installer, while runtime evidence recorded process injection, PowerShell execution, defense impairment, and service-related persistence.
The unsigned executable drew detections from 50 of 75 engines, including 11 high-trust engines such as BitDefender, Kaspersky, Microsoft, ESET, and Sophos. Runtime evidence also mapped six offensive techniques, including process injection and defense impairment, making accidental heuristic detection highly unlikely.
7cc9e17085066cd229…43d112c27bf486Recommended 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 unsigned executable drew detections from 50 of 75 engines, including 11 high-trust engines such as BitDefender, Kaspersky, Microsoft, ESET, and Sophos. Runtime evidence also mapped six offensive techniques, including process injection and defense impairment, making accidental heuristic detection highly unlikely.
Detections are broad and independent: 50 of 75 engines flagged the sample, with 11 high-trust engines participating. Most labels describe a trojan, though miner, ransomware, and other family names conflict, so the evidence supports a generic trojan assessment rather than a precise family. One completed sandbox recorded T1055 process injection, T1059.001 PowerShell, T1490 recovery inhibition, T1543.003 service activity, T1562.001 defense impairment, and T1571 non-standard protocol use. The executable is unsigned and has a reputation score of -59, offering no publisher-based explanation for the detections. No complete reputation check is available for the contacted IP addresses because the host cross-reference result was not saved.
What We Detected
Fifty of 75 antivirus engines flagged the executable, including 11 high-trust engines. BitDefender and GData identified Trojan.GenericKD.49023651, Microsoft reported Tenga, Kaspersky reported a VBS Agent trojan, and several others used generic trojan labels. The disagreement over exact names means a specific family cannot be assigned reliably, but the overall malware signal is exceptionally strong.
Threat Behavior
A completed sandbox run mapped six offensive techniques: T1055 process injection, T1059.001 PowerShell, T1490 recovery inhibition, T1543.003 Windows service activity, T1562.001 defense impairment, and T1571 non-standard protocol use. The sample also wrote scripts, registry-import material, executables, and an MSI package under user-writable locations. Direct IP contacts were observed, but no complete host-reputation result is available, so those destinations cannot be characterized conclusively.
What To Do Now
Do not run the file. Quarantine or delete it while keeping endpoint protection enabled; if it was already executed, disconnect the affected computer from the network and perform a full security scan, then review services, scheduled startup points, and user-writable update folders for persistence.
Where this verdict could be wrong4 caveats
- engines.tier1FamilyConsensus.strong=false, and the engine labels disagree between generic trojan, miner, ransomware, and other names, so no precise family attribution is justified.
- behaviour.hasMaliciousSandboxVerdict=false, although the completed sandbox still recorded six offensive techniques.
- droppedChildren inspected 10 children without a confirmed malicious child, but all 10 child verdicts are unknown rather than benign.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false; these absences may reflect coverage gaps and do not outweigh 50/75 detections.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- droppedChildren.hasMaliciousChild=false, although all 10 child verdicts remain unknown
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false
- externalIntel.yaraify.ruleCount=0
- brandMismatch.detected is not present
- 50/75 antivirus detections
- 11 high-trust engine detections
- Unsigned Win32 executable
- T1055 process-injection evidence
- T1562.001 defense-impairment evidence
- T1490 recovery-inhibition evidence
Quarantine or remove the executable and keep all endpoint protection enabled. If it ran, isolate the system, perform full scans, and investigate persistence or unauthorized resource usage.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete50 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 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.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 29MITRE ATT&CK techniques
- 15spawned processes
- 20network 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: Used removable-media replication behaviour that can spread files between devices.
High concern: Attempted to remove recovery data such as backups or shadow copies.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
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
Step 3 - Setup_Install_Game.exe
7cc9e17085066cd2299e7c37c743acbad0370554ec704c803443d112c27bf486
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
<PATH_SAMPLE.EXE>
02Isolated runtime analysis - ProcessObserved
Observed process
<SYSTEM32>\msiexec.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
decoder.dll
%APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\decoder.dll
04Isolated runtime analysis - Written fileObserved
oceanofgames-top-games-exe.msi
%APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\326fa02\oceanofgames-top-games-exe.msi
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.132.105
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.
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.
- 20.99.132.105
- 20.62.24.77
- 23.216.147.76
- a83f:8110:0:0:100:0:1800:0
- a83f:8110:0:0:5c00:0:60cf:15ba
- a83f:8110:acb3:d201:0:0:6825:300
- 23.216.147.64
- a83f:8110:0:0:700:700:2800:4000
- 20.99.184.37
- a83f:8110:4c00:5300:4900:2000:4500:6d00
- %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\decoder.dll
- %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\326fa02\oceanofgames-top-games-exe.msi
- %TEMP%\msi907c.tmp
- %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\326fa02\localappdatafolder\updates\windows
- %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\326fa02\localappdatafolder\updates\run.vbs
- %TEMP%\msi907c.tmp
- %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\decoder.dll
- %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\326fa02\localappdatafolder\updates\import.reg
- %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\326fa02\localappdatafolder\updates\run.vbs
- %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\326fa02\localappdatafolder\updates\windows
- \Sessions\1\BaseNamedObjects\Advinst_6A3AE9B88F6944319D545784174A3117
- \Sessions\1\BaseNamedObjects\2148_prepare_evt
- \Sessions\1\BaseNamedObjects\2148_uigo_evt
- \Sessions\1\BaseNamedObjects\2148_uidone_evt
- \Sessions\1\BaseNamedObjects\2148_mdl_evt
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c290a133b60220479acf…0ca769Never scannednever seen before
- 6d346056c766ed477967…c1c005Never scannednever seen before
- 9fc2608c9e5ef5a88dd9…a4625dNever scannednever seen before
- 0c53460dc124db6c337e…2f3064Never scannednever seen before
- 5fd291193f2735fb5f3d…3ea6a4Never scannednever seen before
- 614c0e2ab48512232a4c…ff2160Never scannednever seen before
- 3577a4fe25ad453c67af…0e8dadNever scannednever seen before
- afbf22880d0129f8b11b…1a8e6cNever scannednever seen before
- 19896a23d7b054625c2f…18e618Never scannednever seen before
- 842fd831650afcd15752…959719Never 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
- 50 / 75engines flagged
- 2,660sources 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
50 of 75 antivirus engines flagged the file, including AhnLab-V3 and Alibaba.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 2,660 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: Step 3 - Setup_Install_Game.exe — 7cc9e17085066cd2299e7c37c743acbad0370554ec704c803443d112c27bf486
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — <PATH_SAMPLE.EXE>
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — <SYSTEM32>\msiexec.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: decoder.dll — %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\decoder.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: oceanofgames-top-games-exe.msi — %APPDATA%\oceanofgames.ccom\exe - step 3 - setup_install_game 1.0.0\install\326fa02\oceanofgames-top-games-exe.msi
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.99.132.105 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.62.24.77 — 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.
Evidence<PATH_SAMPLE.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.
Evidence20.99.132.105 · 20.62.24.77 · 23.216.147.76
50 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
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
- Step 3 - Setup_Install_Game.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 9.2 MB
- Last analyzed
- Sep 9, 2026, 3:34 PM UTC
7cc9e17085066cd2299e7c37c743acbad0370554ec704c803443d112c27bf486Safety & 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 any of your files were locked or renamed, do NOT pay the ransom — payment rarely restores files. Recover them from a backup instead.
- 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 Step 3 - Setup_Install_Game.exe a virus?
What is Step 3 - Setup_Install_Game.exe?
How many antivirus engines detected Step 3 - Setup_Install_Game.exe?
What should I do if I already installed Step 3 - Setup_Install_Game.exe?
How do I remove Step 3 - Setup_Install_Game.exe?
What kind of malware is Step 3 - Setup_Install_Game.exe?
What is the SHA-256 hash of Step 3 - Setup_Install_Game.exe?
How up to date is this analysis of Step 3 - Setup_Install_Game.exe?
Community
Member reviews and reports for this exact file hash.