v1q64x64.sys file report

MD5 926e548ce69cd2dd232e09b4364f581a
Latest seen 2021-01-12 03:50:22 (5 years ago)
First seen 2017-08-14 14:09:36 (8 years ago)
Size 128 KB
Publisher Intel Corporation
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:36 (8 years ago); latest analysis 2021-01-12 03:50:22 (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.

v1q64x64.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 03:50:22 (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: Intel(R) Gigabit Adapter
Company Name: Intel Corporation
MD5: 926e548ce69cd2dd232e09b4364f581a
Size: 128 KB
First Published: 2017-08-14 14:09:36 (8 years ago)
Latest Published: 2021-01-12 03:50:22 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 03:50:22 (5 years ago)
Signed By: Intel Corporation
Status: Valid

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

%programfiles%\drivertoolkit\download\c5c2e9d7c5c9d0c9e3e1fb218cd181ae\pro1000\winx64\ndis64
%programfiles%\drivertoolkit\download\c5c2e9d7c5c9d0c9e3e1fb218cd181ae\pro1000\winx64
%programfiles%\drivertoolkit\download\589eb3c165aa73ce793263562edf92f3\pro1000\winx64
%programfiles%\drivertoolkit\download\589eb3c165aa73ce793263562edf92f3\pro1000\winx64
%appdata%\easeware\drivernavigator\drivers\5jm5oayw.a2d\19_5_cd\pro1000\winx64

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

66.7%
11.1%
11.1%
11.1%

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.

Windows 10 77.8%
Windows 7 22.2%

The most common operating system signal for v1q64x64.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.

v1q64x64.sys is identified as pe for 64 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.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x00001e18

PE Sections:

Name Size of data MD5
.text 91136 5eca456251d8ba636785832e65cfd3f9
.rdata 7680 0f2beda84038779754329afc0b6c9a3f
.data 2048 e3531087ec08395145ff64129e0e0f14
.pdata 4608 526281722154a68342ee23920f6c5af5
INIT 3072 6108813cc6fb9775401ab60b6ba06baf
.rsrc 13312 20a23b7ad0f67fa845bfe19fba6036c4
.reloc 512 de717745b6eb79d34159c0800290e6b1

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.

More information: