GridinSoft Threat Intelligence

IFP60X64.sys file report

Clean record File reputation report
MD5 8e9c28f603738b1e5fa31b1d48605c51
Latest seen 2021-01-12 04:14:13 (5 years ago)
First seen 2017-08-14 14:09:33 (8 years ago)
Size 159 KB
Publisher Intel(R) Corporation
Product Intel® Ethernet FCoE SAN Stack for Windows* OS
Signed by Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-08-14 14:09:33 (8 years ago); latest analysis 2021-01-12 04:14:13 (5 years ago).

Publisher context

Company metadata: Intel(R) Corporation. Product metadata: Intel® Ethernet FCoE SAN Stack for Windows* OS.

Digital signature

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

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

IFP60X64.sys is a Windows file recorded in the ThreatInfo database. It is associated with Intel® Ethernet FCoE SAN Stack for Windows* OS. The reported company name is Intel(R) Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-12 04:14:13 (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: Intel® Ethernet FCoE SAN Stack for Windows* OS
Company Name: Intel(R) Corporation
MD5: 8e9c28f603738b1e5fa31b1d48605c51
Size: 159 KB
First Published: 2017-08-14 14:09:33 (8 years ago)
Latest Published: 2021-01-12 04:14:13 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 04:14:13 (5 years ago)

Overview

Signed By: Intel Corporation
Status: Valid

The signature on IFP60X64.sys 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:

%programfiles%\drivertoolkit\download\c5c2e9d7c5c9d0c9e3e1fb218cd181ae\apps\prosetdx\winx64\drivers
%programfiles%\drivertoolkit\download\c5c2e9d7c5c9d0c9e3e1fb218cd181ae\apps\prosetdx\winx64
%appdata%\easeware\drivernavigator\drivers\5jm5oayw.a2d\19_5_cd\apps\fcoeboot\winx64
%appdata%\easeware\drivernavigator\drivers\5jm5oayw.a2d\19_5_cd\apps\prosetdx\winx64

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

Geographic signal

Observed country distribution

ThreatInfo has seen IFP60X64.sys across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Hong Kong
Share 75.0%
Low High activity

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

OS Version:

Windows 10 75.0%
Windows 7 25.0%

The most common operating system signal for IFP60X64.sys is Windows 10 with 75.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.

Analysis

IFP60X64.sys is identified as pe for 64-bit systems. The subsystem is Native. 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 Native
Entry point 0x00013fbc
Image base 0x0000000140000000

PE Sections:

Sections 8
Raw data 154624

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

.text 123904 bytes · 80.1% of section data
MD5 08fe01850c6170dbb4547e7e7a2b9e36
.rdata 5120 bytes · 3.3% of section data
MD5 70a9a7adac34b0289a268db88d294fdf
.data 10240 bytes · 6.6% of section data
MD5 9d1d81e646c06f15178197ce564d95ed
.pdata 4608 bytes · 3.0% of section data
MD5 c605e12c04108a6224d81f41b622f8b4
PAGE 2048 bytes · 1.3% of section data
Uncommon name
MD5 72cb982bf74f95a5f8a4129b787d68de
INIT 2560 bytes · 1.7% of section data
Uncommon name
MD5 a10feb0d4ce10c4d75a57faea2228104
.rsrc 5632 bytes · 3.6% of section data
MD5 a3d9d66a67631071ffa62502f23e0015
.reloc 512 bytes · 0.3% of section data
MD5 05ba4ed7d03faf51c10da09aa9176acf

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 8e9c28f603738b1e5fa31b1d48605c51.
  • 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.