File scan report
Verdict Safe
Is meteorextras-
No antivirus engine detected this JAR, and its completed sandbox run produced no malicious conclusion, though two offensive-associated techniques warrant source verification.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made 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 7mo ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The sample drew no detections from 75 antivirus engines, including 17 major antivirus engines, and one completed sandbox run produced no malicious conclusion. Two offensive-associated techniques were recorded, but there were no observed network contacts, confirmed malicious files it created, or external intelligence matches.
One completed sandbox run did not produce a malicious conclusion or record any contacted domains, IP addresses, or URLs. It did record and T1562.001, which are meaningful counter-signals but are not corroborated by detections, persistence indicators, or hostile network activity. Five written-file hashes were inspected without a confirmed malicious child, although their individual verdicts remain unknown. Researcher-curated sources supplied no YARA, CIRCL, or MalwareBazaar match, while 57 submitters and 64 submissions indicate moderate circulation.
What We Detected
None of the 64 antivirus engines that checked it flagged the JAR, including 17 major antivirus engines. Researcher-curated checks also returned no YARAify rules, CIRCL match, or MalwareBazaar entry.
Threat Behavior
One completed sandbox run produced no malicious conclusion and recorded no contacted domains, IP addresses, or URLs. It did associate the execution with T1543.002 and T1562.001, so those behaviors remain cautionary signals. Five child hashes were inspected without a confirmed malicious result, but each child still lacks a conclusive individual verdict. No complete contacted-host reputation result was saved.
What To Do Now
Obtain the mod from its official project page or another trusted repository and verify the SHA-256 hash before installation. Keep security software enabled, and avoid granting the JAR unnecessary administrative privileges.
Where this verdict could be wrong3 caveats
- The runtime record includes and T1562.001, techniques associated with service activity and impairment of defenses, so the sample should still come from a trusted mod source.
- All five inspected files it created have unknown verdicts rather than confirmed benign results.
- The missing contacted-host reputation result means no saved host-reputation cross-check is available, although the sandbox recorded no network contacts.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/64 antivirus engines reported a malicious or suspicious result.
- No sandbox returned a malicious verdict in one completed sandbox run.
- No domains, IP addresses, or URLs were recorded by the sandbox.
- No CIRCL, MalwareBazaar, or YARAify match was found.
- Evidence from the test run includes offensive-associated techniques and T1562.001.
- Five inspected child hashes have unknown individual verdicts.
- The missing contacted-host reputation result leaves host-reputation coverage unavailable.
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
- 13filesystem & mutex artifacts
Includes 10 mapped techniques, every process, file, registry and network entry and 2 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, 4:05 PM UTC
- SHA-256
633c53fefbaf2230dc0bc2dc7729eeaeca237b5f4b6bf2a629d7263e143f6667- SHA-1
1161c59ac5b7ae4b04d9fe40e54382ed93b9eabb- MD5
859e036c01f3cc49f182f1c94ef8b203
About this file
meteorextras-1.4.1+1.21.11.jar is a JAR file of 74.7 kB.
- Type and size
- JAR · 74.7 kB
- Signer
- Not applicable
- First seen
- Mar 19, 2026On VirusTotal.
- Submitted by
- 57 distinct sources
First scanned
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 meteorextras-1.4.1+1.21.11.jar safe?
What is meteorextras-1.4.1+1.21.11.jar?
How many antivirus engines detected meteorextras-1.4.1+1.21.11.jar?
What is the SHA-256 hash of meteorextras-1.4.1+1.21.11.jar?
Is it safe to open or run meteorextras-1.4.1+1.21.11.jar?
How up to date is this analysis of meteorextras-1.4.1+1.21.11.jar?
Community
Member reviews and reports for this exact file hash.