Is game.exe safe?
Runtime analysis observed injection, service creation, and defense impairment, reinforced by 15 YARA rules, despite no detections among 75 antivirus engines.
A completed runtime analysis produced a malware finding and mapped activity to process injection, service creation, and defense impairment. Fifteen researcher YARA rules reinforce those concerns, although 0 of 75 antivirus engines detected the file and the observed network contacts had no cached threat findings.
487bd28f3d0b43ed98…586c7bc82a9474Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran 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.
A completed runtime analysis produced a malware finding and mapped activity to process injection, service creation, and defense impairment. Fifteen researcher YARA rules reinforce those concerns, although 0 of 75 antivirus engines detected the file and the observed network contacts had no cached threat findings.
The strongest evidence is the completed runtime analysis, which produced a malware finding and recorded T1055, T1543.003, and T1562.001. These techniques indicate possible process injection, service-based execution or persistence, and interference with security controls. Fifteen YARA rules also matched, including a script-injection detector and several anti-debugging checks. In contrast, 0 of 75 antivirus engines detected the file, all 17 participating tier-1 engines were non-detecting, and the complete host cross-check found no known threat hosts. The behavioral and researcher-rule convergence outweighs those counter-signals, but the conflict limits confidence and does not support assigning a specific family.
What We Detected
A completed runtime analysis produced a malware finding and recorded three offensive techniques: T1055 process injection, T1543.003 Windows service activity, and T1562.001 defense impairment. Researcher intelligence also reported 15 matching YARA rules, including CP_Script_Inject_Detector and multiple debugger-detection rules.
Threat Behavior
The sample exhibited injection-related and anti-analysis indicators, wrote a temporary driver-like file, and modified several service registry entries. Its observed contacts included Microsoft and Mozilla infrastructure plus a mining-themed domain; the host-reputation cross-check covered all 20 distinct contacts and found no known malicious or suspicious hosts. Ten dropped files were inspected without a malicious finding, but all remain unclassified.
What To Do Now
Do not run the file on a production system. If it has already executed, keep endpoint protection enabled, isolate the device, run a full scan, and review services, drivers, and security-control changes for unauthorized activity.
Where this verdict could be wrong5 caveats
- All 75 antivirus engines were non-detecting, including 17 tier-1 engines, which is substantial counter-evidence to the runtime result.
- contactedHosts found no malicious or suspicious no complete contacted-host reputation result was available records for www.microsoft.com and res.public.onecdn.static.microsoft.
- droppedChildren inspected 10 files without a malicious child, but every child remains unclassified rather than affirmatively benign.
- externalIntel.circl.knownMalicious=null and MalwareBazaar returned no hit.
- The sample is common and old, with 495348 submissions since 2018, reducing the likelihood of an obscure newly emerging 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.
- 0 of 75 antivirus engines detected the sample.
- All 17 participating tier-1 engines were non-detecting.
- The complete host cross-check found no malicious or suspicious contacts.
- No inspected dropped child was identified as malicious.
- The sample has circulated widely since 2018.
- Completed runtime analysis produced a malware finding.
- T1055 indicates possible process injection.
- T1543.003 indicates Windows service creation or modification.
- T1562.001 indicates possible impairment of security tools.
- Fifteen YARA rules matched, including CP_Script_Inject_Detector.
- The executable is unsigned despite code signing being applicable.
Quarantine the file and avoid executing it outside an isolated analysis environment. If it already ran, keep security software enabled, isolate the host, and investigate service, driver, and endpoint-protection changes.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 of 40 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete6 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
- 28MITRE ATT&CK techniques
- 15spawned processes
- 40network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a scheduled task, which can provide persistence.
High concern: Injected code into another process, a technique that can conceal execution.
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.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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
game.exe
487bd28f3d0b43ed9827ba519d6d113c4f31059bd62b4492da586c7bc82a9474
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\game.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\wuapihost.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
vsbndqqvotjt.sys
C:\Users\<USER>\AppData\Local\Temp\vsbndqqvotjt.sys
04Isolated runtime analysis - Written fileObserved
Program Files (x86)
C:\Program Files (x86)
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
query.prod.cms.rt.microsoft.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostDerived
www.microsoft.com
Saved reputation verdict: safe.
07Contacted-host cross-check - +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; 1 returned "malicious".
Adversary techniques mapped to the MITRE ATT&CK framework.
- query.prod.cms.rt.microsoft.com
- www.microsoft.com
- res.public.onecdn.static.microsoft
- us-zephyr.miningocean.org
- 212.143.182.52.in-addr.arpa
- 45.107.88.104.in-addr.arpa
- 173.117.168.52.in-addr.arpa
- sfd-production.azurefd.net
- 106.89.54.20.in-addr.arpa
- 210.81.184.52.in-addr.arpa
- a83f:8110:cce1:d301:10:0:0:0
- 23.216.147.76
- 23.59.190.187
- a83f:8110:9403:0:0:0:9403:0
- 192.168.0.36
- 13.107.39.203
- 192.168.0.39
- 192.168.0.14
- 23.216.147.64
- a83f:8110:0:0:1b00:100:2800:0
- HKLM\System\CurrentControlSet\Services\GoogleUpdaterInternalService117.0.5934.0\Start
- HKLM\System\CurrentControlSet\Services\GoogleUpdaterInternalService117.0.5934.0\ImagePath
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService119.0.6042.0\Start
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService119.0.6042.0\ImagePath
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications\Data\418A073AA3BC1C75
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService122.0.6180.0\Start
- C:\Users\<USER>\AppData\Local\Temp\vsbndqqvotjt.sys
- C:\Program Files (x86)
- C:\Program Files (x86)\Microsoft
- C:\Program Files (x86)\Microsoft\EdgeUpdate\1.3.147.37
- C:\Program Files (x86)\Microsoft\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2390.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER244C.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER247C.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER25D3.tmp.WERInternalMetadata.xml
- \BaseNamedObjects\Local\SM0:7488:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:7488:120:WilError_01
- \BaseNamedObjects\Local\SM0:7656:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:7656:120:WilError_01
- \BaseNamedObjects\Local\SM0:7636:304:WilStaging_02
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 2099f0854585b2115e09…0d7b95Never scannednever seen before
- 3096d8e82917a9b73f32…3cdd5bNever scannednever seen before
- 30e621d2720a1f8b727f…44e8bcNever scannednever seen before
- f2f69d75c8e2d790026c…f926e9Never scannednever seen before
- 67f193c7b2edcd0c93ef…bbaa2dNever scannednever seen before
- 4d5434fc95c38b74a2ac…fea714Never scannednever seen before
- 4f1628e9a5aeb665aec3…8a9607Never scannednever seen before
- 91d3fc490565ded7621f…1145f5Never scannednever seen before
- 896256ee322d663494b6…60e232Never scannednever seen before
- 058fbe06656f584be64b…843ca0Never 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.
- 6rule hits recorded
- 0 / 75engines flagged
- 3,698sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 isolated runtime environment classified the observed behavior as malicious.
Verdict inputView chapterProvenanceObservedSourceIsolated runtime analysisObserved at - 02
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: game.exe — 487bd28f3d0b43ed9827ba519d6d113c4f31059bd62b4492da586c7bc82a9474
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\game.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\wuapihost.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: vsbndqqvotjt.sys — C:\Users\<USER>\AppData\Local\Temp\vsbndqqvotjt.sys
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Program Files (x86) — C:\Program Files (x86)
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: query.prod.cms.rt.microsoft.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved 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.
- Check_OutputDebugStringA_iat
- CP_Script_Inject_Detector
- DebuggerCheck__API
- DebuggerCheck__QueryInfo
- DebuggerException__SetConsoleCtrl
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%SAMPLEPATH%\game.exe
0 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
- game.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.5 MB
- Last analyzed
- Sep 27, 2026, 7:25 AM UTC
487bd28f3d0b43ed9827ba519d6d113c4f31059bd62b4492da586c7bc82a9474Safety & 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 run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran 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 you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy 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 game.exe malware?
What is game.exe?
How many antivirus engines detected game.exe?
I already downloaded and ran game.exe — what should I do?
How do I remove game.exe?
What kind of malware is game.exe?
What is the SHA-256 hash of game.exe?
How up to date is this analysis of game.exe?
Community
Member reviews and reports for this exact file hash.