File scan report
Verdict Safe
Is Moid-
This Java add-on archive was flagged by none of the 65 antivirus engines that checked it, and its sandbox run showed only ordinary Java activity in the test run.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Use this add-on only if downloaded from its official source, and keep your antivirus protection 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 65 flagged
- Flagged 0
- No detection 65
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 7mo 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
The sandbox run returned a clean result, with only routine Java runtime file writes and no injection into other processes. It has circulated for about seven months among 18 submitters.
None of the 65 antivirus engines that checked it flagged the file, and all 18 major antivirus engines that analysed it reported it clean. The sandbox run returned a clean result and recorded only standard Java runtime artefacts such as performance-data and usage timestamp files. The only network contact was the analysis machine's own background traffic, and no complete host-reputation check is available. A defence-evasion technique label appeared without any matching artefact, which is common for legitimate software and not evidence of tampering. Code signing does not apply to this archive type, and no external threat databases list it.
What We Detected
No antivirus detections: none of the 65 antivirus engines that checked it flagged this Java archive, including Kaspersky, ESET, BitDefender and Microsoft. No public malware databases or community rules matched it, and it has been seen by 18 submitters over roughly seven months.
Threat Behavior
The sandbox run launched the archive with Java and returned a clean result. Observed activity was limited to normal Java runtime files and a command shell launching Java. No process injection, persistence or registry changes were recorded. The only network contact was background traffic from the analysis machine itself. Debug-environment and CPU checks were noted, which are common in Java applications and game add-ons.
What To Do Now
If you obtained this add-on from its official project page or a trusted mod repository, it appears fine to use. Keep your antivirus enabled, and avoid copies from unofficial reuploads.
Where this verdict could be wrong2 caveats
- Tags note debug-environment and CPU-name checks, which some malware uses for sandbox evasion, though game add-ons and Java runtimes commonly perform such checks too.
- Java add-on JARs can fetch code when it ran, which a single sandbox observation may not reveal.
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.
- The sandbox run returned a clean result with no injection or persistence.
- Seen by 18 different submitters over about seven months without detections.
- No matches in public malware databases or community malware rules.
- The file checks for debugging environments and the processor name, which some evasive software also does.
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- 10sandbox rule tags
- 4spawned processes
- 0network contacts
- 11filesystem & mutex artifacts
Includes the sandbox verdicts, 10 mapped techniques, every process, file, registry and network entry and 2 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
- Oct 16, 2026, 8:25 AM UTC
- SHA-256
52b55dd3395f6b5224b69be9fd129909b7af0a1d1c5581a419b4bca4527f5a35- SHA-1
faec84c83910973bdbbc71cc413b533b10efcc0f- MD5
b7484c4cef0ed468e25b3f361e4124c2
About this file
Moid-Addon-1.5.jar is a JAR file of 171.0 kB.
- Type and size
- JAR · 171.0 kB
- Signer
- Not applicable
- First seen
- Mar 23, 2026On VirusTotal.
- Submitted by
- 18 distinct sources
First scanned Updated
Verdict history
- Not fully confirmed
- Safeafter the analysis was completed
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Includes every engine result (75) 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 Moid-Addon-1.5.jar safe?
What is Moid-Addon-1.5.jar?
How many antivirus engines detected Moid-Addon-1.5.jar?
What is the SHA-256 hash of Moid-Addon-1.5.jar?
Is it safe to open or run Moid-Addon-1.5.jar?
How up to date is this analysis of Moid-Addon-1.5.jar?
Community
Member reviews and reports for this exact file hash.