GridinSoft Threat Intelligence
setup.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2026-02-02 23:01:02 (3 months ago); latest analysis 2026-02-06 23:01:50 (3 months ago).
Company metadata: Wavesor Software. Product metadata: WaveBrowser Installer.
Signed by Eightpoint Technologies Ltd. SEZC. The signature is reported as valid, but signed files can still be bundled or abused.
ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.
Recommended action
What to do next
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
setup.exe is a Windows file recorded in the ThreatInfo database. It is associated with WaveBrowser Installer. The reported company name is Wavesor Software. The current detection status is Undefined, based on the latest analysis from 2026-02-06 23:01:50 (3 months ago).
ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.
File Details
| Product Name: | WaveBrowser Installer |
| Company Name: | Wavesor Software |
| MD5: | 72e5e8fb45be5cf57ec64a6a5490a7bd |
| Size: | 5 MB |
| First Published: | 2026-02-02 23:01:02 (3 months ago) |
| Latest Published: | 2026-02-06 23:01:50 (3 months ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2026-02-06 23:01:50 (3 months ago) |
Overview
| Signed By: | Eightpoint Technologies Ltd. SEZC |
| Status: | Valid |
The signature on setup.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %profile%\wavesor software\wavebrowser\1.5.24.12 |
ThreatInfo has observed setup.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
Geographic signal
Observed country distribution
ThreatInfo has seen setup.exe across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for setup.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
setup.exe is identified as pe for 64-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
b44a7384a9dc9ba56214cc774cabb718
7ceb60dd963e7d82522a004a410e7fd5
e85c14e6de84d1aece77401480ac28b1
0ba0b5252c0027d83626a905b7b6e280
bf619eac0cdf3f68d496ea9344137e8b
956c856939278d142083bef02b9de040
57853f7a2d2f1f99e62e10d99f05a314
60d3ea61d541c9be2e845d2787fb9574
05e9eab8428a551a281ab278073669fa
616e52f37c5933dd7fd22ca8ec2c7bd8
9b94ebe66a8ccb8e136d5dce2f4ed1a5
92a9a36fc9dfc4422fe2177023f931ee
e4b02dbc6753b6a9bec6109380e98528
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
Report conclusion
This file is still under review
ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.