Is TLauncher.jar safe?
Zero detections across 75 engines despite sandbox activity that triggered heuristic rules.
No antivirus engine flagged the JAR. Sandbox recorded process-injection and LSASS access patterns, yet no malicious verdict or known-bad no complete contacted-host reputation result was available external-intel checks support a safe classification.
77a85ddcf6b24ef725…91ad78cb66fe87Recommended next actions
Before opening or running
Open or run it only when its publisher and download source have been independently verified.
If you already opened or ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
No antivirus engine flagged the JAR. Sandbox recorded process-injection and LSASS access patterns, yet no malicious verdict or known-bad no complete contacted-host reputation result was available external-intel checks support a safe classification.
All 75 engines returned clean results, including 17 tier-1 engines. The sandbox observed six offensive MITRE techniques, but the sandbox itself did not issue a malicious verdict. no complete contacted-host reputation result was available. External intelligence sources returned no hits. The combination of zero engine detections, clean external intel, and medium prevalence outweighs the heuristic signals.
What We Detected
75 engines scanned the 10 MB JAR; none returned a malicious or suspicious label. Sandbox execution produced six MITRE techniques normally associated with malware, yet the sandbox verdict remained clean.
Threat Behavior
The sample wrote files under %APPDATA%\.tlauncher, contacted 15 IPs directly, and accessed LSASS. No persistence mechanisms or malicious child processes were created. External reputation services list no prior malicious associations.
What To Do Now
Keep endpoint protection enabled. If the file is required, run it in a controlled environment and monitor for unexpected outbound traffic.
Where this verdict could be wrong1 caveat
- Sandbox observed LSASS access and direct-IP traffic, but no malicious sandbox verdict or known-bad hosts were 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.
- 0/75 engines flagged the file
- No malicious child files or hosts
- Medium prevalence with 193 unique submitters
- Sandbox observed LSASS access (T1548)
- Direct-IP connections to 15 addresses
The file can be considered safe for use; continue monitoring network activity if executed.
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
Partial2 of 17 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 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
- 32MITRE ATT&CK techniques
- 15spawned processes
- 19network contacts
- 30filesystem & mutex artifacts
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
TLauncher.jar
77a85ddcf6b24ef72524d8615761f52a7970ce1a8b9db7302d91ad78cb66fe87
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
3120
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3120
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
195.201.104.213
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
104.26.10.134
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 195.201.104.213
- 104.26.10.134
- 195.201.83.254
- 104.20.14.15
- 150.171.110.195
- 104.20.7.182
- 172.66.129.18
- 176.9.101.148
- 172.67.221.204
- 185.175.46.50
- http://advancedrepository.net/check.bin
- http://advancedrepository.net/tlauncher-sources/prod/release/tlauncher/starterUpdateV1_bridge.json
- http://img.tlauncher.org/update/downloads/configs/client/video/tl-discord-en.png
- http://img.tlauncher.org/update/downloads/configs/client/images/img-up-for-server.png
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3120
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
- C:\Users\<USER>\AppData\Roaming\.tlauncher\logs\starter\log.2026-07-05_18.log
- C:\Users\<USER>\AppData\Local\Temp\imageio8264375687278334996.tmp
- C:\Users\<USER>\AppData\Local\Temp\imageio8162749816125556552.tmp
- C:\Users\<USER>\AppData\Roaming\.tlauncher\starter\cache\https_repo.tlauncher.org\tlauncher-sources\prod\release\tlauncher\appConfig.json.temp
- C:\Users\<USER>\AppData\Roaming\.tlauncher\starter\cache\https_repo.tlauncher.org\tlauncher-sources\prod\release\tlauncher\2.9369\dependencies.json.temp
- C:\Users\<USER>\AppData\Roaming\.tlauncher\starter\cache\https_repo.tlauncher.org\tlauncher-sources\prod\release\tlauncher\2.9369\resources.json.temp
- C:\Users\<USER>\AppData\Roaming\.tlauncher\starter\cache\https_repo.tlauncher.org\tlauncher-sources\prod\release\tlauncher\javaConfig21.json.temp
- C:\Users\<USER>\AppData\Roaming\.tlauncher\starter\jre-21.0.11-windows-x64.zip
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c04118aed95ef281c6b3…8c3c48Never scannednever seen before
- edd691fc6ad7c7f3167e…3718b1Never scannednever seen before
- 533fcbcf37d49f379094…8fbdd5Never scannednever seen before
- 9ed26791dc2d8629fdf8…3e269bNever scannednever seen before
- 9ecd53bc4faff6895812…3b3799Never scannednever seen before
- 1887ffd2b41d8787c584…6d5af5Never scannednever seen before
- a171ee4c734dd2da837e…36ca26Never scannednever seen before
- 7eb52e240f1d92c808d1…e95173Never scannednever seen before
- fce548284667e4ae3784…f55ea1Never scannednever seen before
- 06436157be6a8a371e07…094e25Never 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.
- 3rule hits recorded
- 0 / 75engines flagged
- 193sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 238 times from 193 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: TLauncher.jar — 77a85ddcf6b24ef72524d8615761f52a7970ce1a8b9db7302d91ad78cb66fe87
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: 3120 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\3120
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: 195.201.104.213 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 104.26.10.134 — 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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence195.201.104.213 · 104.26.10.134 · 195.201.83.254
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
- TLauncher.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 9.7 MB
- Last analyzed
- Sep 4, 2026, 2:39 PM UTC
77a85ddcf6b24ef72524d8615761f52a7970ce1a8b9db7302d91ad78cb66fe87Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or run it only when its publisher and download source have been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is TLauncher.jar safe?
What is TLauncher.jar?
How many antivirus engines detected TLauncher.jar?
What is the SHA-256 hash of TLauncher.jar?
Is it safe to open or run TLauncher.jar?
How up to date is this analysis of TLauncher.jar?
Community
Member reviews and reports for this exact file hash.