File scan report
Verdict Suspicious
Is Open
One less reliable detection contrasts with split sandbox results; the unsigned, protected installer lacks corroborating malicious network, file it created, or family evidence.
Read the whole reasonShow less
Why Suspicious? One antivirus engine (APEX) flags it and one of our detection rules matched it.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
Confirm the file's SHA-256 with the developer's official release before use. Keep security protection enabled and do not run it if the source or checksum cannot be verified.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 62 flagged
- Flagged 1
- No detection 61
- No result 13
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 1 of the 62 antivirus engines that checked it flagged the installer, and no major antivirus engines identified malware. However, one sandbox run returned a malicious result while another was clean, and the executable is unsigned and protected, so caution is warranted until its origin and checksum are verified.
The antivirus evidence is weak: APEX alone flagged the file, while 14 major antivirus engines reported no detection. Runtime findings are contradictory because one sandbox run returned malicious and another returned clean. The mapping has no named injection target, so it does not establish process injection. The observed hosts had no malicious or suspicious reputation, and no malicious child or malware-specific rule provided corroboration. Nevertheless, the executable is unsigned and protected with .NET Reactor, leaving uncertainty about its publisher and concealed code.
What We Detected
Only 1 of the 62 antivirus engines that checked it flagged the installer, and that detection came from APEX, a less reliable detector. No major antivirus engines supplied a malware-family identification. The executable has no digital signature and uses .NET Reactor protection, which makes its code less transparent but does not by itself prove malicious intent.
Threat Behavior
The sandbox evidence is inconsistent: one run returned a malicious assessment while another returned clean. A T1055 mapping appeared without a named injection target, so the evidence does not demonstrate actual process injection. The observed hosts had no malicious or suspicious reputation, and no malicious file it created, persistence indicator, or malware-specific community rule corroborated the adverse result.
What To Do Now
Verify the SHA-256 checksum against the developer's official release information before running it. Keep security software enabled and, if the source or checksum cannot be confirmed, avoid execution or test it only in an isolated environment.
Where this verdict could be wrong3 caveats
- Only one less reliable engine flagged the file, while 14 major antivirus engines reported no detection.
- No malicious contacted host, malicious child, malware-specific community rule, or public malware-database listing corroborates the adverse sandbox result.
- Four of five files built with the same import table previously received safe outcomes, although their different publishers make those matches weak.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of the 62 antivirus engines that checked it flagged the file, and no major antivirus engines detected it.
- No observed host was identified as malicious or suspicious.
- No inspected child was identified as malicious.
- No malware-specific community rule or public malware-database listing matched the hash.
- No named process-injection target or persistence indicator was recorded.
- The Windows executable is unsigned, so there is no verified publisher identity.
- One sandbox run produced a malicious assessment, although another run was clean.
- The executable uses .NET Reactor protection, which obscures portions of its code.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 5 isolated tests; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 5isolated sandbox runs
- 13sandbox rule tags
- 5spawned processes
- 10network contacts
- 20filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Unpacked hidden content while it ran.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
OpenGameMate-Setup-0.1.0.exe
9f797c52d4226fbc4b0f080a4925582bb3bef19664de98bd7be125c3c33c6d4d
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
OpenGameMate-Setup-0.1.0.exe
"C:\Users\<USER>\Desktop\OpenGameMate-Setup-0.1.0.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
OpenGameMate-Setup-0.1.0.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-G5NGIA68E7.tmp\OpenGameMate-Setup-0.1.0.tmp" /SL5="$4006E,5170735,914944,C:\Users\<USER>\Desktop\OpenGameMate-Setup-0.1.0.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
OpenGameMate-Setup-0.1.0.tmp
C:\Users\<USER>\AppData\Local\Temp\is-G5NGIA68E7.tmp\OpenGameMate-Setup-0.1.0.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-D5UEGAQ3TS.tmp\_isetup\_setup64.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
www.msftncsi.com
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
23.11.32.159
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 13 mapped techniques, every process, file, registry and network entry and 6 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 62 antivirus engines that checked it flags it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
- APEXMalicious
File fingerprint
- Last analyzed
- Oct 21, 2026, 12:25 AM UTC
- SHA-256
9f797c52d4226fbc4b0f080a4925582bb3bef19664de98bd7be125c3c33c6d4d- SHA-1
9181a082245262c1b2732cb101574f7df4d0c0ef- MD5
fade20f9b9aecbb7d27f89a9b1a74e31
About this file
OpenGameMate-Setup-0.1.0.exe says it is OpenGameMate Setup (OpenGameMate), 6.4 MB.
- Claims to be
- OpenGameMate Setup (OpenGameMate)From the file's own version information, written by whoever built it.
- Type and size
- Win32 EXE · 6.4 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 17, 2026On VirusTotal.
- Submitted by
- 5 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- .NET Reactor 2.X-3.X (DetectItEasy protector)Packing hides code; legitimate installers use it too.
- Entropy
- 6.50 of 8
First scanned
Includes every engine result (75), 2 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is OpenGameMate-Setup-0.1.0.exe safe, or is it malware?
What is OpenGameMate-Setup-0.1.0.exe?
How many antivirus engines detected OpenGameMate-Setup-0.1.0.exe?
I already downloaded and installed OpenGameMate-Setup-0.1.0.exe — what should I do?
What is the SHA-256 hash of OpenGameMate-Setup-0.1.0.exe?
How up to date is this analysis of OpenGameMate-Setup-0.1.0.exe?
Community
Member reviews and reports for this exact file hash.