File scan report
Verdict Safe
Is Exodar-
No antivirus engine identified a threat, and the completed sandbox run lacked a malicious verdict despite two cautionary behavioral technique mappings.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the project's own website.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 65 flagged
- Flagged 0
- No detection 65
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 5mo ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 65 antivirus engines that checked it flagged this JAR, including all 17 reporting major antivirus engines, and one completed sandbox run produced no malicious verdict. Two offensive-technique mappings deserve awareness, but they lack corroboration from engine detections, malicious hosts, file it created findings, or external research rules.
The strongest evidence is broad antivirus agreement: 0 of the 65 antivirus engines that checked it reported the file as malicious or suspicious, with all 17 reporting major antivirus engines remaining silent. One completed sandbox run did not assign a malicious verdict, and its only observed domain was fully checked without a reputation hit. None of the four inspected child hashes was identified as malicious, although their individual verdicts remain unresolved. No corroboration came from external malware intelligence or researcher-authored YARA rules, leaving the behavioral mappings as isolated cautionary signals.
What We Detected
None of the 65 antivirus engines that checked it flagged the JAR as malicious or suspicious. This includes 17 reporting major antivirus engines, and there was no named-family consensus or hacking tool confirmation. External checks also returned no malware-repository hit and no YARAify rules.
Threat Behavior
One completed sandbox run did not produce a malicious verdict. The sole observed domain, assets.msn.com, was covered by the host-reputation check and had no malicious or suspicious cache entry. Four written child hashes were inspected without a malicious finding, though each child remains individually unresolved.
What To Do Now
Use the add-on only if it came from the expected project or distribution page, and keep security software enabled. If its source or requested permissions are unexpected, verify the SHA-256 hash with the publisher before launching it.
Where this verdict could be wrong2 caveats
- The runtime mapping includes and T1562.001, techniques associated with process injection and defense impairment, even though no malicious sandbox verdict corroborated them.
- All four entries under the dropped-file list have unknown verdicts, so the absence of a known-malicious dropped file reflects no identified malicious child rather than affirmative benign classifications.
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/65 engines reported malicious or suspicious results.
- All 17 reporting major antivirus engines were undetected.
- One completed sandbox run had no malicious verdict.
- The sole observed host was fully reputation-checked with no hit.
- No MalwareBazaar or YARAify corroboration was present.
- Behavior in the test run mapped to process injection.
- Behavior in the test run mapped to defense impairment.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 13sandbox rule tags
- 4spawned processes
- 0network contacts
- 11filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
13MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1055· Process injection
- T1059· Runs commands
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1106
- T1129· Loads modules
- T1202
- T1518.001· Checks your AV
- T1562.001· Disables security
- T1564· Hides artifacts
- T1564.001· Hides artifacts
- T1564.003· Hides artifacts
Observed activity
Processes started
4Programs the file ran, with their command lines.
java.exe"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\download.jar"cmd.exeC:\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>&1java.exe"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"java/usr/bin/java -jar /tmp/download.jar
Files
11Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3168 - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user\6744 - Written
C:\cmdlinestart.log
Show all 11 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/3546/coredump_filter - Written
/tmp/hsperfdata_root/3546 - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\4488 - Deleted
/tmp/hsperfdata_root/3546
Sandbox background — not the file
3The analysis machine's own processes and connections, recorded in every run.
- VM process
icacls.exeC:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M - VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM host
assets.msn.com
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache. 2 have no saved verdict and were not checked; that is missing coverage, not a finding.
- d4a737cb79332fac4762…ed0cf7Not checkedno saved verdict
- 4305596231459dd68cff…352c95Not checkedno saved verdict
Chapter 04
Technical details
None of the 65 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 7, 2026, 7:34 AM UTC
- SHA-256
894fc0fdf6e598c10dce5a06764345a9e63ed61092fe0d5043fb84ca912a367c- SHA-1
5699cdac6401b52fd55cdc5dbcea2a03b24b0a04- MD5
6e4d632353bceca3f5e502ac675c8ebf
About this file
Exodar-Addon-1.0.1-1.21.11.jar is a JAR file of 69.0 kB.
- Type and size
- JAR · 69.0 kB
- Signer
- Not applicable
- First seen
- May 15, 2026On VirusTotal.
- Submitted by
- 15 distinct sources
First scanned Updated
Antivirus consensus
0 of 65 engines flagged this file
10 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-234 engines0flagged
- Low-trust13 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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.