Is NeverloseLauncher.exe safe?
Fifteen community YARA matches, including command-and-control and stealer-oriented rules, outweigh one low-trust detection despite substantial contradictory scanner and sandbox evidence.
The strongest concern is 15 community YARA matches, including command-and-control and stealer-oriented signatures, plus observed T1562.001 defense impairment. However, only 1 of 75 engines detected it, every tier-1 engine was silent, and the completed sandbox produced no malicious verdict, making the assessment less conclusive than a family consensus.
89459d24b895ba9173…903f2b2eeac408Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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.
The strongest concern is 15 community YARA matches, including command-and-control and stealer-oriented signatures, plus observed T1562.001 defense impairment. However, only 1 of 75 engines detected it, every tier-1 engine was silent, and the completed sandbox produced no malicious verdict, making the assessment less conclusive than a family consensus.
Only 1 of 75 engines flagged the executable, and that detection came from low-trust Trapmine rather than a tier-1 engine. In isolation, this would strongly suggest a false positive. The counterweight is externalIntel.yaraify.ruleCount=15, with matches such as 'command_and_control' and 'grakate_stealer_nov_2021', which constitutes substantial independent static corroboration. One sandbox also recorded T1562.001, although it did not issue a malicious verdict or identify persistence. The observed network contact was fully checked against the available host cache without a hit, while all ten inspected child files remain unclassified rather than affirmatively benign. The combined evidence supports containment, but no reliable family attribution is available.
What We Detected
Trapmine was the sole detector among 75 antivirus engines, while all 17 reporting tier-1 engines returned no detection. More importantly, externalIntel.yaraify.ruleCount=15 includes the rules command_and_control and grakate_stealer_nov_2021, alongside generic Go and debugging-oriented matches. The executable is unsigned and has no established signer history.
Threat Behavior
One completed sandbox run recorded T1562.001, a technique associated with impairing defenses, but the sandbox did not produce a malicious verdict or persistence indicators. The only observed domain was included in a complete host-cache check and had no malicious or suspicious hit. Ten dropped children were inspected without a known malicious result, although every child remains unclassified, so this does not establish that they are benign.
What To Do Now
Do not run the file on a production system or grant it elevated privileges. Keep endpoint protection enabled, quarantine the sample, and obtain the launcher only through a verifiable official distribution channel; if it has already run, perform a full endpoint scan and review security controls for signs of tampering.
Where this verdict could be wrong4 caveats
- Only Trapmine flagged the sample among 75 engines, and all 17 reporting tier-1 engines were undetected, which strongly favors a scanner false positive.
- The completed sandbox produced no malicious verdict, no persistence indicators, and the sole observed domain had no cached malicious or suspicious reputation.
- Several YARA matches identify generic Go binaries or debugging imports, so not all 15 rules are malware-specific.
- The executable has been submitted 373 times by 329 sources, reducing the likelihood that it is an entirely novel threat.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of 75 engines detected the file
- All 17 reporting tier-1 engines were undetected
- The completed sandbox produced no malicious verdict
- The sole observed domain had no cached malicious or suspicious reputation
- No malicious dropped child or persistence indicator was identified
- 15 community YARA rules matched the sample
- YARA matches include command-and-control and stealer-oriented signatures
- Observed T1562.001 defense-impairment behavior
- Unsigned Windows executable with no signer history
- All 10 inspected dropped children remain unclassified
Quarantine the executable and avoid launching it outside an isolated analysis environment. Keep endpoint protection enabled and use a verifiable official source if this software is required.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Complete1 contacted host was cross-checked.
YARA
Complete5 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
- 9MITRE ATT&CK techniques
- 6spawned processes
- 1network contacts
- 21filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
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.
Note: Collects details about your system.
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.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
NeverloseLauncher.exe
89459d24b895ba9173d40c8c02c7c01ddd73a05a2f450a19d4903f2b2eeac408
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\NeverloseLauncher.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft\EdgeWebView\Application\134.0.3124.93\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=NeverloseLauncher.exe --webview-exe-version=1.1.3 --user-data-dir="C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --lang=en-US --mojo-named-platform-channel-pipe=728.4372.1647511832345035241 /pfhostedapp:5c1440a115982a4725f2dab07c0fa6423055bc4b
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
com.nuggie.neverlosetauriofficial
C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial
04Isolated runtime analysis - Written fileObserved
EBWebView
C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
eip-terr-na.cdp1.digicert.com.akahost.net
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- eip-terr-na.cdp1.digicert.com.akahost.net
- HKEY_CURRENT_USER\Software\Microsoft\EdgeWebView\BLBeacon\state
- HKEY_CURRENT_USER\Software\Microsoft\EdgeWebView\ThirdParty\StatusCodes
- HKEY_CURRENT_USER\Software\Microsoft\EdgeWebView\PreferenceMACs\Default\extensions.ui.developer_mode
- HKEY_CURRENT_USER\Software\Microsoft\EdgeWebView\PreferenceMACs\Default\google.services.last_signed_in_username
- HKEY_CURRENT_USER\Software\Microsoft\EdgeWebView\PreferenceMACs\Default\media.cdm.origin_data
- HKEY_CURRENT_USER\Software\Microsoft\EdgeWebView\PreferenceMACs\Default\media.storage_id_salt
- C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial
- C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView
- C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView\30889d69-ca29-493e-b6d5-1cbd39420750.tmp
- C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView\4f09c402-e211-43cd-b021-f856830d9b90.tmp
- C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView\AmountExtractionHeuristicRegexes
- C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView\Default\SharedStorage-journal
- C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView\Local State~RF4ef37c.TMP
- C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView\Local State~RF4ef774.TMP
- \Sessions\1\BaseNamedObjects\DBWinMutex
- \Sessions\1\BaseNamedObjects\Local\ChromeProcessSingletonStartup!
- \Sessions\1\BaseNamedObjects\__OMADM_NAMED_MUTEX__
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 80357761a3ec8a6fbaa4…eae1d2Never scannednever seen before
- 5d42fe1bb77e7b17e91c…40eb4aNever scannednever seen before
- 41c91a9c93d76295746a…1cc304Never scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never scannednever seen before
- 4825318b38da4905d34c…d89d94Never scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- 579708feba2a4746b7a2…1f7b91Never scannednever seen before
- 52890eeed41923780272…b790dcNever scannednever seen before
- e54e9d1652848051e07a…4c8461Never scannednever seen before
- f7b24f2eb3d5eb055052…8b5fedNever 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.
- 5rule hits recorded
- 1 / 75engines flagged
- 329sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
5 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 15 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: NeverloseLauncher.exe — 89459d24b895ba9173d40c8c02c7c01ddd73a05a2f450a19d4903f2b2eeac408
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\user\Desktop\NeverloseLauncher.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files (x86)\Microsoft\EdgeWebView\Application\134.0.3124.93\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=NeverloseLauncher.exe --webview-exe-version=1.1.3 --user-data-dir="C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --lang=en-US --mojo-named-platform-channel-pipe=728.4372.1647511832345035241 /pfhostedapp:5c1440a115982a4725f2dab07c0fa6423055bc4b
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: com.nuggie.neverlosetauriofficial — C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: EBWebView — C:\Users\user\AppData\Local\com.nuggie.neverlosetauriofficial\EBWebView
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: eip-terr-na.cdp1.digicert.com.akahost.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched 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.
- Check_OutputDebugStringA_iat
- command_and_control
- Detect_Golang_Binary
- golang_bin_JCorn_CSC846
- grakate_stealer_nov_2021
1 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
- NeverloseLauncher.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 4.4 MB
- Last analyzed
- Oct 7, 2026, 1:05 PM UTC
89459d24b895ba9173d40c8c02c7c01ddd73a05a2f450a19d4903f2b2eeac408Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is NeverloseLauncher.exe malware?
What is NeverloseLauncher.exe?
How many antivirus engines detected NeverloseLauncher.exe?
I already downloaded and ran NeverloseLauncher.exe — what should I do?
How do I remove NeverloseLauncher.exe?
What kind of malware is NeverloseLauncher.exe?
What is the SHA-256 hash of NeverloseLauncher.exe?
How up to date is this analysis of NeverloseLauncher.exe?
Community
Member reviews and reports for this exact file hash.