File scan report
Verdict Safe
Is Meteor Additions- 1. 2. 0 (1). jar safe? Yes, no threats found.
All 63 antivirus engines that checked it were free of detections, including the reporting major antivirus engines, and one sandbox produced no malicious verdict.
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 63 flagged
- Flagged 0
- No detection 63
- No result 12
- Code signing Not applicable
- Test run Completed
- First seen 9mo ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The strongest evidence is the absence of detections across 75 antivirus engines, with no major antivirus engines identifying a threat. One completed sandbox run did not assign a malicious verdict and recorded no persistence indicators or registry modifications. It nevertheless mapped activity to and observed a direct connection to 162.159.36.2. Because contactedHosts is null, that address cannot be characterized as benign or malicious from the available host-reputation evidence. No external intelligence hit or malicious file it created corroborates the behavioral concerns, making them insufficient to outweigh the broader evidence.
What We Detected
None of the 63 antivirus engines that checked it flagged the JAR, and no major antivirus engines flagged it. External research sources also produced no CIRCL, MalwareBazaar, or YARAify match.
Threat Behavior
One sandbox run mapped T1543.002 and T1562.001 and observed a direct connection to 162.159.36.2. The run produced no malicious sandbox verdict, persistence indicator, or registry modification. Host reputation was not completely checked because contactedHosts is unavailable, and the six files it created remain individually unclassified despite no known malicious child being found.
What To Do Now
Obtain the JAR from its official project or release page and verify its SHA-256 hash before running it. Keep security software enabled and use an isolated environment if the download source cannot be confirmed.
Where this verdict could be wrong3 caveats
- The sandbox's offensive-technique list includes and T1562.001, techniques associated with service manipulation and impairment of defenses.
- The sandbox contacted 162.159.36.2 directly, while the missing contacted-host reputation result means its reputation was not completely checked.
- All 6 inspected files it created have unknown verdicts, so the absence of a known-malicious dropped file does not establish that they are benign.
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/63 antivirus engines reported a malicious or suspicious result.
- No major antivirus engines flagged it, with 16 major antivirus engines reporting no detection.
- No sandbox returned a malicious verdict.
- No dropped file is known to be malicious.
- No CIRCL, MalwareBazaar, or YARAify hit was found.
- Sandbox activity mapped to offensive techniques and T1562.001.
- Direct connection to 162.159.36.2 triggered one of our behaviour rules.
- No complete contacted-host reputation result is available.
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- 6sandbox rule tags
- 4spawned processes
- 0network contacts
- 13filesystem & mutex artifacts
Includes 6 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 63 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, 3:46 PM UTC
- SHA-256
7c9c02bd31d5bc2a52c2168ac8b4590f2be53ff6281af2a14d82bbff51869754- SHA-1
438a6de4951bf79abd86fb5c489cfeea6b769b27- MD5
524b84221c5fbad16e45d1721236a0f5
About this file
MeteorAdditions-1.2.0 (1).jar is a JAR file of 874.6 kB.
- Type and size
- JAR · 874.6 kB
- Signer
- Not applicable
- First seen
- Jan 22, 2026On VirusTotal.
- Submitted by
- 64 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 MeteorAdditions-1.2.0 (1).jar safe?
What is MeteorAdditions-1.2.0 (1).jar?
How many antivirus engines detected MeteorAdditions-1.2.0 (1).jar?
What is the SHA-256 hash of MeteorAdditions-1.2.0 (1).jar?
Is it safe to open or run MeteorAdditions-1.2.0 (1).jar?
How up to date is this analysis of MeteorAdditions-1.2.0 (1).jar?
Community
Member reviews and reports for this exact file hash.