Is UpdaterSetup.exe safe?
Signed installer with zero engine detections and no malicious children or host contacts.
All 75 engines returned clean. The file is signed by BrowseAI LLC and shows typical installer behaviour with no malicious sandbox verdict or known-bad network activity.
950fe10a0eb1e7531e…70391992f55338Recommended 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 engines returned clean. The file is signed by BrowseAI LLC and shows typical installer behaviour with no malicious sandbox verdict or known-bad network activity.
Zero detections across 75 reporting engines, including 17 tier-1 engines, eliminates the low-trust-only false-positive pattern. Signing is verified, though the publisher lacks prior history in our records. Sandbox execution produced three MITRE techniques commonly associated with installers, yet no malicious verdict was recorded and all dropped children and no complete contacted-host reputation result was available. Medium prevalence over 99 days further supports a legitimate distribution channel.
What We Detected
75 antivirus engines scanned the 12 MB Win32 executable; none flagged it malicious. The binary is signed by BrowseAI LLC with a valid certificate dated May 2026. Sandbox analysis recorded process-injection, data-destruction and defence-evasion techniques, but these mapped to expected installer behaviour and produced no malicious verdict.
Threat Behavior
The sample wrote ten temporary files under an Edge WebView cache folder and contacted six IP addresses, none of which appear in our malicious-host cache. No persistence mechanisms or registry modifications were observed. All ten child files returned unknown verdicts with zero malicious detections.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If the file was obtained from the official BrowseAI distribution channel, it can be executed; otherwise treat any unexpected installer with standard caution.
Where this verdict could be wrong2 caveats
- signerStats.found=false — no historical samples for 'BrowseAI LLC' to establish reputation baseline.
- triggeredHeuristics: MalwareTips.Synth.ProcessInjection (high) and MalwareTips.Synth.DirectIpC2 (medium) — static mapping to T1055 and direct-IP traffic without domain names.
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 from 75 engines including 17 tier-1 vendors
- Verified digital signature present
- No malicious children or known-bad hosts contacted
- Medium prevalence across 99 sources over 99 days
- No prior samples from signer 'BrowseAI LLC' in our database
- Direct-IP network traffic without domain names recorded
The file shows strong clean signals; it can be considered safe when obtained from a trusted source.
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
Partial4 of 10 contacted hosts were cross-checked; coverage is incomplete.
YARA
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
- 17MITRE ATT&CK techniques
- 5spawned processes
- 12network contacts
- 31filesystem & mutex artifacts
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
UpdaterSetup.exe
950fe10a0eb1e7531e2814500b83bc1767dcb08e5e67d7d8c370391992f55338
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=file.exe --webview-exe-version=143.0.7518.0 --user-data-dir="C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=0 --enable-features=MojoIpcz --mojo-named-platform-channel-pipe=5484.5196.8125993391324254060
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
throttle_store.dat
C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Crashpad\throttle_store.dat
04Isolated runtime analysis - Written fileObserved
settings.dat
C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Crashpad\settings.dat
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.20.31.107
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
34.8.74.205
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.
- 104.20.31.107
- 34.8.74.205
- 74.125.201.93
- 172.66.160.227
- 150.171.28.11
- 162.159.36.2
- https://browser.ace.ai/analytics
- https://update.ace.ai/ace/service/update2/json/1bbcc4da-6f26-11f1-aed5-46fe01f82bec@1bbcc4da-6f26-11f1-9bbb-3c819ea922a0@softonic_cnet@
- https://update.ace.ai/ace/service/update2/json/1bbcc4da-6f26-11f1-aed5-46fe01f82bec@1bbcc4da-6f26-11f1-9bbb-3c819ea922a0@softonic_cnet@?cup2key=1:dlmeXZ-UsDvrFrAVxj-RhA5u3tYTuZ0xctLGVR_Tebw&cup2hreq=cb6f5c5ec40f848d111c38e4e1ff9e5c88b5ccac90183d6dd4982e3f2f35e3a9
- https://dl.google.com/update2/installers/icons/%7B908aaf3d-6daa-4f36-a9b0-538d90bec8c1%7D.bmp?lang=en-US
- https://media.ace.ai/media/versions/ace/mini_installer___ACE-update-148-0-7781-0___x64___20260622073732.crx3
- https://browser.ace.ai/attr_hit
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Crashpad\throttle_store.dat
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Crashpad\settings.dat
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\BrowserMetrics\BrowserMetrics-6A3ABD85-1780.pma
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\lockfile
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Variations
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\BrowserMetrics-spare.pma
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Default\Code Cache\wasm\index-dir\the-real-index
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Default\Code Cache\js\index-dir\the-real-index
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Default\Site Characteristics Database\000001.dbtmp
- C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Default\Sync Data\LevelDB\000001.dbtmp
- Local\ChromeProcessSingletonStartup!
- __OMADM_NAMED_MUTEX__
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
- 872727f89f2263f46d57…6e700dNever scannednever seen before
- 8f35d048504185d9e1ef…7aff15Never scannednever seen before
- 4cdf5eb12966a561f2ee…2e8952Never scannednever seen before
- 8e57cffd04fb5f4add47…5be923Never scannednever seen before
- bfe3cc4b56da9d434252…f58c5fNever scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- b1e963d702392fb72247…c0cdecNever scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never scannednever seen before
- 6ab9a0f330c611cefdd6…1fb29aNever 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
- 99sources 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
The file has a valid code signature from BrowseAI LLC.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: UpdaterSetup.exe — 950fe10a0eb1e7531e2814500b83bc1767dcb08e5e67d7d8c370391992f55338
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=file.exe --webview-exe-version=143.0.7518.0 --user-data-dir="C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=0 --enable-features=MojoIpcz --mojo-named-platform-channel-pipe=5484.5196.8125993391324254060
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: throttle_store.dat — C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Crashpad\throttle_store.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: settings.dat — C:\Users\<USER>\AppData\Local\Temp\AceInstallerWizardData\EBWebView\Crashpad\settings.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.20.31.107 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 34.8.74.205 — 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.
Evidence"C:\Users\<USER>\Desktop\file.exe"The 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.
Evidence104.20.31.107 · 34.8.74.205 · 74.125.201.93
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
- UpdaterSetup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: BrowseAI LLC
- Size
- 11.6 MB
- Last analyzed
- Sep 4, 2026, 2:57 PM UTC
950fe10a0eb1e7531e2814500b83bc1767dcb08e5e67d7d8c370391992f55338Safety & 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 UpdaterSetup.exe safe?
What is UpdaterSetup.exe?
How many antivirus engines detected UpdaterSetup.exe?
Is UpdaterSetup.exe digitally signed?
What is the SHA-256 hash of UpdaterSetup.exe?
Is it safe to run UpdaterSetup.exe?
How up to date is this analysis of UpdaterSetup.exe?
Community
Member reviews and reports for this exact file hash.