GridinSoft Threat Intelligence

IFM60X64.sys file report

Clean record File reputation report
MD5 35ab259cd3f49d16b705ef63c1d215e6
Latest seen 2021-01-12 04:10:20 (5 years ago)
First seen 2017-08-14 14:09:30 (8 years ago)
Size 462 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:30 (8 years ago); latest analysis 2021-01-12 04:10:20 (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

IFM60X64.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:10:20 (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: 35ab259cd3f49d16b705ef63c1d215e6
Size: 462 KB
First Published: 2017-08-14 14:09:30 (8 years ago)
Latest Published: 2021-01-12 04:10:20 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 04:10:20 (5 years ago)

Overview

Signed By: Intel Corporation
Status: Valid

The signature on IFM60X64.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 IFM60X64.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 IFM60X64.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 IFM60X64.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

IFM60X64.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 0x00066cc8
Image base 0x0000000140000000

PE Sections:

Sections 8
Raw data 464896

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

.text 421888 bytes · 90.7% of section data
MD5 71561ae4c7f96710c6b56437fb1b98a7
.rdata 14336 bytes · 3.1% of section data
MD5 0d0f0d3c83bccc1d53cfeae5972fda05
.data 8704 bytes · 1.9% of section data
MD5 829bd088efa1c5c024bda1c0f78a5dda
.pdata 6656 bytes · 1.4% of section data
MD5 a4e488ef54457167d49efd06424101fb
PAGE 2048 bytes · 0.4% of section data
Uncommon name
MD5 5bbf63cc172aa3d71ffd639cb23d5816
INIT 3584 bytes · 0.8% of section data
Uncommon name
MD5 15afc829d52638e559f8a960488b425e
.rsrc 5632 bytes · 1.2% of section data
MD5 53923fea25c753e491f183f624d7be4a
.reloc 2048 bytes · 0.4% of section data
MD5 41478b7bdf5e8c7005210c89555aa8f4

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 35ab259cd3f49d16b705ef63c1d215e6.
  • 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.