Is session-id-login-mod-1.3.0.jar safe?
No antivirus engine detected this new JAR, but one sandbox mapped its activity to three offensive techniques, including possible process injection and defense impairment.
All 75 antivirus engines were silent, including 17 tier-1 engines, and the completed sandbox did not issue a malware finding. However, runtime mappings to T1055, T1543.002, and T1562.001 warrant caution because the file is newly observed and lacks corroborating history.
14ca5c22239e296c6b…46834cb3f1382eRecommended 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 engines, and the completed sandbox did not issue a malware finding. However, runtime mappings to T1055, T1543.002, and T1562.001 warrant caution because the file is newly observed and lacks corroborating history.
The strongest reassuring evidence is that 0 of 75 engines detected the file, with no tier-1 family consensus. One completed sandbox also produced no malicious verdict, and none of nine inspected dropped children was identified as malicious. Against that, the runtime record maps activity to T1055, T1543.002, and T1562.001, while a high-severity heuristic highlights possible process injection. That mapping does not prove the specific mechanism or malicious intent, and no engine or external research source corroborates a malware family. Because the file has only one submission and no similar-file history, the behavioural concern cannot yet be dismissed as routine or confirmed as hostile.
What We Detected
No antivirus engine flagged the JAR: 0 of 75 detections, including no findings from 17 tier-1 engines. No malware family was identified, and CIRCL, MalwareBazaar, and YARAify supplied no corroborating hit.
Threat Behavior
One completed sandbox did not issue a malicious verdict, but its telemetry was mapped to T1055, T1543.002, and T1562.001. The high-severity ProcessInjection heuristic indicates possible process-injection-like activity, although the available evidence does not prove an injection method or hostile intent. Nine dropped files were inspected without a malicious child finding, but their individual verdicts remain unknown. No complete contacted-host reputation result is available.
What To Do Now
Avoid running the file on a primary system until its source and expected mod behavior are verified. If testing is necessary, use an isolated environment, keep endpoint protection enabled, and rescan after additional reputation data becomes available.
Where this verdict could be wrong4 caveats
- The complete 0/75 engine result, including 17 tier-1 engines, weighs against the runtime heuristic.
- The only completed sandbox labeled the run clean, and behaviour.hasMaliciousSandboxVerdict=false.
- All nine dropped children have unknown individual verdicts, so droppedChildren.hasMaliciousChild=false is not affirmative proof that they are benign.
- contactedHosts=null, so no completed host-reputation cross-check is available; the run itself recorded no contacted domains, IPs, or URLs.
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 of 75 antivirus engines detected the file.
- All 17 reporting tier-1 engines returned undetected.
- The completed sandbox issued no malicious verdict.
- No inspected dropped child was identified as malicious.
- No external research-intelligence hit was present.
- Runtime telemetry mapped to T1055 process injection.
- Runtime telemetry mapped to T1562.001 impairment of defenses.
- Runtime telemetry mapped to T1543.002 system-service activity.
- The sample is newly observed with only one submission.
- Nine dropped children lack conclusive individual verdicts.
Verify the JAR against the mod developer's official release and checksum before use. Keep endpoint protection enabled and test only in isolation if provenance cannot be established.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete1 signature or behavior rule 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
- 16MITRE ATT&CK techniques
- 15spawned processes
- 0network 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: Contained obfuscated or packed code that makes inspection harder.
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.
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
session-id-login-mod-1.3.0.jar
14ca5c22239e296c6ba108ca73b772df19147a50edf4fe7d7e46834cb3f1382e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.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
4920
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\4920
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
5 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.
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\4920
- 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\1060
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\2912
- /tmp/hsperfdata_root/3563
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- a57ea470cd25150b2e6d…506703Never scannednever seen before
- f12f56ed3107be3c646f…9dbcc4Never scannednever seen before
- 895b616e93efaadd097a…dd2383Never 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 1sources 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 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: session-id-login-mod-1.3.0.jar — 14ca5c22239e296c6ba108ca73b772df19147a50edf4fe7d7e46834cb3f1382e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.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: 4920 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\4920
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
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\sample.jar"
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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- session-id-login-mod-1.3.0.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 28.0 KB
- Last analyzed
- Oct 1, 2026, 7:56 PM UTC
14ca5c22239e296c6ba108ca73b772df19147a50edf4fe7d7e46834cb3f1382eSafety & 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 session-id-login-mod-1.3.0.jar safe, or is it malware?
What is session-id-login-mod-1.3.0.jar?
How many antivirus engines detected session-id-login-mod-1.3.0.jar?
I already downloaded and opened or ran session-id-login-mod-1.3.0.jar — what should I do?
How do I remove session-id-login-mod-1.3.0.jar?
What is the SHA-256 hash of session-id-login-mod-1.3.0.jar?
How up to date is this analysis of session-id-login-mod-1.3.0.jar?
Community
Member reviews and reports for this exact file hash.