Is meteorist-1.21.11-2.jar safe?
No antivirus engine detected this established JAR, and its substantial submission history outweighs two uncorroborated behavioral technique classifications.
All 75 antivirus engines avoided flagging this JAR, including 17 high-trust engines, despite hundreds of prior submissions. One sandbox mapped activity to two offensive MITRE techniques, but produced no malicious verdict, persistence indicator, malicious child, or network contact.
f83fbd14d545f69d2e…273db51e2ad7a4Recommended next actions
Before opening or running
Open or run it only when its publisher and download source have been independently verified.
If you already opened or ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 antivirus engines avoided flagging this JAR, including 17 high-trust engines, despite hundreds of prior submissions. One sandbox mapped activity to two offensive MITRE techniques, but produced no malicious verdict, persistence indicator, malicious child, or network contact.
The strongest evidence is the complete absence of detections across 75 engines, with all 17 reporting high-trust engines finding nothing actionable. The file is also well established, having appeared through 572 sources and 648 submissions over 226 days. A completed sandbox run did not issue a malicious verdict or record persistence, registry changes, or network contacts. It did map activity to T1543.002 and T1562.001, but those classifications lack corroboration from engines, external intelligence, or known-malicious child files. The three written child hashes remain individually unresolved, so they provide neither positive nor negative confirmation.
What We Detected
None of 75 antivirus engines flagged the JAR, including all 17 reporting high-trust engines. The sample has also accumulated 648 submissions from 572 sources over 226 days, which provides meaningful exposure without corresponding detection growth. CIRCL, MalwareBazaar, and YARAify supplied no corroborating threat intelligence.
Threat Behavior
One completed sandbox run mapped activity to T1543.002 and T1562.001, but it did not produce a malicious sandbox verdict, persistence indicator, registry modification, or observed network contact. Three written child hashes were inspected without a malicious child finding, although each child's individual status remains unresolved. Because contactedHosts is unavailable, no independent host-reputation result exists; however, the sandbox contact lists themselves were empty.
What To Do Now
Use the JAR only if it came from the expected project or distribution channel, and keep endpoint protection enabled. If its source is uncertain, verify the SHA-256 hash and test it in an isolated environment before granting elevated permissions.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques contains T1543.002 and T1562.001, including service manipulation and impairment-of-defenses classifications.
- droppedChildren.rollup reports 3 unknown children, so their absence from the malicious count is not equivalent to confirmed benign status.
- contactedHosts=null, although the sandbox recorded no contacted domains, IPs, or URLs; no complete host-reputation result is available.
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/75 engines reported malicious or suspicious results.
- All 17 reporting tier-1 engines were non-detecting.
- One sandbox produced no malicious verdict.
- No malicious dropped child was identified among 3 inspected hashes.
- The sample has 648 submissions from 572 sources over 226 days.
- Sandbox mapping included T1543.002 and T1562.001.
- Three dropped child hashes have unknown individual verdicts.
- JAR signing was not applicable, leaving no publisher identity to verify.
- No completed contacted-host reputation cross-check is available.
The evidence supports normal use when the JAR came from the intended project source. Keep security protection enabled and avoid granting unnecessary privileges.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 6MITRE ATT&CK techniques
- 9spawned processes
- 0network contacts
- 10filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
meteorist-1.21.11-2.jar
f83fbd14d545f69d2ebe4be3055d9ddbff03466ff1998cf76f273db51e2ad7a4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\runtime.jar"" >> C:\cmdlinestart.log 2>&1
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
6880
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6880
04Isolated runtime analysis - Written fileObserved
17dfc292991c8786.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6880
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
- C:\Users\user\AppData\Local\Temp\hsperfdata_user
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\5880
- C:\cmdlinestart.log
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\6500
- /tmp/hsperfdata_root/5003
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- ab31380a6d6fb674e48e…15e845Never scannednever seen before
- 3f8096f14540c8e18e4e…ad10b8Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 572sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 572 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 648 times from 572 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: meteorist-1.21.11-2.jar — f83fbd14d545f69d2ebe4be3055d9ddbff03466ff1998cf76f273db51e2ad7a4
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\runtime.jar"" >> C:\cmdlinestart.log 2>&1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 6880 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6880
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 17dfc292991c8786.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- meteorist-1.21.11-2.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 392.4 KB
- Last analyzed
- Sep 8, 2026, 3:58 PM UTC
f83fbd14d545f69d2ebe4be3055d9ddbff03466ff1998cf76f273db51e2ad7a4Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or run it only when its publisher and download source have been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is meteorist-1.21.11-2.jar safe?
What is meteorist-1.21.11-2.jar?
How many antivirus engines detected meteorist-1.21.11-2.jar?
What is the SHA-256 hash of meteorist-1.21.11-2.jar?
Is it safe to open or run meteorist-1.21.11-2.jar?
How up to date is this analysis of meteorist-1.21.11-2.jar?
Community
Member reviews and reports for this exact file hash.