File scan report
Verdict Suspicious
Is Update-
Six of the 69 antivirus engines that checked it raised generic alerts, while unsigned provenance and several offensive behavior mappings outweigh the otherwise plausible Windows…
Read the whole reasonShow less
Why Suspicious? 6 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
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 run 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 ran 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
6 of 69 flagged
- Flagged 6
- No detection 63
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 5mo 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
The file launches Windows Package Manager to install or upgrade a Microsoft Store package, which is consistent with its name. However, it is unsigned, six of the 69 antivirus engines that checked it flag it, and the test run maps activity to five offensive techniques, so it should not be trusted without confirming its source.
Six of the 69 antivirus engines that checked it flagged the executable, but no major antivirus engines detected it and there is no family consensus. Observation from the test run shows it invoking Windows Package Manager with a Microsoft Store package identifier, lending support to its claimed update purpose. Against that, the executable is unsigned and the sandbox mapped activity to process injection, service creation, defense impairment, file deletion, and reflective code loading techniques. The sandbox did not return a malicious verdict, named no injected target, and the host-reputation check found no cached malicious or suspicious result for the two distinct observed hosts. The mixture of plausible updater activity and unresolved offensive indicators warrants caution rather than a definitive malware-family attribution.
What We Detected
Six of the 69 antivirus engines that checked it flagged the executable. K7AntiVirus used a generic trojan label, SentinelOne reported a suspicious PE, and the remaining detections were generic malware or machine-learning labels; no major antivirus engines identified a threat and no named family achieved consensus. The file is also unsigned, so there is no authenticated publisher behind its Gaming Services update claim.
Threat Behavior
The completed sandbox run observed the file launching Windows Package Manager to install or upgrade Microsoft Store package 9MWPM2CQNLHN, which is consistent with updater behavior. It also mapped activity to T1055, T1485, T1543, T1562.001, and T1620. These mappings are concerning, although no injected target was recorded and the sandbox itself did not return a malicious verdict. The two distinct contacted hosts had no cached malicious or suspicious reputation, while the ten dropped files have no saved verdict and therefore remain unclassified.
What To Do Now
Do not run this copy unless it came from a source you can independently verify. Prefer updating Gaming Services directly through the Microsoft Store or Windows Package Manager, keep security software enabled, and quarantine or remove this executable if its origin is unknown.
Where this verdict could be wrong4 caveats
- No major antivirus engines flagged the file, and the six detections use generic trojan, machine-learning, or suspicious-PE labels rather than a shared malware family.
- The observed command invokes Windows Package Manager to install or upgrade a Microsoft Store package, behavior consistent with the stated updater purpose.
- The completed sandbox run did not issue a malicious verdict, but several offensive technique mappings still require caution.
- No cached malicious or suspicious reputation was found for the two distinct contacted hosts, though host reputation alone cannot establish file safety.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No major antivirus engines flagged the file, and the detections do not agree on a named malware family.
- The observed command uses Windows Package Manager to install or upgrade a package from the Microsoft Store source.
- The completed sandbox run did not return a malicious verdict.
- No packing was identified, and the code section did not show unusually high entropy.
- The reputation check covering both distinct observed hosts found no cached malicious or suspicious result.
- The executable is unsigned and therefore lacks authenticated publisher provenance.
- Six of the 69 antivirus engines that checked it raised generic malware, trojan, suspicious-PE, or machine-learning detections.
- The test run mapped activity to process injection, file deletion, service creation, defense impairment, and reflective code loading techniques.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 25sandbox rule tags
- 4spawned processes
- 1network contact
- 31filesystem & 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: Ran commands or a script on the test computer.
Moderate concern: Downloaded a file during the test run.
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.
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.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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 6: FileSeen in the test run
Update-GamingServices.exe
143330bf800723ac9a83ee7a178560a64d25128ec65b04cc0e680f0d3b8efe82
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 6: ProcessSeen in the test run
Update-GamingServices.exe
"C:\Users\<USER>\Desktop\Update-GamingServices.exe"
Test run - Evidence 3 of 6: ProcessSeen in the test run
winget.exe
"C:\Users\<USER>\AppData\Local\Microsoft\WindowsApps\winget.exe" upgrade --id 9MWPM2CQNLHN --exact --source msstore --accept-source-agreements --accept-package-agreements --silent --disable-interactivity
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 6: Written fileSeen in the test run
GamingServicesUpdate.log
C:\Users\<USER>\AppData\Local\Temp\GamingServicesUpdate.log
Test run - Evidence 5 of 6: Written fileSeen in the test run
VRegDriver
\Device\VRegDriver
Test run - +1 more recorded observation
- 1
Network
Hosts contacted
- Evidence 6 of 6: Contacted hostSeen in the test run
74.114.119.201
Contacted during the test run.
Test run
6 facts from the test run. See the full activity list.
Includes 25 mapped techniques, every process, file, registry and network entry and 9 dropped files.
Show the technical evidenceChapter 04
Technical details
6 of the 69 antivirus engines that checked it flag 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 6
- APEXMalicious
- BkavW32.Malware.D7354AD9
- K7AntiVirusTrojan ( 700000201 )
- K7GWTrojan ( 700000201 )
- SentinelOneStatic AI - Suspicious PE
- Trapminemalicious.moderate.ml.score
File fingerprint
- Last analyzed
- Oct 14, 2026, 3:23 PM UTC
- SHA-256
143330bf800723ac9a83ee7a178560a64d25128ec65b04cc0e680f0d3b8efe82- SHA-1
3198528c7b843fdbb44354eb1e01e92c19dca1a4- MD5
ebaa985f8411fc08c5f392f819dcf648
About this file
Update-GamingServices.exe is a Win32 EXE file of 33.3 kB.
- Type and size
- Win32 EXE · 33.3 kB
- Signer
- UnsignedNo code signature.
- First seen
- May 14, 2026On VirusTotal.
- Submitted by
- 34 distinct sources
- Packer
- None detected
- Entropy
- 5.71 of 8
First scanned
Includes every engine result (74), 1 matched signature rule, 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 Update-GamingServices.exe safe, or is it malware?
What is Update-GamingServices.exe?
How many antivirus engines detected Update-GamingServices.exe?
What should I do if I already ran Update-GamingServices.exe?
What is the SHA-256 hash of Update-GamingServices.exe?
How up to date is this analysis of Update-GamingServices.exe?
Community
Member reviews and reports for this exact file hash.