File scan report
Verdict Safe
Is 67-
None of the 65 antivirus engines that checked it flagged this Java archive, and the sandbox runs showed only normal Java activity in the test run with no network contact…
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This Java application shows no signs of malware; use it if it came from a source you trust, and keep your security software enabled.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the project's own website.
Keep your security software and system 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 65 flagged
- Flagged 0
- No detection 65
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
1 point against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This Java application drew no detections from any of the 74 engines, including all major antivirus engines that analysed it. In the sandbox runs it simply launched under the Java runtime, wrote ordinary Java temp files, made no network connections and set no persistence. It has been submitted by 33 different sources over three months.
None of the 65 antivirus engines that checked it flagged the file, and 17 major antivirus engines returned clean results. The sandbox runs recorded only the Java runtime starting the archive, with standard Java usage and performance files written. No network contacts, registry changes or persistence were recorded. Moderate prevalence over 92 days further supports a benign Java client, though no publisher signature is available for this file type.
What We Detected
None of the 65 antivirus engines that checked it flagged this Java archive, including Kaspersky, ESET, BitDefender and Microsoft. It has been seen from 33 distinct submitters over roughly three months.
Threat Behavior
In the sandbox runs the archive launched under the standard Java runtime and wrote only routine Java temporary and usage files. No network connections, registry changes or persistence mechanisms were recorded. The sandbox noted checks for the CPU name and debug environment, which are common in Java clients.
What To Do Now
The file appears benign. Run it only if you obtained it from the developer or community you trust, and keep your antivirus protection enabled.
Where this verdict could be wrong2 caveats
- The sandbox tagged the file for checking CPU name and detecting a debug environment, traits sometimes seen in evasive Java malware, though many legitimate Java clients do the same.
- No host-reputation cross-check or external database lookups were completed, so those sources add no confirmation either way.
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, including every major antivirus engine that analysed it.
- Sandbox runs showed only normal Java activity in the test run, with no network connections or persistence.
- Submitted by 33 different sources over about three months.
- The sandbox noted checks for the CPU name and for a debugging environment, which some evasive software also performs.
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- 15sandbox rule tags
- 4spawned processes
- 0network contacts
- 16filesystem & mutex artifacts
Includes 15 mapped techniques, every process, file, registry and network entry and 3 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
- Jul 21, 2026, 7:28 PM UTC
- SHA-256
2b8371928a5404de7983b14becfd933fd5988d8e1b07e4ab99c12488bf6b972f- SHA-1
6442b8fd0903ed97245d02c1866e970e23feb02b- MD5
aec4005a1b4103e75c0f0e013d88ff22
About this file
67-Client.jar is a JAR file of 3.5 MB.
- Type and size
- JAR · 3.5 MB
- Signer
- Not applicable
- First seen
- Jul 20, 2026On VirusTotal.
- Submitted by
- 33 distinct sources
First scanned Updated
Verdict history
- Suspicious
- Safeafter 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 (74), 1 matched signature rule 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 67-Client.jar safe?
What is 67-Client.jar?
How many antivirus engines detected 67-Client.jar?
What is the SHA-256 hash of 67-Client.jar?
Is it safe to open or run 67-Client.jar?
How up to date is this analysis of 67-Client.jar?
Community
Member reviews and reports for this exact file hash.