160WifiProNat64.sys file report

MD5 82071b8d44bae04f7d716c2b271c52be
Latest seen 2021-01-12 21:56:14 (5 years ago)
First seen 2017-09-11 20:11:08 (8 years ago)
Size 28 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-09-11 20:11:08 (8 years ago); latest analysis 2021-01-12 21:56:14 (5 years ago).

Publisher context

Company metadata: Windows (R) Win 7 DDK provider. Product metadata: Windows (R) Win 7 DDK driver.

Digital signature

Signed by Shenzhen DriveTheLife Software Technology Co.Ltd. 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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

160WifiProNat64.sys is a Windows file recorded in the ThreatInfo database. It is associated with Windows (R) Win 7 DDK driver. The reported company name is Windows (R) Win 7 DDK provider. The current detection status is Undefined, based on the latest analysis from 2021-01-12 21:56:14 (5 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Windows (R) Win 7 DDK driver
Company Name: Windows (R) Win 7 DDK provider
MD5: 82071b8d44bae04f7d716c2b271c52be
Size: 28 KB
First Published: 2017-09-11 20:11:08 (8 years ago)
Latest Published: 2021-01-12 21:56:14 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-12 21:56:14 (5 years ago)

The signature on 160WifiProNat64.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%\telkomsel flash\160w\driver
%programfiles%\telkomsel flash\160w
%programfiles%\hspa usb modem\160w
%programfiles%\cyborg telkomsel mobile broadband\160w
%programfiles%\telkomsel flash\160w
%programfiles%\cyborg telkomsel mobile broadband\160w
%programfiles%\telkomsel flash\160w
%programfiles%\telkomsel flash\160w
%programfiles%\telkomsel flash\160w
%programfiles%\telkomsel flash\160w

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

85.1%
8.5%
4.3%
2.1%

The strongest geographic signal for this file is Indonesia with 85.1% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 7 58.3%
Windows 8.1 14.6%
Windows XP 12.5%
Windows 10 12.5%
Windows Vista 2.1%

The most common operating system signal for 160WifiProNat64.sys is Windows 7 with 58.3% 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.

160WifiProNat64.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: 0x0000000000010000
Entry Address: 0x0004945c

PE Sections:

Name Size of data MD5
.text 12800 f0b8eb79aa3cbcef0053ceee5b54b183
.rdata 1024 c114de46f0e2ca13610ad8bedc0a177c
.data 512 b721917dc85e66e932431a83c45e49a3
.pdata 512 3ccf61deac72af7e75333c1766b64bdd
INIT 3072 7ba91cdef7a5699531b1c5dbefd59fd1
.rsrc 1536 890bfa08b5941a5443d0a83a22ebfed9
.reloc 512 fe08a5b4cce8cc2d002de1028ce3ed8a

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: