GridinSoft Threat Intelligence

NicInstD.dll file report

Clean record File reputation report
MD5 4c211bb9ec71bab8b21c21ec5d972f8d
Latest seen 2021-01-12 04:14:01 (5 years ago)
First seen 2021-01-12 04:04:24 (5 years ago)
Size 68 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 2021-01-12 04:04:24 (5 years ago); latest analysis 2021-01-12 04:14:01 (5 years ago).

Publisher context

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

Digital signature

Signed by Intel Corporation. ThreatInfo marks this publisher as trusted for this record.

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.

NicInstD.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:14:01 (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: 4c211bb9ec71bab8b21c21ec5d972f8d
Size: 68 KB
First Published: 2021-01-12 04:04:24 (5 years ago)
Latest Published: 2021-01-12 04:14:01 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 04:14:01 (5 years ago)
Signed By: Intel Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%appdata%\easeware\drivernavigator\drivers\5jm5oayw.a2d\19_5_cd\pro1000\win32

ThreatInfo has observed NicInstD.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 7 100.0%

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

NicInstD.dll is identified as pe for 32-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 32-bit
Subsystem Windows CUI
Entry point 0x00006fa1
Image base 0x02000000

PE Sections:

Sections 4
Raw data 61440

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

.text 46080 bytes · 75.0% of section data
MD5 8eac62f442ed3743652049a6ca85e13c
.data 2048 bytes · 3.3% of section data
MD5 0c7a42d75855b8e53732de7d5644c2d4
.rsrc 10240 bytes · 16.7% of section data
MD5 db40a5a5af11c45da385e071340fdc53
.reloc 3072 bytes · 5.0% of section data
MD5 5eba4ed08ff5a21dff6930d5f6df2d98

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 4c211bb9ec71bab8b21c21ec5d972f8d.
  • 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.