Is Proxima.Launcher_1.4.9_x64-setup.exe safe?
Unsigned installer shows sandbox process-injection and LSASS access despite zero AV detections.
Zero engines flagged the file, yet sandbox evidence includes T1055 process injection and LSASS access. Similar imphash samples were previously rated suspicious. The combination of unsigned status and offensive techniques outweighs the clean engine results.
f247e85f714d396fce…d4934a322e006bRecommended 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.
Zero engines flagged the file, yet sandbox evidence includes T1055 process injection and LSASS access. Similar imphash samples were previously rated suspicious. The combination of unsigned status and offensive techniques outweighs the clean engine results.
All 75 engines returned clean, but the sandbox recorded LSASS reads and process injection mapped to T1055, T1134, and T1485. The file is unsigned and the imphash matches three prior samples that triggered borderline verdicts. Prevalence is common_new, yet the offensive techniques and lack of signing create mixed signals that prevent a safe classification.
What We Detected
75 antivirus engines scanned the 6.1 MB installer and none returned a malicious or suspicious label. Sandbox execution revealed three MITRE techniques normally associated with credential dumping and injection: T1055, T1134, and T1485. The sample wrote ten child files, none of which matched known malware in our cache.
Threat Behavior
Runtime traces show the installer touched lsass.exe and performed process injection. Network activity was limited to Microsoft certificate-revocation and Edge WebView2 endpoints; no complete contacted-host reputation result was available were contacted. The binary is unsigned and carries no established signer history.
What To Do Now
Run the installer only in a controlled environment or virtual machine. Keep Windows Defender and other endpoint protection enabled. Monitor for unexpected child processes or persistence mechanisms after installation.
Where this verdict could be wrong2 caveats
- contactedHosts.inspected=3, maliciousHosts.length=0; sandbox contacted only Microsoft CRL and Edge WebView2 domains.
- droppedChildren.rollup.malicious=0 across 10 inspected children.
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 detections across 75 engines
- No malicious dropped children
- no complete contacted-host reputation result was available
- Common_new prevalence with 131 submitters
- Unsigned executable
- Sandbox observed LSASS access
- Process-injection techniques flagged
- Three of four similar imphash samples previously rated suspicious
Treat as potentially risky; do not run on production systems until further reputation or signing evidence appears.
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
Partial3 of 4 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 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
- 28MITRE ATT&CK techniques
- 11spawned processes
- 6network contacts
- 34filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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
Proxima.Launcher_1.4.9_x64-setup.exe
f247e85f714d396fcea3dfef9d77af75119056ee00d1bb4c3ad4934a322e006b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Proxima.Launcher_1.4.9_x64-setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nsbC1CA.tmp
C:\Users\<USER>\AppData\Local\Temp\nsbC1CA.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsrC229.tmp\System.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
crl.microsoft.com
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.
- 162.159.36.2
- http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl
- http://crl.microsoft.com/pki/crl/products/WinPCA.crl
- http://crl.microsoft.com/pki/crl/products/MicrosoftTimeStampPCA.crl
- https://go.microsoft.com/fwlink/p/?LinkId=2124703
- https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/f22cd250-2575-4cca-a00b-085ed94eace9/MicrosoftEdgeWebview2Setup.exe
- C:\Users\<USER>\AppData\Local\Temp\nsbC1CA.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsrC229.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsrC229.tmp\modern-header.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsrC229.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsrC229.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\<USER>\AppData\Local\Temp\nsoA876.tmp
- C:\Users\<USER>\AppData\Local\Temp\nseA9C0.tmp
- C:\Program Files (x86)\Microsoft\Temp\EU8B0F.tmp
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
- Local\MSCTF.Asm.MutexDefault1
- DefaultTabtip-MainUI
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- e738c6d7ccb9254eb586…8de5a8Never scannednever seen before
- 1612c3b6a648949983ac…4fa7f3Never scannednever seen before
- f6c541919cb19adad110…57f982Never scannednever seen before
- b1350f487692057c8ffd…551fc0Never scannednever seen before
- 9baee42d66f715bba878…b40256Never scannednever seen before
- 7b030b89b3ff2e4a4b07…424680Never scannednever seen before
- 2618a53029717f50d695…44bd82Never scannednever seen before
- 8b4c47c4cf5e76ec57dd…90d37cNever scannednever seen before
- 5ba143b5db4a87d32d6e…ad4709Never scannednever seen before
- 0d5cd37ce671f3bda186…468144Never 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
- 131sources 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 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 150 times from 131 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Proxima.Launcher_1.4.9_x64-setup.exe — f247e85f714d396fcea3dfef9d77af75119056ee00d1bb4c3ad4934a322e006b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Proxima.Launcher_1.4.9_x64-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nsbC1CA.tmp — C:\Users\<USER>\AppData\Local\Temp\nsbC1CA.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nsrC229.tmp\System.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: crl.microsoft.com — 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\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.
Evidence162.159.36.2
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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- Proxima.Launcher_1.4.9_x64-setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 5.9 MB
- Last analyzed
- Aug 15, 2026, 12:57 PM UTC
f247e85f714d396fcea3dfef9d77af75119056ee00d1bb4c3ad4934a322e006bSafety & 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 Proxima.Launcher_1.4.9_x64-setup.exe safe, or is it malware?
What is Proxima.Launcher_1.4.9_x64-setup.exe?
How many antivirus engines detected Proxima.Launcher_1.4.9_x64-setup.exe?
I already downloaded and installed Proxima.Launcher_1.4.9_x64-setup.exe — what should I do?
How do I remove Proxima.Launcher_1.4.9_x64-setup.exe?
What is the SHA-256 hash of Proxima.Launcher_1.4.9_x64-setup.exe?
How up to date is this analysis of Proxima.Launcher_1.4.9_x64-setup.exe?
Community
Member reviews and reports for this exact file hash.