File scan report
Verdict Safe
Is Anti
None of the 64 antivirus engines that checked it flagged this established JAR, and its completed sandbox run found no malicious verdict despite two unsupported behavioral 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 64 flagged
- Flagged 0
- No detection 64
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 5y 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 flagged the file, including all 17 major antivirus engines represented in the results.
The strongest evidence is the absence of any detection among 74 engines, with no major or independent engine flags. A completed sandbox run returned clean and did not record network communication or persistence. It mapped and T1562.001, but no injected target was identified and the process list mainly reflects Java execution and analysis instrumentation. No malware-specific YARA rules, MalwareBazaar record, malicious child verdict, or named threat family corroborates those mappings. The five files it created lack saved verdicts, and no complete host-reputation cross-check is available, so those areas remain coverage limitations rather than adverse evidence.
What We Detected
None of the 64 antivirus engines that checked it flagged AntiAntiXray-1.8.jar, including the major antivirus engines represented in the results. No named malware family, malware-specific YARA rule, or MalwareBazaar record was found.
Threat Behavior
One completed sandbox run returned clean and recorded no sample network contacts or persistence indicators. It mapped T1055 and T1562.001, but no injected process, injection method, or concrete security-control disabling action was identified. The observed Java commands also include analysis instrumentation, which limits the weight of these broad mappings.
What To Do Now
The evidence supports normal use if the JAR came from the expected Minecraft server-plugin source. Keep security software enabled, retain a backup of the server, and test third-party plugins in a restricted environment before production deployment.
Where this verdict could be wrong3 caveats
- The sandbox mapped possible process injection and security-control impairment, although it identified neither an injected process nor a concrete disabling action.
- Five written or dropped files have no saved verdict, so their safety was not independently established.
- No complete contacted-host reputation cross-check is available, although the completed sandbox recorded no sample network contacts.
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 major antivirus engines represented in the results reported no detection.
- The completed sandbox run returned clean and recorded no sample network contacts or persistence.
- No malware-specific researcher rules or known malware-exchange record matched the hash.
- The file has been observed for more than five years across 68 submitting sources.
- The test run mapped possible process injection and security-control impairment without identifying a target or concrete disabling action.
- Five generated or dropped files do not have saved verdicts.
- A complete reputation check for contacted hosts is unavailable.
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- 12sandbox rule tags
- 3spawned processes
- 0network contacts
- 11filesystem & mutex artifacts
Includes the sandbox verdicts, 12 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 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 11, 2026, 2:22 PM UTC
- SHA-256
2abf1c0a64e256f04134d5fd98cb9e8fc11becab26ac9477aabc169ea3669801- SHA-1
534dd237a8d953485f4a04ef19ef944aa36f35af- MD5
2ef21fbec654411bfae3ba70ef731d9b
About this file
AntiAntiXray-1.8.jar is a JAR file of 47.4 kB.
- Type and size
- JAR · 47.4 kB
- Signer
- Not applicable
- First seen
- Aug 30, 2021On VirusTotal.
- Submitted by
- 68 distinct sources
First scanned
Includes every engine result (74), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is AntiAntiXray-1.8.jar safe?
What is AntiAntiXray-1.8.jar?
How many antivirus engines detected AntiAntiXray-1.8.jar?
What is the SHA-256 hash of AntiAntiXray-1.8.jar?
Is it safe to open or run AntiAntiXray-1.8.jar?
How up to date is this analysis of AntiAntiXray-1.8.jar?
Community
Member reviews and reports for this exact file hash.