Is Start BeSight Launcher.cmd safe?
No engine detected malware in this tiny launcher script, although an uncorroborated researcher annotation and absent runtime data warrant source verification before execution.
All 75 antivirus engines avoided a malware or suspicious label, including the reporting tier-1 products. One researcher annotation mentions a suspicious PowerShell pattern, but no engine, curated intelligence source, or saved YARA result corroborates it; because no sandbox run exists, inspect the script and verify its source before launching it.
ef01750099dae7ae04…7fdb59ce79e5ddRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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 malware or suspicious label, including the reporting tier-1 products. One researcher annotation mentions a suspicious PowerShell pattern, but no engine, curated intelligence source, or saved YARA result corroborates it; because no sandbox run exists, inspect the script and verify its source before launching it.
Static scanning produced 0 detections across 75 engines, while 16 tier-1 engines explicitly reported no detection. Curated external intelligence also returned no matching malware or YARA record. A researcher annotation cites the SUSP_PS1_Dropper_Indicators_Oct23 rule, providing a legitimate caution because batch launchers can invoke PowerShell. However, that annotation has no votes and conflicts with the saved YARAify result of zero rules, so it is insufficient by itself to establish harmful activity. No runtime observation or complete contacted-host reputation result is available, limiting certainty about execution effects. The evidence therefore favors a benign launcher while supporting manual inspection and source verification.
What We Detected
The 145-byte DOS batch file received 0 malicious and 0 suspicious results from 75 engines. Sixteen tier-1 engines reported no detection, including Microsoft, Kaspersky, ESET-NOD32, BitDefender, and Avast. MalwareBazaar, CIRCL, and the saved YARAify result provided no matching intelligence.
Threat Behavior
No completed sandbox observation is available, so the script's commands, child processes, and network effects were not observed. A researcher annotation references the rule SUSP_PS1_Dropper_Indicators_Oct23, which looks for suspicious PowerShell flag combinations in small files, but externalIntel.yaraify.ruleCount=0 and the antivirus results do not corroborate that note. No complete contacted-host reputation result is available.
What To Do Now
Open the .cmd file in a plain-text editor and verify every command, especially any PowerShell invocation, encoded argument, download command, or hidden-window flag. Run it only if it came from the expected BeSight distribution channel, and keep endpoint protection enabled.
Where this verdict could be wrong3 caveats
- communityComments[0] associates the file with SUSP_PS1_Dropper_Indicators_Oct23, which targets suspicious PowerShell command-line combinations in small files.
- The sample has only 2 submissions from 2 sources, so the absence of detections is supported by limited prevalence.
- No sandbox run or complete contacted-host reputation check is available to establish what the script does when launched.
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 engines reported malicious or suspicious results.
- tier1Malicious=0, with 16 tier-1 engines reporting no detection.
- externalIntel.malwareBazaar.hit=false.
- externalIntel.circl.hit=false and knownMalicious=null.
- externalIntel.yaraify.ruleCount=0.
- communityComments[0] references SUSP_PS1_Dropper_Indicators_Oct23.
- behaviour=null, so execution behavior was not observed.
- contactedHosts=null, so no complete host-reputation result is available.
- Only 2 submissions from 2 sources are recorded.
- The .cmd format can launch PowerShell or other system utilities.
Verify the script's origin and inspect its 145 bytes as plain text before execution, paying particular attention to PowerShell flags or download commands. 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
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 2sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
- Start BeSight Launcher.cmd
- Format
- DOS batch file
- Code signing
- Not applicable to this file type
- Size
- 145 B
- Last analyzed
- Sep 27, 2026, 12:39 PM UTC
ef01750099dae7ae04701fb28dd0d788fb7ca9bf215b12a8f97fdb59ce79e5ddSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Start BeSight Launcher.cmd safe?
What is Start BeSight Launcher.cmd?
How many antivirus engines detected Start BeSight Launcher.cmd?
What is the SHA-256 hash of Start BeSight Launcher.cmd?
Is it safe to run Start BeSight Launcher.cmd?
How up to date is this analysis of Start BeSight Launcher.cmd?
Community
Member reviews and reports for this exact file hash.