Is template-mod-1.0.0.jar safe?
No antivirus engine detected this JAR, but sandbox mappings for process injection, service modification, defense impairment, and direct-IP traffic warrant caution.
All 75 antivirus engines were silent, including 17 tier-1 products, and the completed sandbox issued no malware finding. However, runtime telemetry mapped activity to T1055, T1543.002, and T1562.001 and recorded direct-IP traffic whose reputation was not checked, so execution should be limited to an isolated environment.
d5287ec98a3d4bdffb…0948542876f88aRecommended 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 were silent, including 17 tier-1 products, and the completed sandbox issued no malware finding. However, runtime telemetry mapped activity to T1055, T1543.002, and T1562.001 and recorded direct-IP traffic whose reputation was not checked, so execution should be limited to an isolated environment.
The strongest reassuring signal is that 0 of 75 engines detected the file, including no detections from 17 tier-1 engines. One completed sandbox produced no malware verdict, and none of nine inspected dropped files was confirmed malicious. Against that, behavioral mappings include process injection, service modification, and impairment of defenses, which are material risk indicators even though the mappings do not prove intent. The sample also contacted 162.159.36.2 directly, but no complete host-reputation result is available. Medium prevalence reduces novelty concerns, yet no signer history, similar-file history, or researcher intelligence establishes a trusted origin.
What We Detected
None of 75 antivirus engines flagged the JAR, including 17 tier-1 engines. The file has been submitted 231 times by 206 sources, which provides moderate exposure rather than an isolated first sighting. No established malware family was identified.
Threat Behavior
One completed sandbox mapped activity to T1055, T1543.002, and T1562.001, covering possible process injection, service modification, and impairment of defenses. These mappings are concerning but do not independently prove malicious intent. Direct traffic to 162.159.36.2 was also recorded; because contacted-host reputation was not checked or saved, its risk remains unresolved. Nine dropped files were inspected without a confirmed malicious child, although their individual verdicts remain unknown.
What To Do Now
Do not run the JAR on a primary system until its source and expected functionality are verified. If testing is necessary, use an isolated virtual machine with endpoint protection enabled and monitor Java processes, service changes, and outbound traffic.
Where this verdict could be wrong4 caveats
- The complete 0/75 detection result, including 17 tier-1 engines without detections, weighs strongly against known malware.
- behaviour.hasMaliciousSandboxVerdict=false, so the completed sandbox did not independently issue a malware finding.
- The T1055 mapping is based on saved behavioral telemetry and does not prove that process injection actually occurred.
- No complete reputation cross-check exists for 162.159.36.2 because contactedHosts=null.
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 antivirus engines reported a malicious or suspicious result.
- All 17 reporting tier-1 engines returned no detection.
- behaviour.hasMaliciousSandboxVerdict=false after one completed sandbox.
- droppedChildren.hasMaliciousChild=false across nine inspected files.
- The sample has 206 submitters and 231 submissions.
- Runtime telemetry mapped possible process injection to T1055.
- Runtime telemetry mapped service modification to T1543.002.
- Runtime telemetry mapped defense impairment to T1562.001.
- Direct-IP traffic to 162.159.36.2 lacks a complete host-reputation result.
- All nine dropped-child verdicts remain unknown.
Verify the download source and expected mod contents before use. If validation is not possible, avoid execution; otherwise test only in isolation while keeping endpoint protection enabled.
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
PartialIndependent reference checks were attempted but are incomplete.
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
template-mod-1.0.0.jar
d5287ec98a3d4bdffb28519c92a8af52a5e8b891488ec54f5f0948542876f88a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.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
3460
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3460
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>\3460
- 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\6304
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\2104
- /tmp/hsperfdata_root/3564
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- e85301747d9141217b56…88db11Never scannednever seen before
- 3baaa8d96b62f40f44d9…68e350Never scannednever seen before
- 7044eb761a7faa20657f…af9deaNever 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
- 206sources 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 231 times from 206 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: template-mod-1.0.0.jar — d5287ec98a3d4bdffb28519c92a8af52a5e8b891488ec54f5f0948542876f88a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.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: 3460 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3460
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.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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\download.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
- template-mod-1.0.0.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 16.6 KB
- Last analyzed
- Sep 17, 2026, 4:18 AM UTC
d5287ec98a3d4bdffb28519c92a8af52a5e8b891488ec54f5f0948542876f88aSafety & 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 template-mod-1.0.0.jar safe, or is it malware?
What is template-mod-1.0.0.jar?
How many antivirus engines detected template-mod-1.0.0.jar?
What should I do if I already opened or ran template-mod-1.0.0.jar?
How do I remove template-mod-1.0.0.jar?
What is the SHA-256 hash of template-mod-1.0.0.jar?
How up to date is this analysis of template-mod-1.0.0.jar?
Community
Member reviews and reports for this exact file hash.