File scan report
Verdict Low Risk
Is meteor-
This Java game-client archive has no antivirus detections, but it is rarely submitted and its contents were never inspected, so its safety cannot be confirmed.
Read the whole reasonShow less
Why not Safe? Only one source had seen it when we scanned it.
Limited evidence · Nothing points to a problem, but little confirms who made it.
Use this client only if it matches the official project release; otherwise download it again from the official source and keep your antivirus enabled.
Good practice2 tips
Low Risk: no threat found, but we could not fully confirm this file.
Get it from the publisher's own website or app store, not from a re-upload or a link someone sent you.
Keep your security software on, and stop if the file does anything you didn't expect.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 65 flagged
- Flagged 0
- No detection 65
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
4 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 65 antivirus engines that checked it flagged this Java archive, and the sandbox runs showed no confirmed harmful actions. However, only one source has ever submitted it, it carries no signature or verifiable release origin, and engines often miss threats packed inside Java archives. The evidence is too thin to call it safe.
None of the 65 antivirus engines that checked it flagged the file, including all 18 major antivirus engines. The file is a Java archive named like a Minecraft modification client, a category commonly used to disguise stealers. It was first seen on Aug 31, 2026, and only one source has submitted it. No signature, GitHub release match or known-software reference vouches for its origin, and nobody has examined the classes inside it. Sandbox technique labels for process injection and defence tampering appeared without any matching activity, so they carry no weight either way.
What We Detected
None of the 65 antivirus engines that checked it flagged this Java archive. It was first seen on Aug 31, 2026, and has been submitted by a single source. There is no code signature, no matching public release and no known-software reference entry for it.
Threat Behavior
The sandbox runs started the archive with Java. No injected processes, persistence or network activity of the sample's own were recorded. The only network contact was the analysis machine's background traffic. Some technique labels were assigned without any supporting activity and are not evidence of harm. Nobody has inspected the archive's contents, and engines often miss threats hidden in compressed Java classes.
What To Do Now
Only run this client if you downloaded it from the project's official release page and can match the file there. Otherwise obtain a fresh copy from the official source, and keep your antivirus enabled.
Where this verdict could be wrong1 caveat
- None of the antivirus engines flagged the file, and the sandbox recorded no injection target. No complete contacted-host reputation result was available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 65 antivirus engines that checked it flagged the file
- The sandbox recorded no injection targets, persistence or network activity of the sample's own
- Rarely submitted, with only one source on record
- The file name points to a game modification client, a category often abused to spread stealers
- No signature or verifiable release origin
- Nobody has inspected the archive's contents, and engines see little inside Java archives
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- 18sandbox rule tags
- 3spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
Includes 18 mapped techniques, every process, file, registry and network entry and 4 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 65 antivirus engines that checked it flag it.
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 8, 2026, 6:47 PM UTC
- SHA-256
354ae2c935ca06c61b361357a500fa752ba6c9cf076cec0bcb2fdd20ac8b4ec4- SHA-1
3ec64f688ea02cb93a30be50fa3d895fcff2b2ac- MD5
cf37ac39932def7f5212254535248789
About this file
meteor-client-1.21.11_26.1.2-local.jar is a JAR file of 4.8 MB.
- Type and size
- JAR · 4.8 MB
- Signer
- Not applicable
- First seen
- Aug 31, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
- Low Riskafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Includes every engine result (75), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 5 questions people ask most about this file.
Is meteor-client-1.21.11_26.1.2-local.jar safe?
What is meteor-client-1.21.11_26.1.2-local.jar?
How many antivirus engines detected meteor-client-1.21.11_26.1.2-local.jar?
What is the SHA-256 hash of meteor-client-1.21.11_26.1.2-local.jar?
How up to date is this analysis of meteor-client-1.21.11_26.1.2-local.jar?
Community
Member reviews and reports for this exact file hash.