Is meteorextras-1.4.1+1.21.11.jar safe?
No antivirus engine detected this JAR, and its completed sandbox run produced no malicious conclusion, though two offensive-associated techniques warrant source verification.
The sample drew no detections from 75 antivirus engines, including 17 tier-1 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 children, or external intelligence matches.
633c53fefbaf2230dc…d7263e143f6667Recommended 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.
The sample drew no detections from 75 antivirus engines, including 17 tier-1 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 children, or external intelligence matches.
No engine flagged the sample among 75 antivirus products, and all 17 tier-1 engines reported no detection. One completed sandbox run did not produce a malicious conclusion or record any contacted domains, IP addresses, or URLs. It did record T1543.002 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 75 antivirus engines flagged the JAR, including 17 tier-1 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 endpoint protection enabled, and avoid granting the JAR unnecessary administrative privileges.
Where this verdict could be wrong3 caveats
- The runtime record includes T1543.002 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 dropped children have unknown verdicts rather than confirmed benign results.
- contactedHosts=null 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/75 antivirus engines reported a malicious or suspicious result.
- All 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false in one completed sandbox run.
- No domains, IP addresses, or URLs were recorded by the sandbox.
- No CIRCL, MalwareBazaar, or YARAify match was found.
- Runtime evidence includes offensive-associated techniques T1543.002 and T1562.001.
- Five inspected child hashes have unknown individual verdicts.
- contactedHosts=null leaves host-reputation coverage unavailable.
Use only a copy obtained from the mod's official distribution channel and verify SHA-256 633c53fefbaf2230dc0bc2dc7729eeaeca237b5f4b6bf2a629d7263e143f6667. Keep endpoint protection enabled.
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
- 10MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 13filesystem & 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
meteorextras-1.4.1+1.21.11.jar
633c53fefbaf2230dc0bc2dc7729eeaeca237b5f4b6bf2a629d7263e143f6667
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\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
6236
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6236
04Isolated runtime analysis - Written fileObserved
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.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>\6236
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
- 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\7152
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\5924
- /tmp/hsperfdata_root/5013
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- 89d15b8516e93b23bba6…b45e1cNever scannednever seen before
- 5abf77a9c7c587b12c95…0f85d9Never scannednever seen before
- c1de3a9376fdaef0ba6a…308b70Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 44a3bab2c338e3bca24c…d3b9e7Never 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
- 57sources 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 been submitted 64 times from 57 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: meteorextras-1.4.1+1.21.11.jar — 633c53fefbaf2230dc0bc2dc7729eeaeca237b5f4b6bf2a629d7263e143f6667
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: 6236 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6236
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- meteorextras-1.4.1+1.21.11.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 72.9 KB
- Last analyzed
- Sep 8, 2026, 4:05 PM UTC
633c53fefbaf2230dc0bc2dc7729eeaeca237b5f4b6bf2a629d7263e143f6667Safety & 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 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.