GridinSoft Threat Intelligence

instfsps.exe file report

Clean record File reputation report
MD5 84bffec8c9df6ab00dc40f24d428081a
Latest seen 2021-01-11 00:13:27 (5 years ago)
First seen 2021-01-11 00:13:27 (5 years ago)
Size 58 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-01-11 00:13:27 (5 years ago); latest analysis 2021-01-11 00:13:27 (5 years ago).

Publisher context

Company metadata: F-Secure Corporation. Product metadata: F-Secure Protocol Scanner LSP Installer.

Digital signature

Signed by F-Secure 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.

instfsps.exe is a Windows file recorded in the ThreatInfo database. It is associated with F-Secure Protocol Scanner LSP Installer. The reported company name is F-Secure Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-11 00:13:27 (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.

Product Name: F-Secure Protocol Scanner LSP Installer
Company Name: F-Secure Corporation
MD5: 84bffec8c9df6ab00dc40f24d428081a
Size: 58 KB
First Published: 2021-01-11 00:13:27 (5 years ago)
Latest Published: 2021-01-11 00:13:27 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-11 00:13:27 (5 years ago)
Signed By: F-Secure 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%\pc veilig

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

instfsps.exe is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x0000296c
Image base 0x01000000

PE Sections:

Sections 3
Raw data 50176

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

.text 44032 bytes · 87.8% of section data
MD5 3793fcafd6d8241f3468c9d13f75be58
.data 4096 bytes · 8.2% of section data
MD5 f3326becf5ab47e54f9ea9fa022a5070
.rsrc 2048 bytes · 4.1% of section data
MD5 8088a71850e8a1384b663e5d553fd445

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 84bffec8c9df6ab00dc40f24d428081a.
  • 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.