Is leavesHack-2.3.0.jar safe?
No antivirus engine detected this JAR, but one sandbox mapped potentially offensive techniques and direct-IP traffic that lacks a completed reputation check.
All 75 antivirus engines produced no malicious or suspicious detections, including the reporting tier-1 engines. However, one sandbox mapped process-injection, service, and defense-impairment techniques and observed direct-IP traffic, so the file warrants caution until its source and behavior can be independently verified.
5aab62df5d2b67f0e0…97ad188aba3891Recommended next actions
Before opening or running
Do not open or run it until the source and publisher can be verified independently.
If you already opened or ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the publisher's official site and verify its exact hash when possible.
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 produced no malicious or suspicious detections, including the reporting tier-1 engines. However, one sandbox mapped process-injection, service, and defense-impairment techniques and observed direct-IP traffic, so the file warrants caution until its source and behavior can be independently verified.
Static scanning strongly favors a benign interpretation because 0 of 75 engines flagged the JAR, with no tier-1 family consensus. One completed sandbox nevertheless mapped activity to T1055, T1543.002, and T1562.001, although it did not issue a malicious sandbox finding. The sample also contacted 162.159.36.2 directly, and no complete host-reputation result is available because the contacted-host check was not saved. Nine dropped children were inspected without a malicious finding, but every child remains unclassified. With no external-intelligence hits or named malware family, the runtime concerns are meaningful but not sufficiently corroborated for a malware-family determination.
What We Detected
No antivirus engine flagged the JAR: 0 of 75 reported it as malicious or suspicious, and engines.tier1Malicious=0. External research sources also supplied no matching malware family, with externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false.
Threat Behavior
One completed sandbox mapped activity to T1055, T1543.002, and T1562.001. These mappings can indicate process injection, service-related manipulation, and impairment of defenses, but behaviour.hasMaliciousSandboxVerdict=false and the saved evidence does not establish intent. Direct traffic to 162.159.36.2 was also recorded; contactedHosts=null means no complete reputation result is available for that address. Nine dropped children were inspected without a malicious child finding, although all nine remain unclassified.
What To Do Now
Only run the JAR if it came from a verified project release or another source you trust. Keep endpoint protection enabled, use an isolated environment if testing is necessary, and verify the file hash against the publisher's official release information.
Where this verdict could be wrong3 caveats
- The completed sandbox mapped activity to T1055, T1543.002, and T1562.001, techniques associated with process injection, service manipulation, and defense impairment.
- Direct communication with 162.159.36.2 was observed, but contactedHosts=null means its reputation was not completely cross-checked.
- All nine inspected dropped-child records have unknown verdicts, so hasMaliciousChild=false does not establish that those children are benign.
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 detection.
- engines.tier1Malicious=0 with 16 tier-1 engines reporting no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- YARAify, CIRCL, and MalwareBazaar returned no matching intelligence.
- Runtime evidence mapped possible process injection under T1055.
- Runtime evidence mapped T1543.002 and T1562.001.
- Direct-IP traffic to 162.159.36.2 lacks a completed host-reputation check.
- All nine dropped children remain unclassified.
- The JAR has no applicable code-signing identity to authenticate its publisher.
Verify SHA-256 5aab62df5d2b67f0e09929dcc166c3deca944afe337a3c488f97ad188aba3891 against the official source before execution. If its origin cannot be confirmed, keep endpoint protection enabled and avoid running it outside an isolated test environment.
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
Complete2 signature or behavior rules 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
- 15MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Transferred a file over the network; malware can use this to fetch additional payloads.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
leavesHack-2.3.0.jar
5aab62df5d2b67f0e09929dcc166c3deca944afe337a3c488f97ad188aba3891
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.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
2616
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2616
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>\2616
- 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\1560
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\1616
- /tmp/hsperfdata_root/3582
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- 1806d57ccf31a37a6246…8c289eNever scannednever seen before
- 7eb664c02525e71e4e56…094972Never scannednever seen before
- 99cb5de0573367122029…f9f962Never scannednever seen before
- b468bf508c1b034631c5…457d6eNever scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 61625fd8b084f70f242d…55abd2Never scannednever seen before
- 50c82f36208ed8040447…2d7843Never scannednever seen before
- 8e8711854186c68e2368…4a3c7cNever scannednever seen before
- 759aafcfa2395ce1b800…2af0f7Never 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.
- 2rule hits recorded
- 0 / 75engines flagged
- 18sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 20 times from 18 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: leavesHack-2.3.0.jar — 5aab62df5d2b67f0e09929dcc166c3deca944afe337a3c488f97ad188aba3891
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 2616 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2616
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\runtime.jar"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
- leavesHack-2.3.0.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 1.7 MB
- Last analyzed
- Sep 8, 2026, 3:46 PM UTC
5aab62df5d2b67f0e09929dcc166c3deca944afe337a3c488f97ad188aba3891Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open or run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this Java file and use a fresh copy from a trusted source. Get a fresh copy from the publisher's official site and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is leavesHack-2.3.0.jar safe, or is it malware?
What is leavesHack-2.3.0.jar?
How many antivirus engines detected leavesHack-2.3.0.jar?
I already downloaded and opened or ran leavesHack-2.3.0.jar — what should I do?
How do I remove leavesHack-2.3.0.jar?
What is the SHA-256 hash of leavesHack-2.3.0.jar?
How up to date is this analysis of leavesHack-2.3.0.jar?
Community
Member reviews and reports for this exact file hash.