Is original-TLauncher-2.9374.jar safe?
Unsigned JAR shows process-injection behaviour in sandbox yet zero AV detections.
The file triggered a heuristic rule for process injection and performed several suspicious actions in the sandbox, but no antivirus engine flagged it and no malicious children or external-intel hits were found.
4ed12866d2e15537d7…0e6eb963a31352Recommended 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.
The file triggered a heuristic rule for process injection and performed several suspicious actions in the sandbox, but no antivirus engine flagged it and no malicious children or external-intel hits were found.
Zero detections across 75 engines and clean external-intel sources weigh against malice, yet the sandbox recorded three offensive MITRE techniques and wrote nine dropped files. The triggered heuristic explicitly notes that the T1055 mapping does not prove actual injection or malicious intent. Medium prevalence and lack of a completed host-reputation check leave the file in mixed-signal territory.
What We Detected
75 engines reported the JAR clean; none returned a malicious or suspicious label. Sandbox execution captured three MITRE techniques (T1055, T1543.002, T1562.001) and nine dropped files, but the sandbox verdict itself was not malicious and no child file was flagged.
Threat Behavior
The observed commands include Java execution with a javaagent flag and permission changes via icacls, consistent with possible process manipulation or persistence attempts. No C2 domains, malicious children, or external-intel matches were recorded.
What To Do Now
Do not run the file on production systems. If you need the functionality, obtain the launcher from its official source and verify the hash against the publisher. Keep endpoint protection enabled.
Where this verdict could be wrong1 caveat
- Sandbox observed process-injection-related commands and 9 dropped children, but no malicious verdict or child verdict was recorded.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections from 75 engines
- No tier-1 or low-trust malicious labels
- No external-intel hits on CIRCL, MalwareBazaar, or YARAify
- Sandbox recorded process-injection-related activity (T1055)
- Nine dropped files created during execution
- Medium prevalence with only 11 days of history
Treat the file as untrusted; obtain any needed Minecraft launcher directly from the official TLauncher site and compare hashes before execution.
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
- 15MITRE 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: 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
original-TLauncher-2.9374.jar
4ed12866d2e15537d78eafe054bc02bab0ff5604a349c408f80e6eb963a31352
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
2640
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2640
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>\2640
- 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\6952
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\5732
- /tmp/hsperfdata_root/3550
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- fb1cb711404e6cc0d87f…4af574Never scannednever seen before
- 7c9193b691926d65930d…ed2ae7Never scannednever seen before
- e5c4d9cf566003a3fff6…bb171fNever scannednever seen before
- 3f8096f14540c8e18e4e…ad10b8Never 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
- 5sources 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 5 times from 5 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: original-TLauncher-2.9374.jar — 4ed12866d2e15537d78eafe054bc02bab0ff5604a349c408f80e6eb963a31352
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: 2640 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2640
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\download.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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- original-TLauncher-2.9374.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 4.8 MB
- Last analyzed
- Sep 4, 2026, 2:40 PM UTC
4ed12866d2e15537d78eafe054bc02bab0ff5604a349c408f80e6eb963a31352Safety & 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 original-TLauncher-2.9374.jar safe, or is it malware?
What is original-TLauncher-2.9374.jar?
How many antivirus engines detected original-TLauncher-2.9374.jar?
I already downloaded and opened or ran original-TLauncher-2.9374.jar — what should I do?
How do I remove original-TLauncher-2.9374.jar?
What is the SHA-256 hash of original-TLauncher-2.9374.jar?
How up to date is this analysis of original-TLauncher-2.9374.jar?
Community
Member reviews and reports for this exact file hash.