Is Exodar-Addon-1.0.1-1.21.11.jar safe?
No antivirus engine detected this JAR, while one sandbox produced uncorroborated process-injection and defense-impairment mappings that warrant ordinary source verification.
The file received no detections from 75 antivirus engines, including 17 tier-1 engines, and no sandbox issued a malware conclusion. One runtime record mapped activity to T1055 and T1562.001, so the file should still be obtained from the addon’s official source and used with protection enabled.
894fc0fdf6e598c10d…fb84ca912a367cRecommended 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 file received no detections from 75 antivirus engines, including 17 tier-1 engines, and no sandbox issued a malware conclusion. One runtime record mapped activity to T1055 and T1562.001, so the file should still be obtained from the addon’s official source and used with protection enabled.
None of 75 antivirus engines flagged the JAR, and all 17 reporting tier-1 engines were silent. One completed sandbox mapped activity to T1055 and T1562.001, but it did not issue a malware conclusion, and the process-injection heuristic explicitly says the exact method and intent were not proven. No known-malware, CIRCL, or YARA rule match corroborates those behavioral mappings. Four dropped hashes were inspected without a malicious child finding, although their individual dispositions remain unknown. No network contacts were recorded, but a complete contacted-host reputation result was not saved. Overall, the broad detection silence outweighs the single uncorroborated behavioral heuristic, with some residual caution appropriate.
What We Detected
The JAR was not flagged by any of 75 antivirus engines. This includes 17 tier-1 engines, and there was no family consensus, hacktool confirmation, known-malware database hit, CIRCL hit, or YARA rule match.
Threat Behavior
One completed sandbox mapped activity to MITRE T1055 and T1562.001. These mappings can indicate process injection and impairment of defenses, but the saved evidence does not prove the exact mechanism or malicious intent, and the sandbox did not issue a malware conclusion. Four written child hashes were inspected without a malicious result, although all four remain individually unknown. The run recorded no domains, IP addresses, or URLs; however, no complete host-reputation cross-check was saved.
What To Do Now
Install the addon only if its SHA-256 matches the release from the project’s official distribution channel. Keep antivirus and endpoint protection enabled, and avoid granting the JAR elevated privileges unless the publisher clearly documents why they are required.
Where this verdict could be wrong3 caveats
- The completed sandbox mapped activity to T1055 and T1562.001, techniques associated with process injection and impairment of defenses; the evidence does not establish the exact mechanism or intent.
- All four dropped children have unknown verdicts, so droppedChildren.hasMaliciousChild=false is not equivalent to four confirmed-benign children.
- No code-signing assurance is available because signing.applicable=false for this JAR.
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 detected the file
- 17 tier-1 engines reported no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- YARAify, MalwareBazaar, and CIRCL returned no hits
- Sandbox mapping to MITRE T1055 process injection
- Sandbox mapping to MITRE T1562.001 impairment of defenses
- Four dropped child hashes remain individually unknown
- No complete contacted-host reputation result is available
Use only a hash-matching copy from the addon’s official release channel and keep endpoint protection enabled. Reassess if the project cannot account for the T1055 or T1562.001 mappings.
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
- 13MITRE ATT&CK techniques
- 6spawned 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
Exodar-Addon-1.0.1-1.21.11.jar
894fc0fdf6e598c10dce5a06764345a9e63ed61092fe0d5043fb84ca912a367c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\java.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
3168
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3168
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>\3168
- 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\6744
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\4488
- /tmp/hsperfdata_root/3546
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- d4a737cb79332fac4762…ed0cf7Never scannednever seen before
- 4305596231459dd68cff…352c95Never 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
- 8sources 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 9 times from 8 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Exodar-Addon-1.0.1-1.21.11.jar — 894fc0fdf6e598c10dce5a06764345a9e63ed61092fe0d5043fb84ca912a367c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.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: 3168 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3168
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\java.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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Exodar-Addon-1.0.1-1.21.11.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 67.4 KB
- Last analyzed
- Sep 8, 2026, 3:28 PM UTC
894fc0fdf6e598c10dce5a06764345a9e63ed61092fe0d5043fb84ca912a367cSafety & 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 Exodar-Addon-1.0.1-1.21.11.jar safe?
What is Exodar-Addon-1.0.1-1.21.11.jar?
How many antivirus engines detected Exodar-Addon-1.0.1-1.21.11.jar?
What is the SHA-256 hash of Exodar-Addon-1.0.1-1.21.11.jar?
Is it safe to open or run Exodar-Addon-1.0.1-1.21.11.jar?
How up to date is this analysis of Exodar-Addon-1.0.1-1.21.11.jar?
Community
Member reviews and reports for this exact file hash.