Is TLauncher.exe safe?
TLauncher.exe shows process-injection and LSASS-access behaviour with only two low-tier detections and an unproven signer.
Two engines flag the file as PUP/TrojanDropper while 17 tier-1 engines remain silent. The sample exhibits five offensive MITRE techniques including process injection and LSASS access, yet no malicious children or known-bad hosts were observed. The single prior signer match was also rated suspicious.
f0cb809918c2bf85a8…50acf3e5a714ceRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
Two engines flag the file as PUP/TrojanDropper while 17 tier-1 engines remain silent. The sample exhibits five offensive MITRE techniques including process injection and LSASS access, yet no malicious children or known-bad hosts were observed. The single prior signer match was also rated suspicious.
The engine consensus is weak (2/75) and lacks tier-1 support, but the runtime evidence shows clear offensive techniques that legitimate software rarely needs. The signer has no track record, and the only similar-hash verdict was also suspicious. These mixed signals place the file in the borderline category rather than clean or malicious.
What We Detected
Two of 75 engines flagged TLauncher.exe: Malwarebytes labelled it PUP.Optional.TLauncher and VBA32 called it TrojanDropper.Win32.Launch4j. No tier-1 engine joined the consensus. The file is signed by 'TLauncher Inc.' but that signer has only one recorded sample and zero historical safe rate.
Threat Behavior
Sandbox telemetry recorded five offensive MITRE techniques: T1055 (process injection), T1485/T1486 (data destruction), T1548 (privilege escalation) and T1562.001 (defense evasion). The sample contacted 18 raw IP addresses and wrote multiple temporary and configuration files under %APPDATA%\.tlauncher. No dropped child files or previously known malicious hosts were identified.
What To Do Now
Do not run the executable on production systems. If Minecraft launcher functionality is required, obtain it from the official Mojang site or a verified distribution channel. Keep Windows Defender and other endpoint protection enabled.
Where this verdict could be wrong1 caveat
- contactedHosts.maliciousHosts.length=0 and droppedChildren.hasMaliciousChild=false reduce the weight of the observed offensive techniques.
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 tier-1 malicious detections
- No malicious dropped children
- no complete contacted-host reputation result was available
- Five offensive MITRE techniques observed in sandbox
- Signer has no established safe history
- Direct-IP network traffic without domain context
Treat the file as untrusted; obtain Minecraft launchers only from official sources and retain all security software protections.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 21 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
- 29MITRE ATT&CK techniques
- 15spawned processes
- 23network contacts
- 31filesystem & 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: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
TLauncher.exe
f0cb809918c2bf85a8eef2bcbd35218e75426b4e5698ca1cca50acf3e5a714ce
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\starter-core-1.268-v6.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\starter-core-1.268-v6.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
5216
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5216
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.20.15.15
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.20.15.15
- 104.26.10.134
- 150.171.110.195
- 195.201.83.254
- 172.66.129.18
- 176.9.101.148
- 104.20.7.182
- 185.175.46.50
- 212.41.10.12
- 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>\5216
- 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\imageio355229352328223702.tmp
- C:\Users\<USER>\AppData\Local\Temp\imageio1467050269030202348.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
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- a1fb74983ba0d8eb876f…e6c89eNever scannednever seen before
- d627e7065391634c7aee…b1d224Never scannednever seen before
- 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
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
- 2 / 75engines flagged
- 1,057sources 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
2 of 75 antivirus engines flagged the file, including Malwarebytes and VBA32.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from TLauncher Inc..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: TLauncher.exe — f0cb809918c2bf85a8eef2bcbd35218e75426b4e5698ca1cca50acf3e5a714ce
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\starter-core-1.268-v6.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\starter-core-1.268-v6.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 5216 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5216
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.20.15.15 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
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.20.15.15 · 104.26.10.134
2 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- TLauncher.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: TLauncher Inc.
- Size
- 9.2 MB
- Last analyzed
- Aug 12, 2026, 9:53 AM UTC
f0cb809918c2bf85a8eef2bcbd35218e75426b4e5698ca1cca50acf3e5a714ceSafety & 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 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 file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- 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 TLauncher.exe safe, or is it malware?
What is TLauncher.exe?
How many antivirus engines detected TLauncher.exe?
What should I do if I already ran TLauncher.exe?
How do I remove TLauncher.exe?
What kind of malware is TLauncher.exe?
Is TLauncher.exe digitally signed?
What is the SHA-256 hash of TLauncher.exe?
How up to date is this analysis of TLauncher.exe?
Community
Member reviews and reports for this exact file hash.