CheckNDISPort_df.exe file report

• » File
• File Details
• Overview
• Analysis

Analyst brief

What this report says

ThreatInfo currently records CheckNDISPort_df.exe as Clean. Treat the hash, publisher, signature, and observed locations below as the primary identity markers for comparison with the file on your system.

This page combines the detection verdict with file identity, publisher metadata, alternate names, observed paths, geography, OS signals, and PE details so the report reads as a triage record rather than a standalone download page.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-01-07 19:39:01 (5 years ago); latest analysis 2021-01-07 19:39:01 (5 years ago).

Digital signature

Signed by ZTE CORPORATION. ThreatInfo marks this publisher as trusted for this record.

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.

CheckNDISPort_df.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-01-07 19:39: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.

File Details

Overview

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

The most common operating system signal for CheckNDISPort_df.exe is Windows Server 2012 R2 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.

Analysis

CheckNDISPort_df.exe is identified as pe for 32 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

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.