Is mgaming v1.exe safe?
Unsigned, brand-new executable flagged by one tier-1 engine with no family consensus and no sandbox malice.
5 of 75 engines flagged the file, including one tier-1 detection. The sample is unsigned, appeared today, and shows no malicious sandbox behaviour or known-bad network activity.
2373dab3e6047737b7…129f133687f995Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
5 of 75 engines flagged the file, including one tier-1 detection. The sample is unsigned, appeared today, and shows no malicious sandbox behaviour or known-bad network activity.
A single tier-1 engine (Microsoft) returned a generic detection while 16 other tier-1 engines stayed silent. The file is unsigned, extremely new, and has no corroborating external-intel hits. Sandbox execution produced no malicious verdict and no C2 traffic. The combination of limited detections, lack of signing, and minimal prevalence places the file in mixed-signal territory.
What We Detected
5 of 75 engines flagged the sample; Microsoft (tier-1) labelled it Trojan:Win32/Wacatac.C!ml. Three tier-2 engines and one low-trust engine also reported malicious. No tier-1 family consensus exists.
Threat Behavior
The executable is unsigned and first seen today. Sandbox execution wrote temporary Python runtime files but triggered no malicious verdict and contacted no domains. No dropped children were flagged malicious.
What To Do Now
Do not execute the file on production systems. Keep endpoint protection enabled and monitor for additional submissions or updated detections.
Where this verdict could be wrong1 caveat
- sandbox executed without malicious verdict and no C2 domains observed
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- sandbox returned no malicious verdict
- no contacted malicious hosts recorded
- unsigned executable
- rare_new prevalence
- single tier-1 detection
Treat the file as untrusted; avoid execution until further reputation data or additional engine detections appear.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete5 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 10MITRE ATT&CK techniques
- 4spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Manipulated how the operating system loads code, which can redirect execution.
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.
Moderate concern: Scans through your files and folders.
Note: Listed running processes; both legitimate software and malware may do this.
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.
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
mgaming v1.exe
2373dab3e6047737b786c2d1608f3421542e500a7bcdb6e6e5129f133687f995
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\mgaming v1.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
mgaming v1.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI50362\VCRUNTIME140.dll
04Isolated runtime analysis - Written fileObserved
_bz2.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI50362\_bz2.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\<USER>\AppData\Local\Temp\_MEI50362\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI50362\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI50362\_decimal.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI50362\_hashlib.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI50362\_lzma.pyd
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 33f4fddc181066fce06b…510c57Never scannednever seen before
- 3a72b4f29f39a265d32a…5e78adNever scannednever seen before
- 39095f59c41d76ec81bb…9c84f9Never scannednever seen before
- 6ee44dd0d8510dc024c9…34e5dcNever scannednever seen before
- 1bd81dfd19204b446625…c16818Never scannednever seen before
- 4cadbc0c39da7c672220…d1990dNever scannednever seen before
- 64a1dad031e97f13b1a0…3f4eecNever scannednever seen before
- 6eda016742a6171205a3…24207dNever scannednever seen before
- c29dce345ec2dbc5d649…ea6296Never scannednever seen before
- 2703635d835396afd0f1…1932c0Never 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.
- 0rule hits recorded
- 5 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
5 of 75 antivirus engines flagged the file, including APEX and Gridinsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 3 times from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: mgaming v1.exe — 2373dab3e6047737b786c2d1608f3421542e500a7bcdb6e6e5129f133687f995
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\mgaming v1.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — mgaming v1.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: VCRUNTIME140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI50362\VCRUNTIME140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _bz2.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI50362\_bz2.pyd
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
5 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
Barely seen in the wild and first surfaced recently. 5 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- mgaming v1.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 8.0 MB
- Last analyzed
- Aug 16, 2026, 9:27 AM UTC
2373dab3e6047737b786c2d1608f3421542e500a7bcdb6e6e5129f133687f995Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is mgaming v1.exe safe, or is it malware?
What is mgaming v1.exe?
How many antivirus engines detected mgaming v1.exe?
I already downloaded and ran mgaming v1.exe — what should I do?
How do I remove mgaming v1.exe?
What kind of malware is mgaming v1.exe?
What is the SHA-256 hash of mgaming v1.exe?
How up to date is this analysis of mgaming v1.exe?
Community
Member reviews and reports for this exact file hash.