GridinSoft Threat Intelligence
setup.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2025-01-10 23:02:01 (a year ago); latest analysis 2025-09-13 23:01:45 (8 months ago).
Company metadata: OneStart.ai. Product metadata: OneStart Installer.
Signed by Apollo Technologies Inc.. 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 OneStart Installer. The reported company name is OneStart.ai. The current detection status is Undefined, based on the latest analysis from 2025-09-13 23:01:45 (8 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: | OneStart Installer |
| Company Name: | OneStart.ai |
| MD5: | 235fdb3b59ee9dc1069f9c05f6734e16 |
| Size: | 4 MB |
| First Published: | 2025-01-10 23:02:01 (a year ago) |
| Latest Published: | 2025-09-13 23:01:45 (8 months ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2025-09-13 23:01:45 (8 months ago) |
Overview
| Signed By: | Apollo Technologies Inc. |
| 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:
| %localappdata%\onestart.ai\onestart\application\130.0.6723.134 |
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 2 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 77.8% 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.
4ec55f747bc3df1cc0872bc0d531d339
2fa8f1119be1da9169459b128aa53def
9024b143f0357113884fe8ec361ed09f
db4d105f580ab164587427165e4d27c9
3636063cf25741b30fab643f7e6fd5fd
daf679929e82d180bceb8491233f5884
956c856939278d142083bef02b9de040
ce82e45a4f8f304208b2933cf451ea55
60d3ea61d541c9be2e845d2787fb9574
05e9eab8428a551a281ab278073669fa
e0b558cc265c375042ab97fb8fcb6ade
80ebfc3dd1f795cc42563bb87a839a2a
8388e189d1c85c33cc85eae5f2dfc770
b7a293e51fe4c859e7818a2b6d449c8e
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.