GridinSoft Threat Intelligence

e1k63x64.sys file report

Clean record File reputation report
MD5 bf0b2e0a0f24a015e9530b2f85dbc323
Latest seen 2021-01-12 04:01:03 (5 years ago)
First seen 2017-08-14 14:09:31 (8 years ago)
Size 458 KB
Publisher Intel Corporation
Product Intel(R) Gigabit Adapter
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:31 (8 years ago); latest analysis 2021-01-12 04:01:03 (5 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) Gigabit Adapter.

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

e1k63x64.sys is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Gigabit Adapter. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-12 04:01:03 (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(R) Gigabit Adapter
Company Name: Intel Corporation
MD5: bf0b2e0a0f24a015e9530b2f85dbc323
Size: 458 KB
First Published: 2017-08-14 14:09:31 (8 years ago)
Latest Published: 2021-01-12 04:01:03 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 04:01:03 (5 years ago)

Overview

Signed By: Intel Corporation
Status: Valid

The signature on e1k63x64.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\pro1000\winx64\ndis63
%programfiles%\drivertoolkit\download\c5c2e9d7c5c9d0c9e3e1fb218cd181ae\pro1000\winx64
%programfiles%\drivertoolkit\download\589eb3c165aa73ce793263562edf92f3\pro1000\winx64
%appdata%\easeware\drivernavigator\drivers\5jm5oayw.a2d\19_5_cd\pro1000\winx64

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

Top country Hong Kong
Share 66.7%
Low High activity

The strongest geographic signal for this file is Hong Kong with 66.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 77.8%
Windows 7 22.2%

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

e1k63x64.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 0x000131ec
Image base 0x0000000140000000

PE Sections:

Sections 7
Raw data 460288

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

.text 330240 bytes · 71.7% of section data
MD5 2620956f011d6f3fb204f6a3dde93f03
.rdata 28672 bytes · 6.2% of section data
MD5 a2fc20dbcdbe4aea7062372ef749f265
.data 62464 bytes · 13.6% of section data
MD5 9d831f2c9982db74f67cd60d2c547623
.pdata 19456 bytes · 4.2% of section data
MD5 262a841b848711ddde235a1278ade422
INIT 3584 bytes · 0.8% of section data
Uncommon name
MD5 f1a895bc7dded7ea2b2dfb0d4bba365e
.rsrc 14336 bytes · 3.1% of section data
MD5 b75880ba8dba8a859be184f4073bf2c1
.reloc 1536 bytes · 0.3% of section data
MD5 196ae81001581f01111edd113db074bf

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