Is Minecraft.Client.exe safe?
No engine detected malware, runtime analysis found no offensive activity, and the established sample showed no packing or malicious-intelligence matches.
All 75 antivirus engines returned without a malicious or suspicious detection, including 17 tier-1 engines. One sandbox run found no offensive techniques or malicious verdict, while broad prevalence and ordinary PE structure further reduce concern; the unsigned status and unchecked direct-IP contact remain caveats.
c73ebd7bfd196ced28…57b3e21cc5f2d2Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
All 75 antivirus engines returned without a malicious or suspicious detection, including 17 tier-1 engines. One sandbox run found no offensive techniques or malicious verdict, while broad prevalence and ordinary PE structure further reduce concern; the unsigned status and unchecked direct-IP contact remain caveats.
The antivirus result is consistently favorable, with no malicious or suspicious findings among 75 engines and no tier-1 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. Static 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 75 antivirus engines flagged the executable as malicious or suspicious. This includes 17 tier-1 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 ambient techniques 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 endpoint protection enabled, and verify the download source because the executable has no publisher signature confirming its claimed identity.
Where this verdict could be wrong2 caveats
- signing.signed=false for an executable, so no verified publisher identity supports the Minecraft branding.
- triggeredHeuristics[0] reports direct-IP traffic to 162.159.36.2, and contactedHosts=null leaves that endpoint without a completed reputation cross-check.
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/75 engines reported a malicious or suspicious result.
- 17 tier-1 engines reported no detection.
- 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.
- Sandbox activity included direct-IP traffic to 162.159.36.2.
- No complete contacted-host reputation result is available.
It is reasonable to use this file if it came from the expected official source, but verify the download origin because it is unsigned. Keep endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
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
- 4MITRE ATT&CK techniques
- 3spawned processes
- 1network contacts
- 0filesystem & mutex artifacts
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
Minecraft.Client.exe
c73ebd7bfd196ced28e1271b968e1571b2ba56515cbdf58f5257b3e21cc5f2d2
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\Minecraft.Client.exe" -install
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\Minecraft.Client.exe" /install
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
04Isolated runtime analysis
4 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.
- 162.159.36.2
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 75engines flagged
- 170sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 170 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 188 times from 170 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Minecraft.Client.exe — c73ebd7bfd196ced28e1271b968e1571b2ba56515cbdf58f5257b3e21cc5f2d2
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\user\Desktop\Minecraft.Client.exe" -install
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\Minecraft.Client.exe" /install
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
0 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Minecraft.Client.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 9.1 MB
- Last analyzed
- Sep 12, 2026, 2:46 PM UTC
c73ebd7bfd196ced28e1271b968e1571b2ba56515cbdf58f5257b3e21cc5f2d2Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.