File scan report
Verdict Safe
Is Playnite
No antivirus engine detected this widely circulated, validly signed installer, while the isolated behavioral alerts lack evidence proving injection or credential access.
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 71 flagged
- Flagged 0
- No detection 71
- No result 4
- Code signing SignPath Foundation
- Test run Completed
- First seen 11mo 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
All 71 antivirus engines that checked it returned without a detection, including 17 major contributors, and the installer carries a verified SignPath Foundation signature.
The strongest evidence is complete agreement across 75 antivirus engines, with no malicious or suspicious result and all 17 major contributors silent. The file is validly signed by SignPath Foundation and has circulated through 3,017 sources across 3,938 submissions, which is inconsistent with an obscure newly deployed payload. The test run completed once and raised mappings to and T1562.001, but it did not produce a malicious sandbox verdict. Five dropped files were checked without identifying a malicious child, and the fully covered observed host contact had no cached malicious or suspicious reputation. The mixed import-table fingerprint history is not persuasive because every match involved a different signer and may reflect a shared build or installer framework.
What We Detected
No antivirus engine flagged the sample: 0 of 75 reported it as malicious or suspicious, including all 17 major contributors. The executable has a verified signature from SignPath Foundation, no detected brand mismatch, and substantial prevalence across 3,017 sources and 3,938 submissions.
Threat Behavior
One completed sandbox run recorded techniques mapped to T1055 and T1562.001 and triggered process-injection and the Windows password store-related heuristics. The sandbox issued no malicious verdict, five inspected children were not identified as malicious, and the observed domain/IP contact was fully covered by the host-reputation check with no malicious or suspicious match.
What To Do Now
Obtain the installer from Playnite's official release channel and confirm that Windows reports the SignPath Foundation signature as valid before running it. Keep security software enabled and rescan if the signature changes, the download source is unofficial, or unexpected credential-access behavior appears.
Where this verdict could be wrong4 caveats
- One of our behaviour rules maps saved activity to T1055, but its cited evidence is a standard svchost command line and does not establish an injection mechanism.
- One of our behaviour rules associates observed the Windows password store activity with credential dumping, but the saved evidence only identifies the Windows password store and does not demonstrate memory access.
- 3 earlier files from this signer were seen and this signer is not auto-trusted from its history, so the verified SignPath Foundation signature lacks extensive historical support.
- The file appears packed, although no code section has packed-level entropy and the identified format is a .NET executable.
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/71 engines reported a malicious or suspicious result.
- All 17 major contributors returned without a detection.
- The SignPath Foundation signature is verified and no brand mismatch was detected.
- The file has 3,017 sources and 3,938 submissions over 323 days.
- No malicious sandbox verdict, malicious child, malicious host, MalwareBazaar hit, or YARAify rule was present.
- Runtime mappings include and T1562.001.
- The signer-history record covers only 3 historical samples and is not auto-trusted.
- The file appears packed for the .NET executable.
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- 9sandbox rule tags
- 5spawned processes
- 0network contacts
- 7filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
9MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1055· Process injection
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1106
- T1222
- T1497· Sandbox evasion
- T1562.001· Disables security
Observed activity
Processes started
5Programs the file ran, with their command lines.
file.exe"C:\Users\<USER>\Desktop\file.exe"PlayniteInstaller.exe"C:\Users\user\Desktop\PlayniteInstaller.exe"file.exe"C:\Users\user\Desktop\file.exe"software.exe"C:\Users\user\Desktop\software.exe"program.exe"C:\Users\user\Desktop\program.exe"
Files
5Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\PlayniteInstaller\installer.log - Written
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp - Written
C:\Users\user\AppData\Local\Temp\PlayniteInstaller - Written
C:\Users\user\AppData\Local\Temp\PlayniteInstaller\installer.log - Written
C:\Users\user\AppData\Roaming
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
\Sessions\1\BaseNamedObjects\Local\__DDrawExclMode__\Sessions\1\BaseNamedObjects\Local\__DDrawCheckExclMode__
Sandbox background — not the file
8The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time
Show all 8 entries for sandbox background — not the file
- VM host
bg.microsoft.map.fastly.net - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache. 5 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 2f3d3d627b1d30f447d1…899855Not checkedno saved verdict
- e2a794a984e1b9b25298…047c0aNot checkedno saved verdict
- 2c64cc0fa5755e3f8315…b4f8c6Not checkedno saved verdict
- d28b9246c37865014609…675af6Not checkedno saved verdict
- f9fffdb79e6b35b176f5…455718Not checkedno saved verdict
Chapter 04
Technical details
None of the 71 antivirus engines that checked it flag it; signed by SignPath Foundation.
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.
File fingerprint
- Last analyzed
- Oct 9, 2026, 1:41 AM UTC
- SHA-256
6ca62bacfa234f2b2c2b26341d5c5292d7f6ad99cb816418af58302647548d65- SHA-1
37d962355fc2c42ab01fd54f76703f3f2ecab019- MD5
8fa7ed975d52eae3649733267850c90a
About this file
PlayniteInstaller.exe is a Win32 EXE file of 256.3 kB.
- Type and size
- Win32 EXE · 256.3 kB
- Signer
- SignPath FoundationValid code signature.
- First seen
- Nov 19, 2025On VirusTotal.
- Submitted by
- 3,017 distinct sources
- Packer
- None detected
- Entropy
- 4.27 of 8
First scanned Updated
Antivirus consensus
0 of 71 engines flagged this file
4 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
These identify the compiler, runtime or installer used to build the file. They are not packing and are not a risk signal on their own.
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.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is PlayniteInstaller.exe safe?
What is PlayniteInstaller.exe?
How many antivirus engines detected PlayniteInstaller.exe?
Is PlayniteInstaller.exe digitally signed?
What is the SHA-256 hash of PlayniteInstaller.exe?
Is it safe to run PlayniteInstaller.exe?
How up to date is this analysis of PlayniteInstaller.exe?
Community
Member reviews and reports for this exact file hash.