File scan report
Verdict Safe
Is Raven
No engine detected this JAR, and its completed sandbox run produced no malicious verdict despite two behavior mappings that warrant modest caution.
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 14d 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 65 antivirus engines that checked it flagged the file, including all 17 reporting major antivirus engines.
None of the 65 antivirus engines that checked it flagged the JAR, and the reporting major antivirus engines were uniformly silent. It mapped and T1543.002, but recorded no injected process, persistence indicator, or malicious child. All three listed contacts received host-reputation checks without a malicious or suspicious match, while two were identified as analysis-environment background traffic. Malware-specific research rules and other external intelligence provided no corroboration. The file is so retaining normal security software and obtaining it from a trusted source remain prudent.
What We Detected
None of the 65 antivirus engines that checked it flagged the JAR, including all 17 reporting major antivirus engines. No malware family was identified, and malware-specific research rules or external intelligence did not corroborate a threat.
Threat Behavior
One completed sandbox run returned no malicious verdict. It mapped T1055 and T1543.002, but no injected target, persistence indicator, malicious file it created, or known-harmful contacted host was recorded. Two of the three listed contacts were explicitly attributed to sandbox background traffic.
What To Do Now
The evidence supports ordinary use if the file came from an expected, trustworthy source. Because it is and eight dropped files lack individual saved verdicts, keep security software enabled and avoid granting unnecessary privileges.
Where this verdict could be wrong3 caveats
- The runtime mapping includes and T1543.002, techniques associated with process injection and service execution, but no injected target or persistence indicator was recorded.
- The file was first submitted very recently and has only five submissions, so long-term reputation is limited.
- Eight dropped files lack saved verdicts, leaving their individual safety unresolved.
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 65 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.
- All three listed network contacts were checked without a malicious or suspicious reputation match.
- No malicious file it created or malware-specific research rule was found.
- The file is and has limited submission history.
- The test run mapped possible process injection and service execution techniques, although no target process or persistence indicator was identified.
- Eight dropped files do not yet have individual saved verdicts.
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- 16sandbox rule tags
- 3spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
Includes the sandbox verdicts, 16 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 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 12, 2026, 9:31 AM UTC
- SHA-256
5cd2b3dcec209d7377cf45887fba2cd74a2e9e5ee7a59632ce0824918e457d02- SHA-1
611f968a1fdc1c9a9bb092eff8b5bce3effad3da- MD5
20a432d7ba573f7a29365f4f16b63a7f
About this file
RavenB4.jar is a JAR file of 2.2 MB.
- Type and size
- JAR · 2.2 MB
- Signer
- Not applicable
- First seen
- Oct 11, 2026On VirusTotal.
- Submitted by
- 5 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75), 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 RavenB4.jar safe?
What is RavenB4.jar?
How many antivirus engines detected RavenB4.jar?
What is the SHA-256 hash of RavenB4.jar?
Is it safe to open or run RavenB4.jar?
How up to date is this analysis of RavenB4.jar?
Community
Member reviews and reports for this exact file hash.