Is HIGTools-2.11.2.jar safe?
No antivirus engine identified a threat, and one sandbox produced no malicious verdict, though low-severity direct-IP traffic remains incompletely reputation-checked.
None of 75 antivirus engines flagged this JAR, including the contributing tier-1 products, and the completed sandbox did not issue a malicious verdict. The main caveat is one direct-IP connection plus two offensive-associated techniques; the contacted IP lacks a complete reputation result, so protection should remain enabled.
cc4df984842ad07ee0…0c67b9f666bccfRecommended 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.
None of 75 antivirus engines flagged this JAR, including the contributing tier-1 products, and the completed sandbox did not issue a malicious verdict. The main caveat is one direct-IP connection plus two offensive-associated techniques; the contacted IP lacks a complete reputation result, so protection should remain enabled.
The strongest evidence is broad antivirus agreement: 0 of 75 engines reported a malicious or suspicious result, with 16 tier-1 engines reporting no detection. One completed sandbox recorded two offensive-associated MITRE techniques, but it produced no malicious sandbox verdict, persistence indicator, or registry modification. Six dropped files were inspected without a malicious child being identified, although their individual verdicts remain unknown. A low-severity heuristic noted direct contact with 162.159.36.2, and no complete contacted-host reputation result is available. Research intelligence supplied no MalwareBazaar, CIRCL, or YARAify corroboration, making a known malware interpretation unlikely on the available evidence.
What We Detected
None of 75 antivirus engines flagged HIGTools-2.11.2.jar, and 16 tier-1 engines reported no detection. MalwareBazaar, CIRCL, and YARAify supplied no corroborating threat-intelligence matches.
Threat Behavior
One completed sandbox run recorded T1543.002 and T1562.001, but it did not produce a malicious sandbox verdict, persistence indicator, mutex, or registry change. A low-severity heuristic also noted direct-IP traffic to 162.159.36.2. Because contactedHosts is unavailable, no complete reputation result exists for that address. Six written or dropped files were inspected without a malicious child being identified, although each child remains individually unclassified.
What To Do Now
Use the file only if it came from the expected project or distributor, and keep endpoint protection enabled. If the source is uncertain, verify the SHA-256 hash with the publisher and run it in an isolated environment before granting elevated privileges.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques includes T1543.002 and T1562.001, techniques associated with service execution and impairment of defenses.
- The sandbox recorded contact with 162.159.36.2, but contactedHosts=null means its reputation was not completely checked.
- All six dropped children have unknown individual verdicts despite droppedChildren.hasMaliciousChild=false.
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 a malicious or suspicious result.
- engines.tier1Malicious=0 and engines.tier1ReportedClean=16.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false.
- Sandbox observed offensive-associated techniques T1543.002 and T1562.001.
- Low-severity direct-IP contact to 162.159.36.2 lacks a complete host-reputation check.
- Six dropped children remain individually unclassified.
Confirm the JAR came from the expected project and keep endpoint protection enabled. Avoid granting administrative access unless its functionality requires it and the source is trusted.
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
- 13filesystem & 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
HIGTools-2.11.2.jar
cc4df984842ad07ee0efb26c49c821a12dedf8976c6c276c4e0c67b9f666bccf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\sample.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
6492
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6492
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>\6492
- 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\6548
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\5056
- /tmp/hsperfdata_root/5002
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- 0a3e69c051b43f4ae875…82f44aNever scannednever seen before
- a3020b6ffb3a2d467674…c1506fNever scannednever seen before
- c1de3a9376fdaef0ba6a…308b70Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 44a3bab2c338e3bca24c…d3b9e7Never scannednever seen before
- ac941ead01d5451a7a9f…253227Never 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
- 38sources 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 45 times from 38 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: HIGTools-2.11.2.jar — cc4df984842ad07ee0efb26c49c821a12dedf8976c6c276c4e0c67b9f666bccf
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\sample.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: 6492 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6492
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
- HIGTools-2.11.2.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 206.0 KB
- Last analyzed
- Sep 8, 2026, 3:48 PM UTC
cc4df984842ad07ee0efb26c49c821a12dedf8976c6c276c4e0c67b9f666bccfSafety & 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 HIGTools-2.11.2.jar safe?
What is HIGTools-2.11.2.jar?
How many antivirus engines detected HIGTools-2.11.2.jar?
What is the SHA-256 hash of HIGTools-2.11.2.jar?
Is it safe to open or run HIGTools-2.11.2.jar?
How up to date is this analysis of HIGTools-2.11.2.jar?
Community
Member reviews and reports for this exact file hash.