GridinSoft Threat Intelligence

IFD63X64.sys file report

Clean record File reputation report
MD5 b7962cc617a4a23aba505177cc433d39
Latest seen 2021-01-12 03:57:26 (5 years ago)
First seen 2017-08-14 14:09:34 (8 years ago)
Size 491 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:34 (8 years ago); latest analysis 2021-01-12 03:57:26 (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

IFD63X64.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 03:57:26 (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: b7962cc617a4a23aba505177cc433d39
Size: 491 KB
First Published: 2017-08-14 14:09:34 (8 years ago)
Latest Published: 2021-01-12 03:57:26 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 03:57:26 (5 years ago)

Overview

Signed By: Intel Corporation
Status: Valid

The signature on IFD63X64.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\prosetdx\winx64

ThreatInfo has observed IFD63X64.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 IFD63X64.sys across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Hong Kong
Share 85.7%
Low High activity

The strongest geographic signal for this file is Hong Kong with 85.7% 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 85.7%
Windows 7 14.3%

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

IFD63X64.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 0x00021560
Image base 0x0000000140000000

PE Sections:

Sections 7
Raw data 494592

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

.text 450560 bytes · 91.1% of section data
MD5 5290d68269437477ef002bf187a0bda8
.rdata 16896 bytes · 3.4% of section data
MD5 1013af2c181716dec4265bbe2e577ffd
.data 8704 bytes · 1.8% of section data
MD5 af0cb62c783c4a5d537edfa7ff610666
.pdata 8704 bytes · 1.8% of section data
MD5 70218d8284fc1f0450cdd87ab0eabcb2
INIT 2048 bytes · 0.4% of section data
Uncommon name
MD5 12f55fb560df814356047fecabe2dda1
.rsrc 5632 bytes · 1.1% of section data
MD5 3e2bbe5d029e820242808edd1b558c4b
.reloc 2048 bytes · 0.4% of section data
MD5 5ad65529c3b42881374db453e013e734

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 b7962cc617a4a23aba505177cc433d39.
  • 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.