File scan report
Verdict Safe
Is HIGTools-
None of the 65 antivirus engines that checked it flagged this JAR, including 17 major antivirus engines, and the completed sandbox run issued no malicious 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 7
- Code signing Not applicable
- Test run Completed
- First seen 6mo ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Two offensive techniques and a direct connection to an IP address remain cautionary signals, but they lack engine, file it created, or external-intelligence corroboration.
The strongest evidence is broad antivirus agreement: 0 of the 65 antivirus engines that checked it detected the file, with all 17 reporting major antivirus engines silent. One completed sandbox run did not issue a malicious verdict, and no inspected child was identified as malware. The runtime record nevertheless includes and T1562.001, so the behavioral evidence is not entirely routine. A low-severity rule also noted direct traffic to 162.159.36.2, but no complete host-reputation result is available because that cross-check was not saved. With no family labels, YARA matches, or external threat-intelligence hits, the cautionary behavior does not outweigh the broad clean scan evidence.
What We Detected
The file was checked by 72 antivirus engines, and none reported it as malicious or suspicious. This includes 17 major antivirus engines. No malware family was identified, and researcher-curated checks returned no YARA rules or malware-feed match.
Threat Behavior
One completed sandbox run did not issue a malicious verdict. It recorded T1543.002 and T1562.001, plus direct traffic to 162.159.36.2; however, the direct-IP rule was low severity and these signals received no antivirus or external-intelligence corroboration. Six written or dropped hashes were inspected without a malicious child finding, although all six child verdicts remained unresolved. A complete reputation check for the contacted IP is unavailable.
What To Do Now
Use the JAR only if it came from the expected project or distribution channel, and keep security software enabled. If its source is uncertain, verify its SHA-256 hash and run it in an isolated environment rather than granting elevated privileges.
Where this verdict could be wrong3 caveats
- The runtime record contains and T1543.002, techniques associated with impairing defenses and service modification, though the sandbox did not produce a malicious verdict.
- The sample contacted 162.159.36.2 directly, but the missing contacted-host reputation result means no complete reputation assessment is available for that endpoint.
- Six dropped hashes were inspected without a malicious finding, but a count of 6 dropped files without a saved verdict means none received a definitive child verdict.
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 antivirus engines reported a detection.
- No sandbox returned a malicious verdict in one completed sandbox run.
- No dropped file is known to be malicious.
- YARAify returned 0 matching rules and MalwareBazaar returned no hit.
- The test run recorded T1562.001, associated with impairing defenses.
- The test run recorded T1543.002, associated with service modification.
- A low-severity direct-IP behaviour rule matched for 162.159.36.2.
- No contacted-host reputation result was saved, so the observed IP lacks a complete saved reputation check.
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
- 13filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
10MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1064
- T1082· System recon
- T1106
- T1202
- T1518.001· Checks your AV
- T1543.002· Service install
- T1562.001· Disables security
- T1564· Hides artifacts
- T1564.001· Hides artifacts
- T1564.003· Hides artifacts
Observed activity
Processes started
4Programs the file ran, with their command lines.
java.exe"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"cmd.exeC:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\sample.jar"" >> C:\cmdlinestart.log 2>&1java.exe"C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\sample.jar"java/usr/bin/java -jar /tmp/sample.jar
Files
13Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6492 - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user\6548 - Written
C:\cmdlinestart.log
Show all 13 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/5002/coredump_filter - Written
/tmp/hsperfdata_root/5002 - Written
/var/log/auth.log.1.gz - Written
/var/log/kern.log.1.gz - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\5056 - Deleted
/tmp/hsperfdata_root/5002
Sandbox background — not the file
8The analysis machine's own processes and connections, recorded in every run.
- VM process
icacls.exeC:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M - VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM process
sh/bin/sh sh -c /usr/lib/rsyslog/rsyslog-rotate logrotate_script /var/log/syslog - VM process
rsyslog-rotate/usr/lib/rsyslog/rsyslog-rotate - VM process
systemctl/usr/bin/systemctl systemctl kill -s HUP rsyslog.service - VM process
gzip/bin/gzip
Show all 8 entries for sandbox background — not the file
- VM process
sh/bin/sh sh -c /usr/lib/rsyslog/rsyslog-rotate logrotate_script /var/log/mail.info/var/log/mail.warn/var/log/mail.err/var/log/mail.log/var/log/daemon.log/var/log/kern.log/var/log/auth.log/var/log/user.log/var/log/lpr.log/var/log/cron.log/var/log/debug/var/log/messages - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache. 2 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 0a3e69c051b43f4ae875…82f44aNot checkedno saved verdict
- a3020b6ffb3a2d467674…c1506fNot checkedno saved verdict
Chapter 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
- Oct 6, 2026, 5:04 PM UTC
- SHA-256
cc4df984842ad07ee0efb26c49c821a12dedf8976c6c276c4e0c67b9f666bccf- SHA-1
ae8a3fc691b46c03ceafea8bf5b2ee2e15ac4bda- MD5
8a7b2f0944fdfb10c5be11dfc8410ece
About this file
HIGTools-2.11.2.jar is a JAR file of 210.9 kB.
- Type and size
- JAR · 210.9 kB
- Signer
- Not applicable
- First seen
- Apr 19, 2026On VirusTotal.
- Submitted by
- 48 distinct sources
First scanned Updated
Antivirus consensus
0 of 65 engines flagged this file
7 of the 72 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-234 engines0flagged
- Low-trust13 engines0flagged
View all 72 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookClean
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZoneAlarmClean
- ZonerClean
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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.