File scan report
Verdict Suspicious
Is hunterbuddy- 1. 0. 3. jar safe? Treat it as suspicious.
No antivirus engine flags this Java archive, but the sandbox analysis returned split results with a malware label, so the evidence is not strong enough for a firm call.
Read the whole reasonShow less
Why Suspicious? One sandbox test run rated it malicious while another found nothing; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open or run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already opened or ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
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 8d ago
Chapter 02
Why we think so
2 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 65 antivirus engines that checked it flagged this Java archive. However, the combined sandbox analysis produced both a malware/trojan label and a clean label. Nothing else corroborates the malicious result, and the file is rarely submitted, with no publisher or reference-database history to vouch for it.
Detection results are entirely clean, including all major antivirus engines that reported. The sandbox analysis, however, is split between a malware/trojan label and a clean label. The recorded activity in the test run looks like ordinary Java startup: Java processes and temporary performance files, with no named injection target, persistence or network contact. With only four submitters, no signature applicable and no external intelligence either way, the evidence does not support a confident call in either direction.
What We Detected
None of the 65 antivirus engines that checked it flagged this Java archive, which was first seen on Oct 18, 2026. Public malware databases and community YARA rules returned no matches, and we hold no prior verdicts on similar files.
Threat Behavior
Across the sandbox runs, the combined verdict was split between a malware/trojan label and a clean label. The recorded activity was the archive running under Java and writing standard Java runtime temporary files. No process was named as an injection target, no persistence was recorded and no network contacts were captured. No complete host-reputation result is available.
What To Do Now
Only run this file if you obtained it from the developer's official source and trust that source. If unsure, wait for more analysis or rescan it later, and keep your security software enabled.
Where this verdict could be wrong2 caveats
- The sandbox runs returned a malware/trojan label, which could reflect real hidden behaviour in a Java archive that engines have not yet learned to detect.
- No engine flagged the file and no injection target, network contact or persistence was recorded, so the malicious label may be a sandbox false positive.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No antivirus engine flagged the file, including all major antivirus engines
- No injection target, persistence or network contact was recorded during the sandbox runs
- No matches in public malware databases or malware-specific YARA rules
- The sandbox analysis returned a malware/trojan label in addition to a clean one
- The file is rarely submitted and has no publisher history to establish trust
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 3 isolated tests; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 14sandbox rule tags
- 4spawned processes
- 0network contacts
- 11filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Loaded extra code modules while running.
Note: Checked which security software was installed on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as downloading a file, but no download was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
hunterbuddy-1.0.3.jar
eecdc705a5808c87b3137f3effab3bc0341d4811a13e13b720011546db23d0c5
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
javaw.exe
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"
Test run - Evidence 3 of 5: ProcessSeen in the test run
cmd.exe
C:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\runtime.jar""
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
6508
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6508
Test run - Evidence 5 of 5: Written fileSeen in the test run
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 3 sandboxes and the results were split: 1 returned "malicious" and 1 returned "clean".
Sandbox verdicts
2- VT: MALWARE, TROJANmalicious
- VT: CLEANclean
Techniques observed in the sandbox
14MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1055· Process injection
- T1059· Runs commands
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1106
- T1129· Loads modules
- T1202
- T1518.001· Checks your AV
- T1564· Hides artifacts
- T1564.001· Hides artifacts
- T1564.003· Hides artifacts
- T1574· Execution hijack
Observed activity
Processes started
4Programs the file ran, with their command lines.
javaw.exe"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"cmd.exeC:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\runtime.jar""java.exe"C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\runtime.jar"java/usr/bin/java -jar /tmp/runtime.jar
Files
11Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6508 - 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\6428 - Written
\Device\ConDrv
Show all 11 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/3535/coredump_filter - Written
/tmp/hsperfdata_root/3535 - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\4700 - Deleted
/tmp/hsperfdata_root/3535
Sandbox background — not the file
2The 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
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache. 3 have no saved verdict and were not checked; that is missing coverage, not a finding.
- d7b3636f8625b06c432e…c0fbb2Not checkedno saved verdict
- 340dd107f3aa417a6e33…436096Not checkedno saved verdict
- a575be6136a3ab9e594c…30e39aNot 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 23, 2026, 4:42 PM UTC
- SHA-256
eecdc705a5808c87b3137f3effab3bc0341d4811a13e13b720011546db23d0c5- SHA-1
55b6bdf97d3a129f3e82e9add469e87e0a92d2e4- MD5
1b05af39faa2da4df7c4665f2103ad4c
About this file
hunterbuddy-1.0.3.jar is a JAR file of 3.2 MB.
- Type and size
- JAR · 3.2 MB
- Signer
- Not applicable
- First seen
- Oct 18, 2026On VirusTotal.
- Submitted by
- 4 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
Antivirus consensus
0 of 65 engines flagged this file
10 of the 75 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 75 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
- DeepInstinctNo result
- 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
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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 hunterbuddy-1.0.3.jar safe, or is it malware?
What is hunterbuddy-1.0.3.jar?
How many antivirus engines detected hunterbuddy-1.0.3.jar?
What should I do if I already opened or ran hunterbuddy-1.0.3.jar?
What is the SHA-256 hash of hunterbuddy-1.0.3.jar?
How up to date is this analysis of hunterbuddy-1.0.3.jar?
Community
Member reviews and reports for this exact file hash.