File scan report
Verdict Safe
Is Shama-
None of the 64 antivirus engines that checked it flagged this JAR, and its completed sandbox run produced no malicious verdict despite several uncorroborated MITRE technique…
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 64 flagged
- Flagged 0
- No detection 64
- No result 11
- Code signing Not applicable
- Test run Completed
- First seen 29d ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 64 antivirus engines that checked it detected the file, including 17 major antivirus engines, and the completed sandbox run did not produce a malicious verdict. Three offensive MITRE mappings deserve caution, but no injected target, persistence indicator, malicious child, or researcher rule corroborates them.
The strongest evidence is the absence of detections across 75 engines, with all 17 reporting major antivirus engines silent. One completed sandbox run returned a clean result and did not identify malicious execution. Although the runtime report mapped process injection, service persistence, and security-control impairment techniques, it recorded no injected process target or persistence indicator. The only recorded IP contact was explicitly attributed to sandbox background activity, while a complete host-reputation cross-check was not available. No malware-specific researcher rules, known malware-feed match, or verdict-backed malicious child supplied independent corroboration.
What We Detected
None of the 64 antivirus engines that checked it flagged the JAR, including all 17 major antivirus engines that reported a result. No malware family was identified, and researcher intelligence produced no malware-specific rule match or known malware-feed hit.
Threat Behavior
One completed sandbox run produced no malicious verdict. It mapped T1055, T1543.002, and T1562.001, but did not record an injected target process, persistence indicator, or malicious child. The observed IP contact was identified as analysis-environment background traffic, and no complete host-reputation cross-check is available. Six dropped files have no saved verdict, so they remain unresolved rather than proven benign.
What To Do Now
Use the file only if it came from the expected add-on source and its hash matches the publisher's value. Keep security software enabled, and reconsider execution if the application unexpectedly requests elevated permissions or attempts to alter security settings.
Where this verdict could be wrong3 caveats
- The sandbox mapped T1055, T1543.002, and T1562.001, which can represent injection, service persistence, and security-control impairment; however, no target process, persistence indicator, or malicious sandbox verdict corroborated them.
- The file was first observed on Sep 26, 2026 and has only eight submissions, so its history remains limited.
- Six dropped files lack saved verdicts, leaving their nature unresolved rather than establishing that they 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.
- None of the 64 antivirus engines that checked it flagged the file.
- All 17 reporting major antivirus engines returned no detection.
- The completed sandbox run produced no malicious verdict.
- No injected target process or persistence indicator was recorded.
- No malware-specific researcher rule, known malware-feed match, or malicious child verdict was found.
- The runtime report mapped possible process injection, service persistence, and security-control impairment techniques.
- The file has a relatively short 13-day observation history with eight submissions.
- No complete reputation cross-check is available for sample-attributed hosts, although the only recorded IP was sandbox background traffic.
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 16sandbox rule tags
- 3spawned processes
- 0network contacts
- 13filesystem & 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
16MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1055· Process injection
- T1059· Runs commands
- T1064
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1106
- T1129· Loads modules
- T1202
- T1518.001· Checks your AV
- T1543.002· Service install
- T1562.001· Disables security
- T1564· Hides artifacts
- T1564.001· Hides artifacts
- T1564.003· Hides artifacts
Observed activity
Processes started
3Programs the file ran, with their command lines.
javaw.exe"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.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\download.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\download.jar"
Files
13Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3524 - 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\880 - Written
C:\cmdlinestart.log
Show all 13 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/3553/coredump_filter - Written
/tmp/hsperfdata_root/3553 - Written
/var/log/auth.log.1.gz - Written
/var/log/kern.log.1.gz - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\5832 - Deleted
/tmp/hsperfdata_root/3553
Sandbox background — not the file
13The 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 process
gzip/bin/gzip - VM process
sh/bin/sh sh -c "\n\t\tinvoke-rc.d --quiet cups restart > /dev/null\n" logrotate_script "/var/log/cups/*log " - VM process
invoke-rc.d/usr/sbin/invoke-rc.d invoke-rc.d --quiet cups restart - VM process
runlevel/sbin/runlevel
Show all 13 entries for sandbox background — not the file
- VM process
systemctl/usr/bin/systemctl systemctl --quiet is-enabled cups.service - VM process
ls/usr/bin/ls ls /etc/rc[S2345].d/S[0-9][0-9]cups - VM process
systemctl/usr/bin/systemctl systemctl --quiet is-active cups.service - VM process
sh/bin/sh sh -c /usr/lib/rsyslog/rsyslog-rotate logrotate_script /var/log/syslog - VM process
rsyslog-rotate/usr/lib/rsyslog/rsyslog-rotate - VM process
systemctl/usr/bin/systemctl systemctl kill -s HUP rsyslog.service - VM host
162.159.36.2
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.
- cc8acfcbf1ec69eb7e4f…9e3023Not checkedno saved verdict
- 7497baedd6ed7530113c…2d1defNot checkedno saved verdict
Chapter 04
Technical details
None of the 64 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 9, 2026, 11:12 AM UTC
- SHA-256
ed64ac7c390aa013602ebdaaa7045064c01fdc32c7dec0f94b9db52ed6e1672d- SHA-1
76d5f2b56a505738544b6c783c89e2eed746d56c- MD5
5d28d149d02179ea9a659eeaf529fa69
About this file
Shama-addon-1.21.11.jar is a JAR file of 669.5 kB.
- Type and size
- JAR · 669.5 kB
- Signer
- Not applicable
- First seen
- Sep 26, 2026On VirusTotal.
- Submitted by
- 8 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
Antivirus consensus
0 of 64 engines flagged this file
11 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-233 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
- SentinelOneNo result
- 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 Shama-addon-1.21.11.jar safe?
What is Shama-addon-1.21.11.jar?
How many antivirus engines detected Shama-addon-1.21.11.jar?
What is the SHA-256 hash of Shama-addon-1.21.11.jar?
Is it safe to open or run Shama-addon-1.21.11.jar?
How up to date is this analysis of Shama-addon-1.21.11.jar?
Community
Member reviews and reports for this exact file hash.