setup.exe file report

MD5 e9065784f6fd2a3f162fd84445d8cefc
Latest seen 2021-12-29 21:22:43 (4 years ago)
First seen 2020-08-24 16:56:36 (5 years ago)
Size 116 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-08-24 16:56:36 (5 years ago); latest analysis 2021-12-29 21:22:43 (4 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft Office Small Business Setup.

Digital signature

Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.

Observed locations

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

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

setup.exe is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Office Small Business Setup. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-12-29 21:22:43 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Microsoft Office Small Business Setup
Company Name: Microsoft Corporation
MD5: e9065784f6fd2a3f162fd84445d8cefc
Size: 116 KB
First Published: 2020-08-24 16:56:36 (5 years ago)
Latest Published: 2021-12-29 21:22:43 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-12-29 21:22:43 (4 years ago)
Signed By: Microsoft Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager
%programfiles%\microsoft small business\business contact manager

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.

85.3%
5.9%
5.9%
2.9%

The strongest geographic signal for this file is United States with 85.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows XP 85.3%
Windows 7 11.8%
Windows Vista 2.9%

The most common operating system signal for setup.exe is Windows XP with 85.3% 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.

setup.exe is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x00007fbc

PE Sections:

Name Size of data MD5
.text 81408 edcefe71a6441e74f3561e6c172c97ad
.data 4608 00a7e5c9123c38468c6e07bab7834fbf
.rsrc 23040 63d7853eadeaf469d72dd0c9b312da43

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.

More information: