GridinSoft Threat Intelligence

setup.exe file report

Under review File reputation report
MD5 84e1a045715475dcc35e2aa804a4f1bb
Latest seen 2021-01-13 14:35:41 (5 years ago)
First seen 2018-07-13 10:11:55 (7 years ago)
Size 236 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2018-07-13 10:11:55 (7 years ago); latest analysis 2021-01-13 14:35:41 (5 years ago).

Publisher context

Product metadata: DriverPack Solution.

Digital signature

Signed by Kuzyakov Artur Vyacheslavovich IP. 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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

setup.exe is a Windows file recorded in the ThreatInfo database. It is associated with DriverPack Solution. The current detection status is Undefined, based on the latest analysis from 2021-01-13 14:35:41 (5 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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.

Product Name: DriverPack Solution
MD5: 84e1a045715475dcc35e2aa804a4f1bb
Size: 236 KB
First Published: 2018-07-13 10:11:55 (7 years ago)
Latest Published: 2021-01-13 14:35:41 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-13 14:35:41 (5 years ago)
Signed By: Kuzyakov Artur Vyacheslavovich IP
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.

%appdata%
%sysdrive%\gordons-pc\backup set 2018-08-26 190005\backup files 2018-08-26 190005\backup files 1.zip\c\users\gordons\appdata\roaming
%programfiles%
%profile%\dmin\application data
%profile%\dministrator\application data

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.

Uninstall.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.

Windows 7 50.0%
Windows 10 38.9%
Windows XP 6.9%
Windows Embedded 8.1 1.4%
Windows Vista 1.4%
Windows 8.1 1.4%

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

setup.exe is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x00001590
Image base 0x00400000

PE Sections:

Sections 9
Raw data 233472

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

.text 11264 bytes · 4.8% of section data
MD5 765e818b875ffe85686db9f6b9166db4
.data 512 bytes · 0.2% of section data
MD5 af1f3ea16a22b0486daa7e758006daaf
.rdata 1536 bytes · 0.7% of section data
MD5 525de3702ac8a21b62e8503b6d401bec
/4 2560 bytes · 1.1% of section data
Uncommon name
MD5 4137880a0d116352c53187b23a1ffca5
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.idata 2048 bytes · 0.9% of section data
MD5 cfec2f786b5c53a76bf1dd2f3d51cdbe
.CRT 512 bytes · 0.2% of section data
MD5 049bad4359f7e4531436d9264586a1c5
.tls 512 bytes · 0.2% of section data
MD5 ef84dcef99a8080757b858aa1dd8cef9
.rsrc 214528 bytes · 91.9% of section data
MD5 bda07e3476cb1fc7f239b68051c3c6a8

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.

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 84e1a045715475dcc35e2aa804a4f1bb.
  • 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. Use the PUP category to compare similar reports.