File scan report
Verdict Safe
Is Potion.
No antivirus engine detected Potion.jar, while one sandbox produced potentially offensive technique mappings without a malicious conclusion or supporting threat intelligence.
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 2mo ago
Chapter 02
Why we think so
2 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 64 antivirus engines that checked it returned no malicious or suspicious detection, including 17 major antivirus engines. One sandbox mapped activity to three offensive MITRE techniques, but issued no malicious conclusion, observed no network contacts, and found no confirmed malicious child, so those behavioral mappings remain uncorroborated.
The strongest signal is complete detection silence: 0 of the 64 antivirus engines that checked it flagged the sample, including all 17 major antivirus engines. One completed sandbox mapped activity to T1055, T1543.002, and T1562.001, but did not issue a malicious sandbox conclusion. Those mappings are concerning in isolation, yet the saved process evidence does not establish operator intent or a specific injection method. Seven dropped hashes were inspected without a malicious-child finding, although their individual status remains unknown. No CIRCL, MalwareBazaar, or YARAify corroboration was found, and no complete contacted-host reputation result is available.
What We Detected
Potion.jar received 0 malicious and 0 suspicious detections from 75 antivirus engines.
Threat Behavior
The sandbox did not issue a malicious conclusion, however, and the recorded evidence does not prove a specific injection method or hostile intent. No domains, IP addresses, or URLs were observed during that run. Seven dropped hashes were inspected without a malicious-child finding, but each child remains individually unclassified. A complete contacted-host reputation check was not saved.
What To Do Now
Use the file only if it came from an expected source, and keep security software enabled. If the origin is unfamiliar or the JAR requests elevated privileges, persistence, or protection changes, avoid running it and obtain a fresh copy from the official distributor.
Where this verdict could be wrong3 caveats
- The completed sandbox mapped activity to T1055, T1543.002, and T1562.001, which can indicate injection, service persistence, and impairment of defenses.
- All 7 inspected files it created have unknown individual verdicts, so the absence of a known-malicious dropped file is not equivalent to seven confirmed-benign children.
- The missing contacted-host reputation result means no saved host-reputation cross-check is available, although no network contacts were recorded during the observed run.
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 engines reported a malicious or suspicious detection.
- No sandbox returned a malicious verdict.
- No dropped file is known to be malicious.
- YARAify, CIRCL, and MalwareBazaar returned no hits.
- Sandbox mappings include T1055, T1543.002, and T1562.001.
- The missing contacted-host reputation result leaves host-reputation coverage 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- 15sandbox rule tags
- 3spawned processes
- 0network contacts
- 13filesystem & mutex artifacts
Includes 15 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
- Sep 8, 2026, 6:48 PM UTC
- SHA-256
e01ab29902e3476341a41c1fafc51d69530d5612339c9e9ea03ba95496043068- SHA-1
cbbfabc143f08fd83b648f036db0f75380c11ac9- MD5
e78bdf8b7e127ea1bc6ad2b678b03a47
About this file
Potion.jar is a JAR file of 10.3 kB.
- Type and size
- JAR · 10.3 kB
- Signer
- Not applicable
- First seen
- Aug 8, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned Updated
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 Potion.jar safe?
What is Potion.jar?
How many antivirus engines detected Potion.jar?
What is the SHA-256 hash of Potion.jar?
Is it safe to open or run Potion.jar?
How up to date is this analysis of Potion.jar?
Community
Member reviews and reports for this exact file hash.