GridinSoft Threat Intelligence

spyhunter4.exe file report

Clean record File reputation report
MD5 1f0c66c4dc205d8d7c37911ac4b8bf02
Latest seen 2024-04-25 23:01:07 (2 years ago)
First seen 2024-04-21 23:02:11 (2 years ago)
Size 687 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-04-21 23:02:11 (2 years ago); latest analysis 2024-04-25 23:01:07 (2 years ago).

Publisher context

Company metadata: Enigma Software Group USA, LLC.. Product metadata: SpyHunter Downloader.

Digital signature

Signed by Enigma Software Group USA, LLC. 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.

spyhunter4.exe is a Windows file recorded in the ThreatInfo database. It is associated with SpyHunter Downloader. The reported company name is Enigma Software Group USA, LLC.. The current detection status is Clean, based on the latest analysis from 2024-04-25 23:01:07 (2 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: SpyHunter Downloader
Company Name: Enigma Software Group USA, LLC.
MD5: 1f0c66c4dc205d8d7c37911ac4b8bf02
Size: 687 KB
First Published: 2024-04-21 23:02:11 (2 years ago)
Latest Published: 2024-04-25 23:01:07 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-04-25 23:01:07 (2 years ago)
Signed By: Enigma Software Group USA, LLC
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.

%localappdata%\setup wizard

ThreatInfo has observed spyhunter4.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.

Windows 10 100.0%

The most common operating system signal for spyhunter4.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.

spyhunter4.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 0x0002abd9
Image base 0x00400000

PE Sections:

Sections 5
Raw data 696832

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

.text 281088 bytes · 40.3% of section data
MD5 0125964f3d6f954adb8de1f51410e8b5
.rdata 55296 bytes · 7.9% of section data
MD5 99074bf7fc4441f7a1d25bde6c98d36d
.data 7168 bytes · 1.0% of section data
MD5 75237e5f932cb1ae895b7c8189fabad4
.rsrc 335872 bytes · 48.2% of section data
MD5 7700db413d072774341fdce62e3520e6
.reloc 17408 bytes · 2.5% of section data
MD5 35d84ae7a7c24d640b6040842632a046

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 1f0c66c4dc205d8d7c37911ac4b8bf02.
  • 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.