GridinSoft Threat Intelligence

NicInVQ.dll file report

Clean record File reputation report
MD5 991819ee50d6e47d1b88cc87e60601da
Latest seen 2021-01-12 04:09:09 (5 years ago)
First seen 2017-08-14 14:09:33 (8 years ago)
Size 77 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:33 (8 years ago); latest analysis 2021-01-12 04:09:09 (5 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) Network Interface Card CoInstaller.

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.

NicInVQ.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Network Interface Card CoInstaller. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-12 04:09:09 (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) Network Interface Card CoInstaller
Company Name: Intel Corporation
MD5: 991819ee50d6e47d1b88cc87e60601da
Size: 77 KB
First Published: 2017-08-14 14:09:33 (8 years ago)
Latest Published: 2021-01-12 04:09:09 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 04:09:09 (5 years ago)
Signed By: Intel Corporation
Status: Valid

The signature on NicInVQ.dll 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\ndis63
%programfiles%\drivergenius\temp\18_3_cd\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 NicInVQ.dll 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.

Windows 10 70.0%
Windows 7 20.0%
Windows XP 10.0%

The most common operating system signal for NicInVQ.dll is Windows 10 with 70.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.

NicInVQ.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. 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 Windows CUI
Entry point 0x00009120
Image base 0x0000000002000000

PE Sections:

Sections 5
Raw data 70656

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

.text 62976 bytes · 89.1% of section data
MD5 08a9752c6de53440bdde7eae95760d7c
.data 2560 bytes · 3.6% of section data
MD5 64243c0c61c201c426ab774fd681ffd9
.pdata 3072 bytes · 4.3% of section data
MD5 1fc3e9fe88f9ec9b9ccac5f6910f3e5b
.rsrc 1536 bytes · 2.2% of section data
MD5 6bc91a12994292262ae2a664af6794a3
.reloc 512 bytes · 0.7% of section data
MD5 152dc54d1c06879411809c38acbd57e5

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 991819ee50d6e47d1b88cc87e60601da.
  • 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.