File scan report
Verdict Safe
Is powhax-
All 65 antivirus engines that checked it avoided flagging this JAR, including 17 major antivirus engines, and the completed sandbox did not issue a malware finding.
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 6mo 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
Caution remains because execution mapped two offensive techniques and contacted an IP whose reputation was not fully checked.
The strongest evidence is broad antivirus agreement: none of the 65 antivirus engines that checked it flagged the file, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft. One completed sandbox produced no malware verdict and no confirmed malicious child, although four child verdicts remain unknown. Runtime mapping included and T1562.001, which warrants caution but is not sufficient by itself to establish harmful intent. The sample contacted 162.159.36.2 directly, and no complete host-reputation result is available because the contacted-host check was not saved. Research feeds produced no CIRCL, MalwareBazaar, or YARAify match, leaving no independent family attribution.
What We Detected
None of the 65 antivirus engines that checked it flagged the JAR, and all 17 participating major antivirus engines reported no detection. CIRCL, MalwareBazaar, and YARAify also returned no matching threat intelligence.
Threat Behavior
One completed sandbox did not issue a malware finding. It nevertheless mapped T1543.002 and T1562.001 and observed direct contact with 162.159.36.2. The host-reputation cross-check was not completed or saved, so that connection cannot be described as benign. Four child hashes were inspected without a confirmed malicious child, but their individual verdicts remain unknown.
What To Do Now
Use the file only if it came from the expected project or distribution channel.
Where this verdict could be wrong3 caveats
- The completed sandbox mapped and T1562.001, techniques associated with service execution and impairment of defenses.
- Direct contact with 162.159.36.2 triggered one of our behaviour rules, and the missing contacted-host reputation result means the host was not fully reputation-checked.
- The four written child hashes were inspected but have unknown individual verdicts, so their absence from the malicious count is not affirmative clearance.
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/65 engines reported malicious or suspicious findings.
- 17 major antivirus engines, including BitDefender, Kaspersky, ESET-NOD32, and Microsoft, reported no detection.
- No sandbox returned a malicious verdict after one completed sandbox run.
- No dropped file is known to be malicious across four inspected children.
- CIRCL, MalwareBazaar, and YARAify returned no hits.
- Runtime mapping includes and T1562.001.
- All four inspected child hashes have unknown individual verdicts.
- No applicable code-signing identity is available for this JAR.
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- 10sandbox rule tags
- 4spawned processes
- 0network contacts
- 11filesystem & mutex artifacts
Includes 10 mapped techniques, every process, file, registry and network entry and 2 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 · 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, 3:36 PM UTC
- SHA-256
fc37f179a4bd606f890fd79a48bf6caa7218e58ba9f176bee2ea10970586e83c- SHA-1
a33e27cd4013d1c7ad02f9fd42eec246e40d97c0- MD5
8d96569a5d29d07aca311510f203705a
About this file
powhax-1.6.7.jar is a JAR file of 78.8 kB.
- Type and size
- JAR · 78.8 kB
- Signer
- Not applicable
- First seen
- Apr 23, 2026On VirusTotal.
- Submitted by
- 12 distinct sources
First scanned
Includes every engine result (75) 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 powhax-1.6.7.jar safe?
What is powhax-1.6.7.jar?
How many antivirus engines detected powhax-1.6.7.jar?
What is the SHA-256 hash of powhax-1.6.7.jar?
Is it safe to open or run powhax-1.6.7.jar?
How up to date is this analysis of powhax-1.6.7.jar?
Community
Member reviews and reports for this exact file hash.