File scan report
Verdict Safe
Is Sunstone
This Java archive drew no detections from any of the 75 engines, and the sandbox runs recorded only ordinary Java activity in the test run with no high-risk techniques.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The file appears clean; download it only from the developer's official page and keep your antivirus enabled while running it.
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 64 flagged
- Flagged 0
- No detection 64
- No result 11
- Code signing Not applicable
- Test run Completed
- First seen 2mo 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
None of the 64 antivirus engines that checked it flagged this Java archive, including all major antivirus engines. The sandbox runs show only the Java runtime starting the file, with no confirmed injection, no network contacts and no harmful dropped files. It is rarely seen, so run it only from a source you trust.
None of the 64 antivirus engines that checked it flagged the file, and every major antivirus engine that analysed it reported it clean. The sandbox runs recorded the Java runtime launching the archive and writing normal Java usage and performance files. Technique labels for process injection and defence tampering appeared without any injected process or matching artefact, which is common on clean files. No network contacts by the sample were recorded, though no complete host-reputation check is available. The file is rare, with a single submitter, which limits community confidence but is not hostile evidence.
What We Detected
None of the 64 antivirus engines that checked it flagged this Java archive, and all major antivirus engines that analysed it returned clean results. No external threat-intelligence listing or brand impersonation was found.
Threat Behavior
The sandbox runs show the Java runtime launching the archive and writing standard Java usage and performance-data files. Labels for process injection and defence tampering were mapped without any target process or matching artefact, so they are not evidence of either. No network activity by the sample was recorded, and no dropped file was identified as harmful.
What To Do Now
The evidence points to an ordinary Java application, likely a game-server plugin in beta. Because it is rarely seen, obtain it from the original developer, keep your security software enabled, and rescan if the file changes.
Where this verdict could be wrong1 caveat
- The file was seen from a single submitter and our own static analysis did not run, so a fresh, undetected Java payload cannot be fully ruled out.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No detections from any of the 75 engines, including all major antivirus engines.
- Sandbox activity limited to the Java runtime running the archive.
- No high-risk techniques confirmed and no harmful dropped files identified.
- Seen from only one submitter, so community history is minimal.
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
- 3spawned processes
- 0network contacts
- 15filesystem & 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 64 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:49 PM UTC
- SHA-256
67d10864d8686c73ab84c723e89241139aac269f613db400857f02f41e55077a- SHA-1
462c451d8f3a8e02160588ebf4cb086b8c2860bf- MD5
b66ef46d7681741616843859b3744fe5
About this file
SunstoneSMP-2.0BETA_NOT_READY.jar is a JAR file of 107.6 kB.
- Type and size
- JAR · 107.6 kB
- Signer
- Not applicable
- First seen
- Aug 14, 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
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 6 questions people ask most about this file.
Is SunstoneSMP-2.0BETA_NOT_READY.jar safe?
What is SunstoneSMP-2.0BETA_NOT_READY.jar?
How many antivirus engines detected SunstoneSMP-2.0BETA_NOT_READY.jar?
What is the SHA-256 hash of SunstoneSMP-2.0BETA_NOT_READY.jar?
Is it safe to open or run SunstoneSMP-2.0BETA_NOT_READY.jar?
How up to date is this analysis of SunstoneSMP-2.0BETA_NOT_READY.jar?
Community
Member reviews and reports for this exact file hash.