Is GrimClient1.21.11-fabric.jar safe?
Zero detections across 75 engines despite sandbox process-injection mapping on a brand-new JAR.
No antivirus engine flagged the file. Sandbox observed three MITRE techniques but returned no malicious verdict and no malicious children or host contacts.
3764524e7ee5c2c854…c61c45833c588bRecommended 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.
No antivirus engine flagged the file. Sandbox observed three MITRE techniques but returned no malicious verdict and no malicious children or host contacts.
The complete absence of detections from 75 reporting engines, including 17 tier-1 engines, outweighs the sandbox mapping to T1055. The heuristic rule itself notes that the mapping does not prove injection or malicious intent. The file is rare and new, but no external intelligence or similar-hash history supports malice.
What We Detected
75 engines scanned the JAR; none returned a malicious or suspicious result. Sandbox execution recorded three MITRE techniques (T1055, T1543.002, T1562.001) and wrote several temporary files, yet the sandbox verdict remained clean and no malicious child files were produced.
Threat Behavior
The observed techniques are consistent with legitimate Java launchers or mod loaders that adjust process names or check CPU features. No C2 traffic, persistence mechanisms, or dropped malicious payloads were identified.
What To Do Now
Keep endpoint protection enabled. If the file originates from an untrusted source, obtain it from the official Fabric/GrimClient distribution channel instead.
- 0/75 engines flagged malicious
- no malicious dropped children
- no malicious sandbox verdict
- rare_new prevalence (single submission)
- sandbox mapped T1055 process injection
The file can be considered safe for use provided it is obtained from a trusted source; continue running current endpoint protection.
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
Complete1 signature or behavior rule 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
- 15MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 11filesystem & 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
GrimClient1.21.11-fabric.jar
3764524e7ee5c2c8543fdf44c44691253de2cf604d26f6e8ccc61c45833c588b
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
4980
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\4980
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>\4980
- 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\6896
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\5552
- /tmp/hsperfdata_root/3553
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- 219e07b54b192727ee3d…1fdcf2Never scannednever seen before
- 51729f64c2006c453e16…81c5ddNever scannednever seen before
- 0d24385422223a186796…a8fbbeNever 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 1sources 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
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: GrimClient1.21.11-fabric.jar — 3764524e7ee5c2c8543fdf44c44691253de2cf604d26f6e8ccc61c45833c588b
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: 4980 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\4980
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
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.
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"
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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- GrimClient1.21.11-fabric.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 796.4 KB
- Last analyzed
- Aug 10, 2026, 6:19 AM UTC
3764524e7ee5c2c8543fdf44c44691253de2cf604d26f6e8ccc61c45833c588bSafety & 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 GrimClient1.21.11-fabric.jar safe?
What is GrimClient1.21.11-fabric.jar?
How many antivirus engines detected GrimClient1.21.11-fabric.jar?
What is the SHA-256 hash of GrimClient1.21.11-fabric.jar?
Is it safe to open or run GrimClient1.21.11-fabric.jar?
How up to date is this analysis of GrimClient1.21.11-fabric.jar?
Community
Member reviews and reports for this exact file hash.