Is BeSightLauncher.ps1 safe?
No antivirus engine detected this PowerShell script, but sandbox mappings to credential access and process injection justify caution pending source verification.
All 75 antivirus engines returned no detection, including 17 tier-1 engines, and the available sandbox did not issue a malware finding. However, that run mapped the script to credential-dumping, credential-store access, and process-injection techniques, while all eight dropped children remain unresolved, so execution should be deferred until the source and code are verified.
a8ad7bc4ac83b5b01d…56ba141953f33cRecommended 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.
All 75 antivirus engines returned no detection, including 17 tier-1 engines, and the available sandbox did not issue a malware finding. However, that run mapped the script to credential-dumping, credential-store access, and process-injection techniques, while all eight dropped children remain unresolved, so execution should be deferred until the source and code are verified.
The script received no detections from 75 antivirus engines, including 17 tier-1 engines, which strongly reduces the likelihood of recognized malware. One completed sandbox run did not produce a malware verdict and recorded no network contacts. Nevertheless, the runtime record maps activity to T1003, T1055, T1552.001, T1555, and T1555.003, including credential-access and process-injection behavior. Those mappings are not proof of malicious intent, but they are too consequential to dismiss solely because signature engines were silent. Eight dropped files were inspected without a confirmed malicious child, though each remains unresolved rather than established as benign. No family identification or external research corroboration is available, leaving materially mixed evidence.
What We Detected
The PowerShell script was not flagged by any of 75 antivirus engines, and all 17 participating tier-1 engines reported no detection. No named threat family was identified, and the external research checks returned no matching malware database entry or YARA rule.
Threat Behavior
One sandbox run completed without a malware verdict and recorded no contacted domains, IP addresses, or URLs. However, the runtime evidence was mapped to seven offensive techniques, including T1003 for credential dumping, T1055 for process injection, T1552.001 for credentials in files, and T1555/T1555.003 for credential-store and browser-credential access. These mappings can occasionally arise from broad behavioral classification, but they represent sensitive capabilities that warrant review. The script also launched PowerShell with execution-policy bypass or unrestricted settings and wrote another temporary PowerShell file.
What To Do Now
Do not run the script on a production or personal system until its origin and code are verified. Review the script for credential collection, injection-related API use, obfuscated content, downloaded executables, and the purpose of the eight dropped files; keep endpoint protection enabled during any isolated testing.
Where this verdict could be wrong3 caveats
- The complete 0/75 detection result, including 17 tier-1 engines without detections, weighs strongly against known commodity malware.
- behaviour.sandboxVerdicts[0].verdict is clean and behaviour.hasMaliciousSandboxVerdict=false, although only one sandbox run was available.
- No external-intelligence source identified this hash, but absent rule or database hits can reflect coverage gaps.
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/75 antivirus engines reported a detection
- 17 tier-1 engines reported no detection
- The completed sandbox did not issue a malware verdict
- No network contacts were recorded during the run
- No external-intelligence source identified the hash
- Runtime mapping to T1003 credential dumping
- Runtime mapping to T1055 process injection
- Credential-access mappings T1552.001, T1555, and T1555.003
- PowerShell launched with execution-policy bypass or unrestricted settings
- Eight dropped children remain unresolved
- Unsigned PowerShell script with no established publisher history
Avoid execution until the script and all dropped components have been manually reviewed and their source authenticated. If testing is necessary, use an isolated disposable environment and keep endpoint protection enabled.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 23MITRE ATT&CK techniques
- 7spawned processes
- 0network contacts
- 22filesystem & 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: Searched files or settings where passwords and keys may be stored.
High concern: Accessed browser or password-store data that may contain saved logins.
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
BeSightLauncher.ps1
a8ad7bc4ac83b5b01d6b77fdcc4e11695fe0b9918ff4d38a2656ba141953f33c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\Desktop\BeSightLauncher.ps1"
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
Windows PowerShell.lnk
C:\Users\<USER>\Desktop\%AppData%\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk
04Isolated runtime analysis - Written fileObserved
UNQRIMFACRY6VUPD9UN5.temp
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\UNQRIMFACRY6VUPD9UN5.temp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting\Debug\StoreLocation
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\SystemCertificates\Root\Certificates\0174E68C97DDF1E0EEEA415EA336A163D2B61AFD\Blob
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Windows\Windows Error Reporting\Debug\StoreLocation
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Shell\Bags\1\Desktop\IconLayouts
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Shell\Bags\1\Desktop\IconNameVersion
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SessionInfo\1\ApplicationViewManagement\W32:000000000001021A\VirtualDesktop
- C:\Users\<USER>\Desktop\%AppData%\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\UNQRIMFACRY6VUPD9UN5.temp
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFdb1d.TMP
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFdb1d.TMP
- C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_jle2v2is.v5a.ps1
- C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_qgrrneff.55z.psm1
- Local\Shell.CMruPidlList
- Local\SessionImmersiveColorMutex
- Global\SyncRootManager
- Local\Mutexf01b4d95cf55d32a.automaticDestinations-ms
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache.
- 96ad1146eb96877eab59…87dcf7Never scannednever seen before
- e23040951e464b53b84b…09bc25Never scannednever seen before
- 4fc7c3215f724584ae45…c7f785Never scannednever seen before
- e2ba9e0ca8b0c3cb1099…90d185Never scannednever seen before
- 7ac4e94daae432194e83…bf46a5Never scannednever seen before
- 4520b106d2d0540dc4bb…d89697Never scannednever seen before
- 9b3cb225e50034475a21…2f3365Never scannednever seen before
- 11405ec55ab38b289f5e…892626Never 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 / 75engines flagged
- 1sources 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 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: BeSightLauncher.ps1 — a8ad7bc4ac83b5b01d6b77fdcc4e11695fe0b9918ff4d38a2656ba141953f33c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\Desktop\BeSightLauncher.ps1"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Windows PowerShell.lnk — C:\Users\<USER>\Desktop\%AppData%\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: UNQRIMFACRY6VUPD9UN5.temp — C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\UNQRIMFACRY6VUPD9UN5.temp
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.EXEMITRE T1003 (OS Credential Dumping) mapped by at least one sandbox run.
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- BeSightLauncher.ps1
- Format
- Powershell
- Code signing
- No verified publisher
- Size
- 21.9 KB
- Last analyzed
- Sep 27, 2026, 12:37 PM UTC
a8ad7bc4ac83b5b01d6b77fdcc4e11695fe0b9918ff4d38a2656ba141953f33cSafety & 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 BeSightLauncher.ps1 safe, or is it malware?
What is BeSightLauncher.ps1?
How many antivirus engines detected BeSightLauncher.ps1?
What should I do if I already ran BeSightLauncher.ps1?
How do I remove BeSightLauncher.ps1?
What is the SHA-256 hash of BeSightLauncher.ps1?
How up to date is this analysis of BeSightLauncher.ps1?
Community
Member reviews and reports for this exact file hash.