File scan report
Verdict Safe
Is Minecraft.
No engine detected malware, the test run found no offensive activity, and the established sample showed no packing or malicious-intelligence matches.
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 Unsigned
- Test run Completed
- First seen 7mo ago
Chapter 02
Why we think so
2 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 71 antivirus engines that checked it returned without a malicious or suspicious detection, including 17 major antivirus engines.
The antivirus result is consistently favorable, with no malicious or suspicious findings among 75 engines and no major detections. One completed sandbox run produced no malicious verdict, offensive technique, persistence indicator, or dropped-file evidence. The executable has appeared through 170 sources and 188 submissions over 187 days, which makes an undiscovered widespread threat less likely. The antivirus analysis also found no high-entropy code or likely packing, and external research feeds supplied no matching malware intelligence. The main limitations are the absent publisher signature and a direct connection to 162.159.36.2 whose reputation was not completely checked.
What We Detected
None of the 71 antivirus engines that checked it flagged the executable as malicious or suspicious. This includes 17 major antivirus engines, and there was no malware-family consensus. External intelligence checks also returned no MalwareBazaar entry, CIRCL match, or YARAify rule.
Threat Behavior
One sandbox execution recorded four techniques common in legitimate software but no offensive techniques, malicious sandbox verdict, persistence indicators, or written files. The executable contacted 162.159.36.2 directly; because contacted-host reputation was not checked or saved, no complete reputation conclusion is available for that endpoint. PE analysis found no likely packing or high-entropy code.
What To Do Now
Use the file only if it came from the expected official distribution channel. Keep security software enabled, and verify the download source because the executable has no publisher signature confirming its claimed identity.
Where this verdict could be wrong1 caveat
- The file is unsigned for an executable, so no verified publisher identity supports the Minecraft branding.
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.
- One sandbox run produced no malicious verdict and no offensive techniques.
- The sample has 170 unique sources and 188 submissions over 187 days.
- No packing, high-entropy code, malicious child, or external-intelligence match was identified.
- The executable is unsigned, leaving its publisher identity unverified.
- No complete contacted-host reputation result is available.
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 4sandbox rule tags
- 3spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
Includes 4 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
None of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 12, 2026, 2:46 PM UTC
- SHA-256
c73ebd7bfd196ced28e1271b968e1571b2ba56515cbdf58f5257b3e21cc5f2d2- SHA-1
b98aac5742a58073ca6aa74a726b49dc38fe7229- MD5
ee8d9305ad47151c048aa4fbccf65714
About this file
Minecraft.Client.exe is a Win32 EXE file of 9.5 MB.
- Type and size
- Win32 EXE · 9.5 MB
- Signer
- UnsignedNo code signature.
- First seen
- Mar 9, 2026On VirusTotal.
- Submitted by
- 170 distinct sources
- Packer
- None detected
- Entropy
- 6.16 of 8
First scanned
Includes every engine result (75), 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 Minecraft.Client.exe safe?
What is Minecraft.Client.exe?
How many antivirus engines detected Minecraft.Client.exe?
What is the SHA-256 hash of Minecraft.Client.exe?
Is it safe to run Minecraft.Client.exe?
How up to date is this analysis of Minecraft.Client.exe?
Community
Member reviews and reports for this exact file hash.