Is powhax-1.6.7.jar safe?
No antivirus engine identified a threat, while limited runtime concerns include two offensive techniques and one direct-IP connection lacking a completed reputation check.
All 75 antivirus engines avoided flagging this JAR, including 17 high-trust engines, and the completed sandbox did not issue a malware finding. Caution remains because execution mapped two offensive techniques and contacted an IP whose reputation was not fully checked.
fc37f179a4bd606f89…ea10970586e83cRecommended next actions
Before opening or running
Open or run it only when its publisher and download source have been independently verified.
If you already opened or ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 antivirus engines avoided flagging this JAR, including 17 high-trust engines, and the completed sandbox did not issue a malware finding. 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 75 engines 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 T1543.002 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 75 antivirus engines flagged the JAR, and all 17 participating high-trust 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. Keep endpoint protection enabled and consider running it in an isolated environment if the source is uncertain, especially because of the unresolved direct-IP contact.
Where this verdict could be wrong3 caveats
- The completed sandbox mapped T1543.002 and T1562.001, techniques associated with service execution and impairment of defenses.
- Direct contact with 162.159.36.2 triggered MalwareTips.Synth.DirectIpC2, and contactedHosts=null 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/75 engines reported malicious or suspicious findings.
- 17 tier-1 engines, including BitDefender, Kaspersky, ESET-NOD32, and Microsoft, reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false after one completed sandbox run.
- droppedChildren.hasMaliciousChild=false across four inspected children.
- CIRCL, MalwareBazaar, and YARAify returned no hits.
- Runtime mapping includes T1543.002 and T1562.001.
- Direct-IP contact to 162.159.36.2 lacks a complete host-reputation result.
- All four inspected child hashes have unknown individual verdicts.
- No applicable code-signing identity is available for this JAR.
Use this JAR only from a trusted, expected source and keep endpoint protection enabled. If its origin is uncertain, test it in isolation and monitor the connection to 162.159.36.2.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 10MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 11filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
powhax-1.6.7.jar
fc37f179a4bd606f890fd79a48bf6caa7218e58ba9f176bee2ea10970586e83c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\download.jar"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
6952
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6952
04Isolated runtime analysis - Written fileObserved
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6952
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
- C:\Users\user\AppData\Local\Temp\hsperfdata_user
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\6944
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\1560
- /tmp/hsperfdata_root/4982
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- a5b9b1ebe461f9026f8b…26a8d2Never scannednever seen before
- 1b5b760bd67ca8e5880a…6484e1Never scannednever seen before
- c1de3a9376fdaef0ba6a…308b70Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 75engines flagged
- 12sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 12 times from 12 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: powhax-1.6.7.jar — fc37f179a4bd606f890fd79a48bf6caa7218e58ba9f176bee2ea10970586e83c
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\download.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: 6952 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6952
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- powhax-1.6.7.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 76.9 KB
- Last analyzed
- Sep 8, 2026, 3:36 PM UTC
fc37f179a4bd606f890fd79a48bf6caa7218e58ba9f176bee2ea10970586e83cSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or run it only when its publisher and download source have been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.