GridinSoft Threat Intelligence

setup.exe file report

Clean record File reputation report
MD5 2c430c0a60e3b669d37b25b09f4be8ef
Latest seen 2021-01-11 12:48:35 (5 years ago)
First seen 2017-06-14 03:02:01 (8 years ago)
Size 209 KB
Publisher Microsoft Corporation
Product Microsoft Setup Bootstrapper
Signed by Microsoft Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-06-14 03:02:01 (8 years ago); latest analysis 2021-01-11 12:48:35 (5 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft Setup Bootstrapper.

Digital signature

Signed by Microsoft Corporation. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

File context

setup.exe is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Setup Bootstrapper. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-11 12:48:35 (5 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.

File Details

Product Name: Microsoft Setup Bootstrapper
Company Name: Microsoft Corporation
MD5: 2c430c0a60e3b669d37b25b09f4be8ef
Size: 209 KB
First Published: 2017-06-14 03:02:01 (8 years ago)
Latest Published: 2021-01-11 12:48:35 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-11 12:48:35 (5 years ago)

Overview

Signed By: Microsoft Corporation
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%
%sysdrive%\programdata
%sysdrive%\msocache\all users
%sysdrive%
%sysdrive%\المواقع\تعريفات وبرامج\[ar4up.com]_offi.ce2013arabic_freex64
%sysdrive%\برامج\برامج\برامج\اوفيس2013
%sysdrive%\barameg\nakash\office

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.

File Names:

2 observed names
Tempofsetup.exe setup.exe

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Geographic signal

Observed country distribution

ThreatInfo has seen setup.exe across 10 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Greece
Share 38.7%
Low High activity

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

OS Version:

Windows 8.1 48.4%
Windows 7 35.5%
Windows 10 16.1%

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

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x000016bc
Image base 0x0000000140000000

PE Sections:

Sections 6
Raw data 206848

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 22528 bytes · 10.9% of section data
MD5 7c6521d5def3b3f8351506c9f7d8d5ef
.rdata 10240 bytes · 5.0% of section data
MD5 aeccdeb17633ad90fa24699836e05178
.data 4096 bytes · 2.0% of section data
MD5 38400ca9d90ca312873108a7bb2f9c61
.pdata 1536 bytes · 0.7% of section data
MD5 4596bfac6bb23131fa573dc24b8e893f
.rsrc 167936 bytes · 81.2% of section data
MD5 38fdc4b0ec42a66c61d142e548e8cebf
.reloc 512 bytes · 0.2% of section data
MD5 07e0e30241d7c514ff18a9b5929d9e62

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 2c430c0a60e3b669d37b25b09f4be8ef.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.