Is SKlauncher 2.8.exe safe?
Unsigned 2015-era EXE with one tier-2 adware flag, process-injection behaviour, and direct-IP contacts but no tier-1 consensus.
Single low-tier adware detection from Zillya; unsigned with T1055 process injection and direct-IP C2 indicators observed in sandbox. Common-old prevalence and clean dropped children reduce risk but behaviour heuristics keep the file in mixed-signals territory.
64cd424ac3969f7b6c…69bcb8d62d1b05Recommended 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.
Single low-tier adware detection from Zillya; unsigned with T1055 process injection and direct-IP C2 indicators observed in sandbox. Common-old prevalence and clean dropped children reduce risk but behaviour heuristics keep the file in mixed-signals territory.
The file shows classic borderline traits: minimal engine coverage (only one tier-2 malicious label), unsigned status, and sandbox evidence of process injection plus direct-IP communication. Prevalence data indicates long-term distribution without widespread malicious reputation. No tier-1 engines or family consensus support a malicious call, yet the offensive MITRE techniques and heuristic triggers prevent a clean safe verdict.
What We Detected
One tier-2 engine (Zillya) flagged the sample as Adware.Eorezo.Win32.17620. No tier-1 engines reported malicious. The file is unsigned and has no signer history. Sandbox analysis recorded T1055 process injection and T1562.001 defence-evasion techniques along with direct-IP contacts to 20 addresses and zero DNS resolutions.
Threat Behavior
Observed execution spawns javaw.exe and writes files under .minecraft and Java usage directories. Direct-IP C2 pattern and injection into iexplore.exe are noted but no malicious dropped children or known-malicious hosts were confirmed. External CIRCL reference points to malshare.com.
What To Do Now
Run the file only in an isolated environment if testing is required. Verify the source of SKlauncher before execution. Consider scanning with additional tools or waiting for broader engine coverage.
Where this verdict could be wrong2 caveats
- If the single Zillya adware label reflects a bundled PUA rather than core malware, the overall signal remains weak given tier1Malicious=0 and unsigned status.
- Direct-IP contacts and process-injection behaviour could be legitimate for a Java-based Minecraft launcher (javaw.exe usage observed) but still raise suspicion without signer verification.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Common-old prevalence (387 submissions)
- No tier-1 malicious detections
- No malicious dropped children
- No malicious sandbox verdicts
- Unsigned executable
- Process injection (T1055) observed
- Direct-IP contacts without DNS
- Single adware label from tier-2 engine
Treat as suspicious pending further verification; do not execute on production systems without isolation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 22 contacted hosts were cross-checked; coverage is incomplete.
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
- 18MITRE ATT&CK techniques
- 10spawned processes
- 24network contacts
- 40filesystem & 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: Used an input-capture technique that can record credentials or keystrokes.
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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
SKlauncher 2.8.exe
64cd424ac3969f7b6cc24d0270a25a08358e11bc21bac9092d69bcb8d62d1b05
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\SKlauncher 2.8.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\AppData\Local\Temp\SKlauncher 2.8.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
2924
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_admin\2924
04Isolated runtime analysis - Written fileObserved
cce3fe3b0d8d8401.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\cce3fe3b0d8d8401.timestamp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:7400:6100:6e00:6400:6200:7900
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.132.105
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.
- a83f:8110:7400:6100:6e00:6400:6200:7900
- 20.99.132.105
- a83f:8110:0:0:100:0:1800:0
- 23.216.147.64
- 20.99.133.109
- 23.216.147.76
- 20.99.184.37
- a83f:8110:f80f:46f3:8609:ce9e:dce3:b686
- 192.229.211.108
- 20.99.186.246
- http://s1.skmedix.pl/launcher/2.8/sklauncher.json
- http://s1.skmedix.pl/launcher/2.8/sklauncher.json/
- http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl
- http://crl.microsoft.com/pki/crl/products/WinPCA.crl
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_admin\2924
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\cce3fe3b0d8d8401.timestamp
- C:\ProgramData\Oracle\Java\.oracle_jre_usage
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8080.timestamp
- C:\Users\user\AppData\Local\Temp\hsperfdata_user
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c7c05.timestamp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD0B.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1C.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD2D.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER19DC.tmp.WERInternalMetadata.xml
- Local\__DDrawExclMode__
- Local\__DDrawCheckExclMode__
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 30486e68f76baab82133…5c285fNever scannednever seen before
- 93babcc66ef22dfc9e14…a5e8b5Never scannednever seen before
- 509eb3d47d81e6b052fe…d5d543Never scannednever seen before
- 0b75acf854f2f020bb49…0485c4Never scannednever seen before
- e0277fd504bda3bd7b6e…7a20eeNever scannednever seen before
- 650802f59259082d848f…ed02c4Never scannednever seen before
- 1ea4f71cedf08ae8014f…e96a6fNever scannednever seen before
- 1d08f16f4929b292bbf9…fbbee9Never scannednever seen before
- 550a4f11378f0ee9049a…2d2d3aNever scannednever seen before
- 394987d67c32ef2113cc…ab3f1eNever 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 / 76engines flagged
- 295sources 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 76 antivirus engines flagged the file, including Zillya.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 295 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: SKlauncher 2.8.exe — 64cd424ac3969f7b6cc24d0270a25a08358e11bc21bac9092d69bcb8d62d1b05
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\SKlauncher 2.8.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\AppData\Local\Temp\SKlauncher 2.8.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 2924 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_admin\2924
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: cce3fe3b0d8d8401.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\cce3fe3b0d8d8401.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:7400:6100:6e00:6400:6200:7900 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.99.132.105 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Program Files\Internet Explorer\iexplore.exe C:\Program Files\Internet Explorer\iexplore.exe" -nohome"The 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.
Evidencea83f:8110:7400:6100:6e00:6400:6200:7900 · 20.99.132.105 · a83f:8110:0:0:100:0:1800:0
1 of 76 engines flagged this file
View all 76 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- SKlauncher 2.8.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 2.9 MB
- Last analyzed
- Jul 5, 2026, 9:10 AM UTC
64cd424ac3969f7b6cc24d0270a25a08358e11bc21bac9092d69bcb8d62d1b05Safety & 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 SKlauncher 2.8.exe safe, or is it malware?
What is SKlauncher 2.8.exe?
How many antivirus engines detected SKlauncher 2.8.exe?
What should I do if I already ran SKlauncher 2.8.exe?
How do I remove SKlauncher 2.8.exe?
What is the SHA-256 hash of SKlauncher 2.8.exe?
How up to date is this analysis of SKlauncher 2.8.exe?
Community
Member reviews and reports for this exact file hash.
