Is meteor-client-26.2-23.jar safe?
No antivirus engine detected this widely submitted JAR, although one sandbox mapped several offensive techniques and made an incompletely reputation-checked direct-IP connection.
All 74 antivirus engines were silent, including 17 tier-1 engines, and no malicious sandbox verdict or malicious child was recorded. One runtime observation mapped three offensive techniques and contacted 162.159.36.2, so the file should still be obtained from its official release channel and kept under normal endpoint protection.
aee10fbfcf6932ffc2…abc71460891142Recommended 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 74 antivirus engines were silent, including 17 tier-1 engines, and no malicious sandbox verdict or malicious child was recorded. One runtime observation mapped three offensive techniques and contacted 162.159.36.2, so the file should still be obtained from its official release channel and kept under normal endpoint protection.
The strongest evidence is the complete absence of detections across 74 engines, including 17 tier-1 products. The file has also appeared from 331 sources in six days, which is more consistent with rapidly distributed commodity software than an isolated sample. One sandbox mapped T1055, T1543.002, and T1562.001, but it issued no malicious runtime verdict and recorded no persistence indicators. The direct-IP contact to 162.159.36.2 remains unresolved because a complete host-reputation check was not saved. Nine written or dropped hashes were inspected without a malicious child finding, though their individual verdicts remain unknown. Overall, the runtime cautions reduce confidence but do not outweigh the broad engine silence and lack of corroborating intelligence.
What We Detected
The JAR received 0 detections from 74 antivirus engines, with all 17 reporting tier-1 engines showing no detection. It was submitted 354 times by 331 sources within six days, and neither YARAify nor MalwareBazaar supplied corroborating malware intelligence.
Threat Behavior
One sandbox observation mapped activity to T1055, T1543.002, and T1562.001. These are security-relevant technique mappings, but the sandbox did not issue a malicious verdict or record persistence indicators. The sample contacted 162.159.36.2 directly; because contactedHosts is unavailable, no complete reputation conclusion can be made about that endpoint. Nine child hashes were inspected without a malicious finding, although all remain individually unclassified.
What To Do Now
Use the file only if it came from the project's official release channel and its hash matches the publisher's release information. Keep endpoint protection enabled, and avoid granting unnecessary elevated privileges or network access.
Where this verdict could be wrong3 caveats
- The runtime mapping includes T1055, T1543.002, and T1562.001, techniques associated with process injection, service modification, and impaired defenses.
- MalwareTips.Synth.DirectIpC2 fired for 162.159.36.2, and contactedHosts=null leaves that endpoint without a complete reputation result.
- All nine dropped children have unknown verdicts, so droppedChildren.hasMaliciousChild=false does not establish that those files 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/74 antivirus engines reported a malicious or suspicious result.
- engines.tier1ReportedClean=17 and engines.tier1Malicious=0.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false across 9 inspected hashes.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false.
- One sandbox mapped runtime activity to T1055, T1543.002, and T1562.001.
- Direct-IP contact to 162.159.36.2 lacks a complete host-reputation cross-check.
- The file was first observed only 6 days ago.
- Nine dropped child hashes remain individually unclassified.
Download this JAR only from the project's official release channel and verify its SHA-256 before use. Keep endpoint protection enabled and monitor unexpected privilege, service, or network activity.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
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
- 18MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 16filesystem & 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
meteor-client-26.2-23.jar
aee10fbfcf6932ffc22f4ca4f4c317492159f6ae588fe332b5abc71460891142
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.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
1312
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\1312
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
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\1312
- 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\6516
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\1400
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- a150601fda151d747cce…44ae8fNever scannednever seen before
- 9c51b8768c9d9ccf6f3f…f37cc0Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 624ba29561caba4c31fa…f89d0fNever scannednever seen before
- a813d9f7ffac9d85e6e4…8e7286Never scannednever seen before
- 61625fd8b084f70f242d…55abd2Never scannednever seen before
- 50c82f36208ed8040447…2d7843Never scannednever seen before
- 8e8711854186c68e2368…4a3c7cNever scannednever seen before
- 759aafcfa2395ce1b800…2af0f7Never 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.
- 2rule hits recorded
- 0 / 74engines flagged
- 331sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 354 times from 331 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: meteor-client-26.2-23.jar — aee10fbfcf6932ffc22f4ca4f4c317492159f6ae588fe332b5abc71460891142
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 1312 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\1312
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
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.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.jar"The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- meteor-client-26.2-23.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 4.8 MB
- Last analyzed
- Sep 19, 2026, 9:27 PM UTC
aee10fbfcf6932ffc22f4ca4f4c317492159f6ae588fe332b5abc71460891142Safety & 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 meteor-client-26.2-23.jar safe?
What is meteor-client-26.2-23.jar?
How many antivirus engines detected meteor-client-26.2-23.jar?
What is the SHA-256 hash of meteor-client-26.2-23.jar?
Is it safe to open or run meteor-client-26.2-23.jar?
How up to date is this analysis of meteor-client-26.2-23.jar?
Community
Member reviews and reports for this exact file hash.