Is LegacyLauncher.exe safe?
Unsigned 117 MB launcher shares imphash with known OfferCore PUA samples and exhibits process-injection plus direct-IP behaviour.
One low-trust engine flagged the file; four of five similar-imphash samples were previously classified malicious as OfferCore PUA. Sandbox observed T1055/T1485/T1548 techniques, yet no tier-1 consensus or malicious child files exist.
a092da5c6df6c6be43…4b947457824ac4Recommended 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.
One low-trust engine flagged the file; four of five similar-imphash samples were previously classified malicious as OfferCore PUA. Sandbox observed T1055/T1485/T1548 techniques, yet no tier-1 consensus or malicious child files exist.
The single low-trust detection and unsigned status keep the file out of the safe band, while the absence of tier-1 consensus and lack of confirmed malicious children prevent a malicious verdict. The imphash matches to OfferCore samples provide the strongest malicious signal, tempered by medium prevalence and mixed community comments.
What We Detected
75 engines scanned the 117 MB LegacyLauncher.exe; only Trapmine (low_trust) returned a suspicious ML score. No tier-1 engine flagged the sample. The binary is unsigned and contains three MITRE techniques (T1055 process injection, T1485 data destruction, T1548 privilege escalation) observed during one sandbox execution.
Threat Behavior
The file wrote ten child executables and contacted two raw IP addresses. Four of five prior files sharing the same imphash were classified malicious under the OfferCore family; the fifth was marked suspicious. No dropped child has a known malicious verdict and external-intel sources (CIRCL, MalwareBazaar, YARAify) returned no hits.
What To Do Now
Do not run the file on production systems. If already executed, review running processes for unexpected injection and inspect the two contacted IPs (104.26.10.81, 188.72.103.3) against current threat lists. Keep endpoint protection enabled.
Where this verdict could be wrong2 caveats
- One community comment explicitly tags the file #SAFE; another states "No virus".
- contactedHosts is null — no complete host-reputation cross-check available for the two observed IPs.
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
- Medium prevalence across 3729 submitters
- Unsigned executable
- Imphash collision with known OfferCore samples
- Observed T1055/T1485/T1548 techniques
- Direct-IP network traffic without domain resolution
Treat as potentially unwanted; sandbox or block pending further reputation data.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 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
- 22MITRE ATT&CK techniques
- 11spawned processes
- 2network 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: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Transferred a file over the network; malware can use this to fetch additional payloads.
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
LegacyLauncher.exe
a092da5c6df6c6be4341846f43425006ee0da2ce96953cf98a4b947457824ac4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\system32\services.exe
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\System32\GameBarPresenceWriter.exe" -ServerName:Windows.Gaming.GameBar.Internal.PresenceWriterServer
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
LegacyLauncher.tmp
C:\Users\<USER>\AppData\Local\Temp\is-H3WOZGZMG3.tmp\LegacyLauncher.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-7P3BLKKW1H.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.26.10.81
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
188.72.103.3
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.
- 104.26.10.81
- 188.72.103.3
- C:\Users\<USER>\AppData\Local\Temp\is-H3WOZGZMG3.tmp\LegacyLauncher.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-7P3BLKKW1H.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_256.db
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_48.db
- C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\XboxLive\AuthStateCache.dat
- C:\Users\<USER>\AppData\Local\Microsoft\XboxLive\AuthStateCache.dat
- C:\Users\<USER>\AppData\Roaming\.tlauncher\legacy\Minecraft\is-J1PQRIRBOE.tmp
- C:\Users\<USER>\AppData\Roaming\.tlauncher\legacy\Minecraft\is-M9BQ8954G5.tmp
- C:\Users\<USER>\AppData\Roaming\.tlauncher\legacy\Minecraft\is-XJZDWZR74N.tmp
- cversions.3.m
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 7cc60f1f36f6a1ed8218…3c871aNever scannednever seen before
- 8a8f81cf9b359e3f6dfa…8e8064Never scannednever seen before
- bbb82aadb5e4209527c1…c538e8Never scannednever seen before
- dc1a95e73eb04db93451…b3d30eNever scannednever seen before
- 52c220c2520acce9b79c…302819Never scannednever seen before
- a56e782b5b50811ac204…660fccNever scannednever seen before
- 6f1fd322c52bef87a624…f787ffNever scannednever seen before
- f5f8ef90609e64fec82e…de4dfbNever scannednever seen before
- 1f11fe54a7dfb0e410e2…770787Never scannednever seen before
- 09ba7517c8a9b30780ff…4b6c4eNever 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
- 1 / 75engines flagged
- 3,729sources 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
1 of 75 antivirus engines flagged the file, including Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 45,604 times from 3,729 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: LegacyLauncher.exe — a092da5c6df6c6be4341846f43425006ee0da2ce96953cf98a4b947457824ac4
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\System32\GameBarPresenceWriter.exe" -ServerName:Windows.Gaming.GameBar.Internal.PresenceWriterServer
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: LegacyLauncher.tmp — C:\Users\<USER>\AppData\Local\Temp\is-H3WOZGZMG3.tmp\LegacyLauncher.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-7P3BLKKW1H.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.26.10.81 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 188.72.103.3 — 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\Explorer.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.
Evidence104.26.10.81 · 188.72.103.3
1 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
- LegacyLauncher.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 111.9 MB
- Last analyzed
- Aug 24, 2026, 5:30 AM UTC
a092da5c6df6c6be4341846f43425006ee0da2ce96953cf98a4b947457824ac4Safety & 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 LegacyLauncher.exe safe, or is it malware?
What is LegacyLauncher.exe?
How many antivirus engines detected LegacyLauncher.exe?
I already downloaded and ran LegacyLauncher.exe — what should I do?
How do I remove LegacyLauncher.exe?
What kind of malware is LegacyLauncher.exe?
What is the SHA-256 hash of LegacyLauncher.exe?
How up to date is this analysis of LegacyLauncher.exe?
Community
Member reviews and reports for this exact file hash.
