Suspicious
Unsigned JAR with sandbox-observed process injection but zero engine detections and no external intel hits.
2b8371928a5404de79…88bf6b972fThe reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
Zero engine detections across 66 reporters including 16 tier-1 engines rules out strong malware consensus. However, the sandbox captured T1055 process injection via java.exe command lines and the high-severity heuristic fired on that behaviour. The file is unsigned, only two days old, and has no prior similar-hash verdicts or external-intel corroboration. Medium prevalence suggests wider distribution than a pure test sample, but without named-family detections or malicious children the risk remains borderline.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines: 0 malicious detections, tier1Malicious=0, tier1FamilyConsensus.family=null
behaviour.offensiveTechniques: T1055, T1543.002, T1562.001 with triggeredHeuristics[0].rule=MalwareTips.Synth.ProcessInjection
signing.verified=false, signerStats.found=false, prevalence.classification=medium
droppedChildren.hasMaliciousChild=false, externalIntel.yaraify.ruleCount=0
- Zero malicious engine detections
- No malicious dropped children
- No contacted malicious hosts
- Sandbox observed T1055 process injection
- Unsigned JAR with 2-day age
- Persistence-related MITRE techniques (T1543.002)
Treat as suspicious pending further sandbox runs or community reports; do not execute on production systems without isolation.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Hides inside another running program to evade antivirus.
High concern: Downloads more malware onto your PC.
High concern: Installs itself as a Windows service to stay running.
High concern: Tries to disable or bypass your security software.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
Translated from the file's technical behaviour during analysis. It never ran on your device.
What to do now
We couldn't fully clear this file. Treat it with caution.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an email attachment or a random download link is a red flag.
If you're unsure, delete it. You can always re-download a clean copy from the official source.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
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.
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2956
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
- C:\ProgramData\Microsoft\Windows Security Health\Logs
- 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\1560
- /tmp/hsperfdata_root/3545
- \BaseNamedObjects\Local\SM0:6888:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:6888:120:WilError_03
- \BaseNamedObjects\Local\ZonesCacheCounterMutex
- \BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- 37a341a656fa359e2884…9f9c88Never scannednever seen before
- 1fb70758d211fa4f059f…bde9a9Never scannednever seen before
- cbfa63e9f038f6d4ff92…d16b75Never scannednever seen before
- 3f8096f14540c8e18e4e…ad10b8Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
YARA & heuristic rule matches
A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"
0 detections across 74 engines
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Forensic fingerprint
- File name
- 67-Client.jar
- Size
- 3.35 MB
- MIME type
- (unknown)
- Detected type
- JAR
- SHA-256
- 2b8371928a5404de7983b14becfd933fd5988d8e1b07e4ab99c12488bf6b972f
- MD5
- aec4005a1b4103e75c0f0e013d88ff22
- SHA-1
- 6442b8fd0903ed97245d02c1866e970e23feb02b
- First seen (VT)
- 7/19/2026, 10:00:03 PM
- Last analysis (VT)
- 7/21/2026, 8:11:36 AM
- First scan (MalwareTips)
- 7/21/2026, 3:28:40 PM
- Last scan (MalwareTips)
- 7/21/2026, 3:28:40 PM
Safety FAQ
Common questions about 67-Client.jar, answered from the scan data above.
- 67-Client.jar is suspicious — treat it as unsafe until you're sure. 0 of 74 antivirus engines flag it, which isn't a strong consensus but is enough to be cautious. Don't opened it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- 67-Client.jar is a file, about 3.3 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- None — all 74 antivirus engines we queried report 67-Client.jar as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove 67-Client.jar: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original 67-Client.jar file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- The SHA-256 hash of 67-Client.jar is 2b8371928a5404de7983b14becfd933fd5988d8e1b07e4ab99c12488bf6b972f, and its MD5 is aec4005a1b4103e75c0f0e013d88ff22. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 21, 2026. Because a file's hash never changes, the identity of 67-Client.jar is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.