File scan report
Verdict Safe
Is Kill
No antivirus engine detected this small JAR archive, although its short history (seen shortly before Sep 8, 2026) and lack of the test run warrant source verification.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Use the file only if its hash or release can be verified through the expected project source. Keep security protection enabled and rescan after the sample has accumulated more reputation.
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 Not run
- First seen 1mo ago
Chapter 02
Why we think so
5 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Static scanning produced no detections across 75 antivirus engines, including 17 reporting major antivirus engines. However, the file has only one recorded submission, and no completed sandbox or contacted-host assessment is available, so obtain it only from a trusted project source.
The strongest evidence is the complete absence of malicious or suspicious detections among 75 engines. Seventeen major antivirus engines reported no detection, and no engine family consensus exists. Research feeds also supplied no YARA, MalwareBazaar, or CIRCL hit. The sample is with just one submission, limiting reputation-based assurance. No behaviour in the test run was completed, and no complete contacted-host reputation result is available, so the conclusion rests primarily on static scanning.
What We Detected
None of the 64 antivirus engines that checked it flagged the archive, and all 17 reporting major antivirus engines returned no detection. No named malware family, hacking tool label, YARA rule, MalwareBazaar record, or CIRCL match was present.
Threat Behavior
No completed sandbox observation is available, so execution behavior cannot be characterized. The contacted-host cross-check was also not completed or saved, meaning no conclusion can be drawn about potential network destinations.
What To Do Now
Confirm that the JAR came from the expected developer or official project page before running it. Keep security software enabled, scan any newer copy again, and avoid launching it if the download source or requested permissions appear inconsistent with a game modification.
Where this verdict could be wrong3 caveats
- The file is and has only one recorded submission, so the 0/64 detection result lacks a long reputation history.
- No sandbox execution was completed, and the missing contacted-host reputation result means network reputation was not fully assessed.
- The five similarHashes entries are filetype-only matches and therefore provide little file-specific reassurance.
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/64 antivirus engines reported malicious or suspicious results.
- 17 major antivirus engines reported no detection.
- No confirmed hacking tool or test-file labels were present.
- YARAify returned 0 rules, while MalwareBazaar and CIRCL returned no hits.
- No brand mismatch or adversarial-input flag was detected.
- Only one source and one submission are recorded.
- The sample was first observed very recently.
- No completed sandbox execution is available.
- No complete contacted-host reputation result is available.
- JAR signing history is unavailable and code-signing assessment is not applicable here.
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. See every source
Chapter 03
Technical details
None of the 64 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 4 complete · 1 not run · 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
- Sep 8, 2026, 4:24 PM UTC
- SHA-256
3be6cf34a6ebc940abf862d0580729c004f0a8926e036d08729bbd3094ffac7d- SHA-1
7e9864f0d4785bd74b0f1b6767b707a16a210635- MD5
e18ed56d4e35160d46479c502f7dedb3
About this file
KillAura-by-Veni-1.21.11.jar is a ZIP file of 12.1 kB.
- Type and size
- ZIP · 12.1 kB
- Signer
- Not applicable
- First seen
- Sep 8, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75) and how widely the file has been seen.
Show the technical evidenceChapter 04
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is KillAura-by-Veni-1.21.11.jar safe?
What is KillAura-by-Veni-1.21.11.jar?
How many antivirus engines detected KillAura-by-Veni-1.21.11.jar?
What is the SHA-256 hash of KillAura-by-Veni-1.21.11.jar?
Is it safe to open or run KillAura-by-Veni-1.21.11.jar?
How up to date is this analysis of KillAura-by-Veni-1.21.11.jar?
Community
Member reviews and reports for this exact file hash.