Is OctoLauncher_Installer.exe safe?
No antivirus engine detected this unsigned installer, but encoded PowerShell, possible process injection, and LSASS-related activity warrant substantial caution pending publisher verification.
All 75 antivirus engines avoided a detection, and the completed sandbox did not issue a malware finding. However, the installer is unsigned and exhibited encoded PowerShell, possible process injection, and credential-access-shaped activity, so it should not be run unless its source and hash can be independently verified.
6489641b62c41a21f7…cac91561a69870Recommended 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 75 antivirus engines avoided a detection, and the completed sandbox did not issue a malware finding. However, the installer is unsigned and exhibited encoded PowerShell, possible process injection, and credential-access-shaped activity, so it should not be run unless its source and hash can be independently verified.
The strongest reassuring signal is the complete absence of detections across 75 engines, including 14 tier-1 engines reporting no detection. One completed sandbox also issued a clean result, and no inspected domain or dropped child was identified as malicious. Against that, runtime evidence maps to T1003, T1055, and T1059.001 and includes encoded PowerShell plus LSASS-related activity, which is unusually invasive for a launcher installer. The executable is unsigned and has no established publisher history to explain or authenticate those actions. Similar files sharing the imphash received five prior suspicious assessments, although those publisher-unmatched imphash links are weak because common installer frameworks can collide. These conflicting signals justify caution rather than treating either the clean engine results or the behavioral heuristics as decisive alone.
What We Detected
No antivirus engine flagged the file: 0 of 75 reported malicious or suspicious results, and 14 tier-1 engines reported no detection. The executable is unsigned, with no established signer history. It also lacks a confirmed malware-family label.
Threat Behavior
A completed sandbox run recorded encoded PowerShell and techniques mapped to credential access (T1003), process injection (T1055), and PowerShell execution (T1059.001). It also surfaced LSASS-related activity. These behaviors can occasionally arise from aggressive installer or compatibility logic, but together they are unusually sensitive for a launcher installer. The sandbox did not issue a malware finding, and none of the ten dropped files was confirmed malicious; however, all ten child verdicts remain unresolved. Reputation checks covered all six contacted domains without a malicious or suspicious hit, but the three contacted IP addresses were not fully covered, so no complete host-reputation conclusion is available.
What To Do Now
Do not run the installer unless it came directly from the publisher's official release channel and its SHA-256 hash can be independently confirmed. Keep endpoint protection enabled, and prefer a properly signed release or obtain publisher confirmation explaining the PowerShell and LSASS-related behavior.
Where this verdict could be wrong5 caveats
- No antivirus engine detected the sample: 0/75 malicious and 0/75 suspicious, including no tier-1 detection.
- The completed sandbox assigned a clean result and behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false, although all 10 inspected children lack definitive verdicts.
- externalIntel.malwareBazaar.hit=false and externalIntel.circl.hit=false; YARAify coverage was unavailable because the lookup timed out.
- The file has medium prevalence with 209 sources and 231 submissions, rather than being newly observed with negligible distribution.
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 of 75 antivirus engines reported a malicious or suspicious result
- 14 tier-1 engines reported no detection
- behaviour.hasMaliciousSandboxVerdict=false
- No malicious dropped child was confirmed among 10 inspected files
- No known-malicious or suspicious hit was found for the six inspected domains
- Unsigned Win32 executable with no signer history
- Encoded PowerShell execution observed in the sandbox
- Runtime evidence mapped to T1055 process injection
- LSASS-related activity and T1003 credential-access mapping
- Incomplete reputation coverage for three contacted IP addresses
- All 10 dropped-child verdicts remain unknown
Only use a copy obtained from the publisher's official channel after verifying this SHA-256 hash or a valid digital signature. Keep endpoint protection enabled and avoid granting elevated privileges until the observed PowerShell and LSASS-related actions are explained.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial6 of 9 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 36MITRE ATT&CK techniques
- 15spawned processes
- 9network contacts
- 35filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Accessed operating-system credential data, which can expose saved passwords.
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: Changed an auto-start location that can make code run after sign-in or restart.
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.
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
OctoLauncher_Installer.exe
6489641b62c41a21f7853eb9b341ff701d819aae2121b7f38acac91561a69870
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
powershell.exe -NoProfile -NonInteractive -EncodedCommand JABFAHIAcgBvAHIAQQBjAHQAaQBvAG4AUAByAGUAZgBlAHIAZQBuAGMAZQAgAD0AIAAiAFMAdABvAHAAIgAKACQAYgBhAHMAZQAgAD0AIAAnAEgASwBMAE0AOgBcAFMAWQBTAFQARQBNAFwAQwB1AHIAcgBlAG4AdABDAG8AbgB0AHIAbwBsAFMAZQB0AFwAQwBvAG4AdAByAG8AbABcAEMAbABhAHMAcwBcAHsANABkADMANgBlADkANgA4AC0AZQAzADIANQAtADEAMQBjAGUALQBiAGYAYwAxAC0AMAA4ADAAMAAyAGIAZQAxADAAMwAxADgAfQAnAAoAJABtAGEAeAAgAD0AIABbAGkAbgB0ADYANABdADAACgBHAGUAdAAtAEMAaABpAGwAZABJAHQAZQBtACAAJABiAGEAcwBlACAALQBFAHIAcgBvAHIAQQBjAHQAaQBvAG4AIABTAGkAbABlAG4AdABsAHkAQwBvAG4AdABpAG4AdQBlACAAfAAgAEYAbwByAEUAYQBjAGgALQBPAGIAagBlAGMAdAAgAHsACgAgACAAJABwACAAPQAgAEcAZQB0AC0ASQB0AGUAbQBQAHIAbwBwAGUAcgB0AHkAIAAkAF8ALgBQAFMAUABhAHQAaAAgAC0ARQByAHIAbwByAEEAYwB0AGkAbwBuACAAUwBpAGwAZQBuAHQAbAB5AEMAbwBuAHQAaQBuAHUAZQAKACAAIAAkAHYAIAA9ACAAWwBpAG4AdAA2ADQAXQAwAAoAIAAgAGkAZgAgACgAJABwAC4AJwBIAGEAcgBkAHcAYQByAGUASQBuAGYAbwByAG0AYQB0AGkAbwBuAC4AcQB3AE0AZQBtAG8AcgB5AFMAaQB6AGUAJwApACAAewAgACQAdgAgAD0AIABbAGkAbgB0ADYANABdACQAcAAuACcASABhAHIAZAB3AGEAcgBlAEkAbgBmAG8AcgBtAGEAdABpAG8AbgAuAHEAdwBNAGUAbQBvAHIAeQBTAGkAegBlACcAIAB9AAoAIAAgAGUAbABzAGUAaQBmACAAKAAkAHAALgAnAEgAYQByAGQAdwBhAHIAZQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4ALgBNAGUAbQBvAHIAeQBTAGkAegBlACcAKQAgAHsACgAgACAAIAAgACQAbQAgAD0AIAAkAHAALgAnAEgAYQByAGQAdwBhAHIAZQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4ALgBNAGUAbQBvAHIAeQBTAGkAegBlACcACgAgACAAIAAgAGkAZgAgACgAJABtACAALQBpAHMAIABbAGIAeQB0AGUAWwBdAF0AKQAgAHsAIAAkAHYAIAA9ACAAWwBpAG4AdAA2ADQAXQBbAFMAeQBzAHQAZQBtAC4AQgBpAHQAQwBvAG4AdgBlAHIAdABlAHIAXQA6ADoAVABvAFUASQBuAHQAMwAyACgAJABtACwAIAAwACkAIAB9ACAAZQBsAHMAZQAgAHsAIAAkAHYAIAA9ACAAWwBpAG4AdAA2ADQAXQAkAG0AIAB9AAoAIAAgAH0ACgAgACAAaQBmACAAKAAkAHYAIAAtAGcAdAAgACQAbQBhAHgAKQAgAHsAIAAkAG0AYQB4ACAAPQAgACQAdgAgAH0ACgB9AAoAVwByAGkAdABlAC0ATwB1AHQAcAB1AHQAIAAkAG0AYQB4AA==
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\OctoLauncher_Installer.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
StartupProfileData-NonInteractive
C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
04Isolated runtime analysis - Written fileObserved
powershell.exe.log
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\powershell.exe.log
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
octowow.st
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
dl.octowow.st
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.
- octowow.st
- dl.octowow.st
- a1672.dscr.akamai.net
- eip-terr-na.cdp1.digicert.com.akahost.net
- nexusrules.officeapps.live.com
- assets.msn.com
- 185.165.170.6
- 185.165.171.98
- 162.159.36.2
- HKEY_CURRENT_USER\SOFTWARE\37c94e6d-5118-5dc4-a10a-c5b4972cad87\InstallLocation
- HKEY_CURRENT_USER\SOFTWARE\37c94e6d-5118-5dc4-a10a-c5b4972cad87\KeepShortcuts
- HKEY_CURRENT_USER\SOFTWARE\37c94e6d-5118-5dc4-a10a-c5b4972cad87\ShortcutName
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\37c94e6d-5118-5dc4-a10a-c5b4972cad87\DisplayName
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\37c94e6d-5118-5dc4-a10a-c5b4972cad87\UninstallString
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\37c94e6d-5118-5dc4-a10a-c5b4972cad87\QuietUninstallString
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\powershell.exe.log
- C:\Users\<USER>\AppData\Local\Temp\nspF1E2.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nspF1E2.tmp\UAC.dll
- C:\Users\<USER>\AppData\Local\Temp\nspF1E2.tmp\StdUtils.dll
- C:\Users\<USER>\AppData\Local\Temp\nspF1E2.tmp\7z-out\chrome_100_percent.pak
- C:\Users\<USER>\AppData\Local\Temp\nspF1E2.tmp\7z-out\chrome_200_percent.pak
- C:\Users\<USER>\AppData\Local\Temp\nspF1E2.tmp\7z-out\d3dcompiler_47.dll
- C:\Users\<USER>\AppData\Local\Temp\nspF1E2.tmp\7z-out\ffmpeg.dll
- C:\Users\<USER>\AppData\Local\Temp\nspF1E2.tmp\7z-out\icudtl.dat
- 37c94e6d-5118-5dc4-a10a-c5b4972cad87
- Global\SyncRootManager
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
- Local\octo-launcherProcessSingletonStartup
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fbcfe23a2ecb82b7100c…dc0f2dNever scannednever seen before
- da3f122d19f811a0ee68…fde700Never scannednever seen before
- 96ad1146eb96877eab59…87dcf7Never scannednever seen before
- c1889d7ce46a86ff6e5b…5241c2Never scannednever seen before
- b88494c067b5ea07f287…12a38aNever scannednever seen before
- 3e48c90dbe7a43918e61…e10295Never scannednever seen before
- 5cefd01c3b64f6bfb317…0d8340Never scannednever seen before
- 9b6cc2721495313ebcea…958369Never scannednever seen before
- b1e963d702392fb72247…c0cdecNever scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never 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
- 0 / 75engines flagged
- 209sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 231 times from 209 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: OctoLauncher_Installer.exe — 6489641b62c41a21f7853eb9b341ff701d819aae2121b7f38acac91561a69870
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — powershell.exe -NoProfile -NonInteractive -EncodedCommand JABFAHIAcgBvAHIAQQBjAHQAaQBvAG4AUAByAGUAZgBlAHIAZQBuAGMAZQAgAD0AIAAiAFMAdABvAHAAIgAKACQAYgBhAHMAZQAgAD0AIAAnAEgASwBMAE0AOgBcAFMAWQBTAFQARQBNAFwAQwB1AHIAcgBlAG4AdABDAG8AbgB0AHIAbwBsAFMAZQB0AFwAQwBvAG4AdAByAG8AbABcAEMAbABhAHMAcwBcAHsANABkADMANgBlADkANgA4AC0AZQAzADIANQAtADEAMQBjAGUALQBiAGYAYwAxAC0AMAA4ADAAMAAyAGIAZQAxADAAMwAxADgAfQAnAAoAJABtAGEAeAAgAD0AIABbAGkAbgB0ADYANABdADAACgBHAGUAdAAtAEMAaABpAGwAZABJAHQAZQBtACAAJABiAGEAcwBlACAALQBFAHIAcgBvAHIAQQBjAHQAaQBvAG4AIABTAGkAbABlAG4AdABsAHkAQwBvAG4AdABpAG4AdQBlACAAfAAgAEYAbwByAEUAYQBjAGgALQBPAGIAagBlAGMAdAAgAHsACgAgACAAJABwACAAPQAgAEcAZQB0AC0ASQB0AGUAbQBQAHIAbwBwAGUAcgB0AHkAIAAkAF8ALgBQAFMAUABhAHQAaAAgAC0ARQByAHIAbwByAEEAYwB0AGkAbwBuACAAUwBpAGwAZQBuAHQAbAB5AEMAbwBuAHQAaQBuAHUAZQAKACAAIAAkAHYAIAA9ACAAWwBpAG4AdAA2ADQAXQAwAAoAIAAgAGkAZgAgACgAJABwAC4AJwBIAGEAcgBkAHcAYQByAGUASQBuAGYAbwByAG0AYQB0AGkAbwBuAC4AcQB3AE0AZQBtAG8AcgB5AFMAaQB6AGUAJwApACAAewAgACQAdgAgAD0AIABbAGkAbgB0ADYANABdACQAcAAuACcASABhAHIAZAB3AGEAcgBlAEkAbgBmAG8AcgBtAGEAdABpAG8AbgAuAHEAdwBNAGUAbQBvAHIAeQBTAGkAegBlACcAIAB9AAoAIAAgAGUAbABzAGUAaQBmACAAKAAkAHAALgAnAEgAYQByAGQAdwBhAHIAZQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4ALgBNAGUAbQBvAHIAeQBTAGkAegBlACcAKQAgAHsACgAgACAAIAAgACQAbQAgAD0AIAAkAHAALgAnAEgAYQByAGQAdwBhAHIAZQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4ALgBNAGUAbQBvAHIAeQBTAGkAegBlACcACgAgACAAIAAgAGkAZgAgACgAJABtACAALQBpAHMAIABbAGIAeQB0AGUAWwBdAF0AKQAgAHsAIAAkAHYAIAA9ACAAWwBpAG4AdAA2ADQAXQBbAFMAeQBzAHQAZQBtAC4AQgBpAHQAQwBvAG4AdgBlAHIAdABlAHIAXQA6ADoAVABvAFUASQBuAHQAMwAyACgAJABtACwAIAAwACkAIAB9ACAAZQBsAHMAZQAgAHsAIAAkAHYAIAA9ACAAWwBpAG4AdAA2ADQAXQAkAG0AIAB9AAoAIAAgAH0ACgAgACAAaQBmACAAKAAkAHYAIAAtAGcAdAAgACQAbQBhAHgAKQAgAHsAIAAkAG0AYQB4ACAAPQAgACQAdgAgAH0ACgB9AAoAVwByAGkAdABlAC0ATwB1AHQAcAB1AHQAIAAkAG0AYQB4AA==
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\Desktop\OctoLauncher_Installer.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: StartupProfileData-NonInteractive — C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: powershell.exe.log — C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\powershell.exe.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: octowow.st — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: dl.octowow.st — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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.
Sample spawned PowerShell with an encoded, Base64, or Invoke-Expression payload. Near-universal first-stage malware loader pattern.
Evidencepowershell.exe -NoProfile -NonInteractive -EncodedCommand JABFAHIAcgBvAHIAQQBjAHQAaQBvAG4AUAByAGUAZgBlAHIAZQBuAGMAZQAgAD0AIAAiAFMAdABvAHAAIgAKACQAYgBhAHMAZQAgAD0AIAAnAEgASwBMAE0AOgBcAFMAWQBTAFQARQBNAFwAQwB1AHIAcgBlAG4Ad…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.exe
0 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
- OctoLauncher_Installer.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 80.8 MB
- Last analyzed
- Sep 28, 2026, 10:02 AM UTC
6489641b62c41a21f7853eb9b341ff701d819aae2121b7f38acac91561a69870Safety & 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 OctoLauncher_Installer.exe safe, or is it malware?
What is OctoLauncher_Installer.exe?
How many antivirus engines detected OctoLauncher_Installer.exe?
I already downloaded and installed OctoLauncher_Installer.exe — what should I do?
How do I remove OctoLauncher_Installer.exe?
What is the SHA-256 hash of OctoLauncher_Installer.exe?
How up to date is this analysis of OctoLauncher_Installer.exe?
Community
Member reviews and reports for this exact file hash.