Is SKlauncher_3.2.18_Setup.exe safe?
Unsigned installer with process-injection indicators and six YARA matches but no tier-1 consensus.
One tier-2 engine flagged the file as dropper-like while 17 tier-1 engines stayed silent. Sandbox activity shows process injection and LSASS access, yet the sample is widely submitted and has no malicious children or confirmed malicious hosts.
5d7f6d20b4de8c600f…c8785a63b68997Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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 tier-2 engine flagged the file as dropper-like while 17 tier-1 engines stayed silent. Sandbox activity shows process injection and LSASS access, yet the sample is widely submitted and has no malicious children or confirmed malicious hosts.
The single Skyhigh detection is low-severity and lacks tier-1 support. Unsigned status and YARA hits for injection and TLS anomalies raise concern, but the file's age, high submission count, and clean tier-1 majority keep the risk moderate. No sandbox verdict or malicious dropped children were observed.
What We Detected
75 engines scanned the file; only Skyhigh reported a dropper-like behaviour. Six YARA rules fired, including process-injection and TLS-section heuristics. The executable is unsigned and contains MITRE techniques T1055 (process injection) and T1485 (data destruction).
Threat Behavior
Sandbox execution wrote multiple temporary files, launched javaw.exe, and contacted 13 IP addresses directly. No malicious child files or known-bad hosts were confirmed. LSASS access was observed but not corroborated by tier-1 engines.
What To Do Now
Do not run the installer on production systems. Keep endpoint protection enabled and consider obtaining the launcher from its official distribution channel if needed.
Where this verdict could be wrong2 caveats
- engines.tier1Malicious=0 and 17 tier-1 engines reported clean
- contactedHosts.maliciousHosts.length=0 for the 2 inspected hosts
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
- Widely submitted (common_old)
- No malicious dropped children
- Unsigned executable
- Process-injection indicators (T1055)
- LSASS access observed
- Six YARA rules matched
Treat as untrusted; obtain the launcher only from verified official sources and keep security software active.
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 of 15 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete8 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
- 26network 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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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: Scans through your files and folders.
Moderate concern: Decoded or unpacked concealed content while running.
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_3.2.18_Setup.exe
5d7f6d20b4de8c600f81d64b4608bb65bccf92bfc72a727831c8785a63b68997
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-4ANE5RI8UM.tmp\file.tmp" /SL5="$4003C,2154364,841216,C:\Users\<USER>\Desktop\file.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
file.tmp
C:\Users\<USER>\AppData\Local\Temp\is-4ANE5RI8UM.tmp\file.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-7NEQI6CURV.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
172.64.152.44
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
185.199.109.153
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.
- 172.64.152.44
- 185.199.109.153
- 185.199.111.153
- 13.107.226.70
- 172.67.199.2
- 142.250.107.101
- 104.21.58.14
- 13.107.253.69
- 104.16.80.73
- 173.194.203.102
- https://cdn.azul.com/zulu/bin/zulu21.46.19-ca-jre21.0.9-win_x64.zip
- https://maven.skmedix.pl/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2-win.jar
- https://maven.skmedix.pl/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2-win.jar.sha1
- https://maven.skmedix.pl/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2-win.jar
- https://maven.skmedix.pl/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2-win.jar.sha1
- https://maven.skmedix.pl/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2-win.jar
- C:\Users\<USER>\AppData\Local\Temp\is-4ANE5RI8UM.tmp\file.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-7NEQI6CURV.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-7NEQI6CURV.tmp\_isetup\_isdecmp.dll
- C:\Users\<USER>\AppData\Local\Temp\is-7NEQI6CURV.tmp\_isetup\_is7z.dll
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db
- C:\Users\<USER>\AppData\Roaming\sklauncher\is-K7B0OMMCDQ.tmp
- C:\Users\<USER>\AppData\Roaming\sklauncher\is-OC096D7Z0Y.tmp
- C:\Users\<USER>\AppData\Roaming\sklauncher\is-C6AFGDOVKM.tmp
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\SKlauncher\SKlauncher.lnk
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\SKlauncher\SKlauncher.pif
- cversions.3.m
- Local\SessionImmersiveColorMutex
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- DefaultTabtip-MainUI
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 942c7f45e3ee02dae9ac…a019ddNever scannednever seen before
- 2ee3d52640d84ac4f7f7…85ca97Never scannednever seen before
- 655bade7ff61f01a803e…033e6fNever scannednever seen before
- 12bb3f480ec115d5f944…bc4d19Never scannednever seen before
- 598c5cfc2b5ce7f9c874…fefa94Never scannednever seen before
- c36f5c0ac5d91a841786…8c3d1eNever scannednever seen before
- 113923bc9057678a9717…fff4d4Never scannednever seen before
- 197a57651e3014f9f3cf…101bfaNever scannednever seen before
- 51a73fbfa2afe5e45962…fe70cbNever scannednever seen before
- f901b0bc8c00b3afc80e…ad63c8Never 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.
- 8rule hits recorded
- 1 / 75engines flagged
- 3,708sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including Skyhigh.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 3,708 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: SKlauncher_3.2.18_Setup.exe — 5d7f6d20b4de8c600f81d64b4608bb65bccf92bfc72a727831c8785a63b68997
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-4ANE5RI8UM.tmp\file.tmp" /SL5="$4003C,2154364,841216,C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: file.tmp — C:\Users\<USER>\AppData\Local\Temp\is-4ANE5RI8UM.tmp\file.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-7NEQI6CURV.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 172.64.152.44 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 185.199.109.153 — 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.
- Borland
- CP_Script_Inject_Detector
- HUNTING_SUSP_TLS_SECTION
- pe_detect_tls_callbacks
- SHA512_Constants
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.EXESandbox 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.
Evidence172.64.152.44 · 185.199.109.153 · 185.199.111.153
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
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_3.2.18_Setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 3.6 MB
- Last analyzed
- Aug 15, 2026, 1:30 PM UTC
5d7f6d20b4de8c600f81d64b4608bb65bccf92bfc72a727831c8785a63b68997Safety & 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 install 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. Download a fresh installer 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_3.2.18_Setup.exe safe, or is it malware?
What is SKlauncher_3.2.18_Setup.exe?
How many antivirus engines detected SKlauncher_3.2.18_Setup.exe?
What should I do if I already installed SKlauncher_3.2.18_Setup.exe?
How do I remove SKlauncher_3.2.18_Setup.exe?
What is the SHA-256 hash of SKlauncher_3.2.18_Setup.exe?
How up to date is this analysis of SKlauncher_3.2.18_Setup.exe?
Community
Member reviews and reports for this exact file hash.
