File scan report
Verdict Safe
Is shoreline-
This Java add-on archive was flagged by none of the 64 antivirus engines that checked it, and the combined sandbox verdict was clean with no high-risk behaviour.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This add-on appears clean based on the available evidence. Obtain it only from the project's official distribution channel 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.
Antivirus results
0 of 64 flagged
- Flagged 0
- No detection 64
- No result 11
- Code signing Not applicable
- Test run Completed
- First seen 21d ago
Chapter 02
Why we think so
1 point against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Four sandbox runs only showed the Java runtime starting normally, with no injection target, no contact beyond the analysis machine's own background traffic, and no hits in malware databases.
None of the 64 antivirus engines that checked it flagged the file, and the 18 major engines that analysed it all reported it clean. The combined sandbox verdict was clean, and no high-risk techniques were recorded. The only network contacts were the analysis machine's own background traffic, and reputation checks on them were clean. Public malware databases and community rule sets had no matches. The file is unsigned and rarely submitted, which limits provenance but adds no hostile evidence.
What We Detected
This Java archive, apparently a game add-on build first seen on Oct 4, 2026, was flagged by none of the 64 antivirus engines that checked it. All 18 major engines that analysed it reported it clean. Public malware databases and community detection rules returned no matches.
Threat Behavior
The combined sandbox verdict was clean. Only the Java runtime was observed starting, plus routine Java usage and performance files being written. The only network traffic came from the analysis machine itself.
What To Do Now
The evidence does not indicate a threat. The file is unsigned and has few submitters, so download add-ons only from the project's official page or a trusted mod repository, and keep your antivirus enabled.
Where this verdict could be wrong2 caveats
- The file is a rarely submitted, unsigned Java add-on first seen on Oct 4, 2026, so there is little publisher or community history to confirm its origin.
- Sandbox tags note debug-environment and CPU-name checks, which some malware uses to evade analysis, though such checks are also common in ordinary Java runtimes and mod loaders.
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 64 antivirus engines that checked it flagged the file, including 18 major engines that reported it clean.
- The combined sandbox verdict was clean with no high-risk techniques.
- No matches in public malware databases or community detection rules.
- Network contacts were limited to the analysis machine's own background traffic.
- Java archive with few submitters, so its origin cannot be confirmed from publisher history.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 4 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 4isolated sandbox runs
- 16sandbox rule tags
- 4spawned processes
- 0network contacts
- 12filesystem & mutex artifacts
Includes the sandbox verdicts, 16 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 · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 24, 2026, 3:25 PM UTC
- SHA-256
6786d7fc200a6494e66b5047e8e44526fa30f3b5e7e598e60524dd48fd6182d6- SHA-1
8bf2921fa5a22bb9fdefdc95c3a14b7146d19fa1- MD5
da5160e7f0fe77a50a07d14d904d2e61
About this file
shoreline-addon-v1.0_nightly-b12-36a636b_1.21.11.jar is a JAR file of 620.8 kB.
- Type and size
- JAR · 620.8 kB
- Signer
- Not applicable
- First seen
- Oct 4, 2026On VirusTotal.
- Submitted by
- 6 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
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 shoreline-addon-v1.0_nightly-b12-36a636b_1.21.11.jar safe?
What is shoreline-addon-v1.0_nightly-b12-36a636b_1.21.11.jar?
How many antivirus engines detected shoreline-addon-v1.0_nightly-b12-36a636b_1.21.11.jar?
What is the SHA-256 hash of shoreline-addon-v1.0_nightly-b12-36a636b_1.21.11.jar?
Is it safe to open or run shoreline-addon-v1.0_nightly-b12-36a636b_1.21.11.jar?
How up to date is this analysis of shoreline-addon-v1.0_nightly-b12-36a636b_1.21.11.jar?
Community
Member reviews and reports for this exact file hash.