Is Launcher_Installer_v17.x64.exe safe?
No antivirus engine identified a threat, but process-injection-related behavior and an unestablished signer justify caution until the installer’s source is verified.
All 74 antivirus engines avoided flagging this signed installer, and the sandbox issued no malicious conclusion. However, the run mapped activity to T1055 and T1134, the signer lacks established history, and host-reputation coverage was incomplete, so use it only if obtained from the expected official source.
51d2e7c68d58d348c7…77c927c9354f06Recommended 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.
All 74 antivirus engines avoided flagging this signed installer, and the sandbox issued no malicious conclusion. However, the run mapped activity to T1055 and T1134, the signer lacks established history, and host-reputation coverage was incomplete, so use it only if obtained from the expected official source.
The strongest favorable evidence is that 0 of 74 engines reported a malicious or suspicious result, including no tier-1 detections. The executable has a verified signature, although the signer is neither a curated trusted publisher nor supported by historical sample statistics. One completed sandbox run mapped activity to T1055 and T1134, but it produced no malicious sandbox verdict or persistence indicators. Two dropped children were inspected without a malicious finding, and researcher-curated intelligence supplied no matching rules or known-malware record. The host cross-check inspected only three hosts despite additional observed no complete contacted-host reputation result was available networking. Overall, the unusual runtime mappings prevent an unqualified benign assessment despite the otherwise favorable detection picture.
What We Detected
No malicious or suspicious result was reported by 74 antivirus engines, and no tier-1 engine flagged the sample. The executable is signed with a verified certificate issued to “IP Korolenko Alexander Alexandrovich,” but that signer has no established sample history and is not on the curated trusted-publisher list.
Threat Behavior
One sandbox run mapped activity to MITRE techniques T1055 and T1134, which can represent process injection and access-token manipulation. The sandbox did not issue a malicious verdict, recorded no persistence indicators, and the two inspected dropped files were not identified as malicious. Network activity included four IP addresses and five URLs; only three hosts were cross-checked, so complete host-reputation coverage is unavailable.
What To Do Now
Confirm that the file hash and signer match the publisher’s official release before running it. Keep endpoint protection enabled, and avoid execution if the installer came from an advertisement, mirror, unsolicited message, or other unverified source.
Where this verdict could be wrong4 caveats
- T1055 and T1134 are offensive-capability mappings that warrant caution even though the sandbox produced no malicious verdict.
- The contactedHosts block inspected 3 hosts despite four observed IPs and five URLs, so no complete host-reputation result is available.
- The verified signer has no historical sample record and is not matched by signing.trustedPublisher.matched.
- Three imphash-only similar files previously received suspicious verdicts, although their differing signers make those installer-framework matches weak.
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/74 engines reported a malicious or suspicious result.
- engines.tier1Malicious=0, with 11 tier-1 engines reporting no detection.
- signing.verified=true and brandMismatch is not detected.
- behaviour.hasMaliciousSandboxVerdict=false and no persistence indicators were recorded.
- droppedChildren.hasMaliciousChild=false for 2 inspected children.
- Runtime evidence mapped activity to MITRE T1055 and T1134.
- The verified signer has no historical sample statistics.
- The signer is not matched by signing.trustedPublisher.matched.
- Host-reputation coverage did not clearly include every observed network contact.
- The file’s overall entropy is high, although peAnalysis.highEntropyCode=false and likelyPacked=false.
Run it only after confirming the SHA-256 and signer through the expected publisher’s official release channel. Keep antivirus and endpoint protection enabled, and discard the installer if its origin cannot be verified.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 7 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
- 16MITRE ATT&CK techniques
- 7spawned processes
- 9network contacts
- 4filesystem & 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: Checked the environment for virtualisation or analysis tools.
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
Launcher_Installer_v17.x64.exe
51d2e7c68d58d348c7c06af0900c66aa2974580917930f2eaf77c927c9354f06
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Launcher_Installer_v17.x64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-MEGD8.tmp\Launcher_Installer_v17.x64.tmp" /SL5="$1E0036,62608391,954880,C:\Users\<USER>\Desktop\Launcher_Installer_v17.x64.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Launcher_Installer_v17.x64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-MEGD8.tmp\Launcher_Installer_v17.x64.tmp
04Isolated runtime analysis - Written fileObserved
Launcher_Installer_v17.x64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-2OAUK.tmp\Launcher_Installer_v17.x64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
185.93.1.242
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
104.21.64.14
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.
- 185.93.1.242
- 104.21.64.14
- 216.152.144.252
- 162.159.36.2
- http://rustexremakecdn.b-cdn.net/launcherV2/manifest.json
- http://cdn.rustexremake.com/launcherV2/manifest.json
- http://aa68edc5-a17f-477a-b392-efce94672945.selcdn.net/launcherV2/manifest.json
- http://rustexremakecdn.b-cdn.net/launcherV2/app.jar
- http://rustexremakecdn.b-cdn.net/launcherV2/runtime.zip
- C:\Users\<USER>\AppData\Local\Temp\is-MEGD8.tmp\Launcher_Installer_v17.x64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-2OAUK.tmp\Launcher_Installer_v17.x64.tmp
- C:\Users\user\AppData\Local\Temp\is-1IC9J.tmp
- C:\Users\user\AppData\Local\Temp\is-1IC9J.tmp\Launcher_Installer_v17.x64.tmp
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- c227960fa83062933369…e7b545Never scannednever seen before
- c69e38b2e349ed085680…1bf215Never 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
- 0 / 74engines flagged
- 178sources 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
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from IP Korolenko Alexander Alexandrovich.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Launcher_Installer_v17.x64.exe — 51d2e7c68d58d348c7c06af0900c66aa2974580917930f2eaf77c927c9354f06
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Launcher_Installer_v17.x64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-MEGD8.tmp\Launcher_Installer_v17.x64.tmp" /SL5="$1E0036,62608391,954880,C:\Users\<USER>\Desktop\Launcher_Installer_v17.x64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Launcher_Installer_v17.x64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-MEGD8.tmp\Launcher_Installer_v17.x64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Launcher_Installer_v17.x64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-2OAUK.tmp\Launcher_Installer_v17.x64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 185.93.1.242 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 104.21.64.14 — 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\DllHost.exe /Processid:{F32D97DF-E3E5-4CB9-9E3E-0EB5B4E49801}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.
Evidence185.93.1.242 · 104.21.64.14 · 216.152.144.252
0 of 74 engines flagged this file
View all 74 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
- Launcher_Installer_v17.x64.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: IP Korolenko Alexander Alexandrovich
- Size
- 60.6 MB
- Last analyzed
- Sep 19, 2026, 7:53 AM UTC
51d2e7c68d58d348c7c06af0900c66aa2974580917930f2eaf77c927c9354f06Safety & 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 Launcher_Installer_v17.x64.exe safe, or is it malware?
What is Launcher_Installer_v17.x64.exe?
How many antivirus engines detected Launcher_Installer_v17.x64.exe?
What should I do if I already installed Launcher_Installer_v17.x64.exe?
How do I remove Launcher_Installer_v17.x64.exe?
Is Launcher_Installer_v17.x64.exe digitally signed?
What is the SHA-256 hash of Launcher_Installer_v17.x64.exe?
How up to date is this analysis of Launcher_Installer_v17.x64.exe?
Community
Member reviews and reports for this exact file hash.