GridinSoft Threat Intelligence

netfilter2_b.sys file report

Under review File reputation report
MD5 0dceca5d47f6bd851218de49211ab097
Latest seen 2022-01-29 21:46:07 (4 years ago)
First seen 2017-09-06 11:07:56 (8 years ago)
Size 66 KB
Publisher Windows (R) Win 7 DDK provider
Product Windows (R) Win 7 DDK driver
Signed by Sidorov Vitaly Viktorovich IP

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-09-06 11:07:56 (8 years ago); latest analysis 2022-01-29 21:46:07 (4 years ago).

Publisher context

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

Digital signature

Signed by Sidorov Vitaly Viktorovich IP. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

File context

netfilter2_b.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 2022-01-29 21:46:07 (4 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.

File Details

Product Name: Windows (R) Win 7 DDK driver
Company Name: Windows (R) Win 7 DDK provider
MD5: 0dceca5d47f6bd851218de49211ab097
Size: 66 KB
First Published: 2017-09-06 11:07:56 (8 years ago)
Latest Published: 2022-01-29 21:46:07 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-01-29 21:46:07 (4 years ago)

Overview

Signed By: Sidorov Vitaly Viktorovich IP
Status: Valid

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

Common Places:

%profile%\downloads\nfsdk-demo-pf\bin\driver\wfp\windows7\i386
%system%\drivers
%sysdrive%\$recycle.bin\s-1-5-21-393950803-1809432758-1887329941-1000
%system%
%profile%\downloads\nfsdk-demo-pf\bin\driver\wfp\windows7
%sysdrive%\netfilter\bin\driver\wfp\windows7
%sysdrive%\$recycle.bin
%sysdrive%\downloads\nfsdk-demo-pf\bin\driver\wfp\windows7
%sysdrive%\temp\firewall\netfilter\bin\driver\wfp\windows7
%appdata%\skype\my skype received files\nfsdk-demo-pf.zip\bin\driver\wfp\windows7

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

File Names:

4 observed names
netfilter2.sys netfilter2_7.sys $RNBDE7J.sys netfilter2_b.sys

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Geography:

51 observed countries
29.8%
11.0%
5.0%
4.7%
3.9%
3.9%
3.7%
3.1%
3.1%
2.9%
2.6%
2.1%
1.6%
1.6%
1.6%
1.3%
1.3%
1.0%
1.0%
1.0%
1.0%
0.8%
0.8%
0.8%
0.8%
0.8%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%

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

OS Version:

Windows 7 83.2%
Windows 10 16.8%

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

netfilter2_b.sys is identified as pe for 32-bit 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.

Format pe
Architecture 32-bit
Subsystem Native
Entry point 0x0001d03e
Image base 0x00010000

PE Sections:

Sections 6
Raw data 50176

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

.text 38912 bytes · 77.6% of section data
MD5 648b523942ad1abd181771d99f57e2e7
.rdata 2560 bytes · 5.1% of section data
MD5 042834c15fc8dd84a563eb4fc322e54d
.data 1024 bytes · 2.0% of section data
MD5 6a4e14aa813adf8309dea090c7fe433f
INIT 3584 bytes · 7.1% of section data
Uncommon name
MD5 6a357ac612e56daf78438f803678bf61
.rsrc 1024 bytes · 2.0% of section data
MD5 eca08abc63c7d45288f720477e89c066
.reloc 3072 bytes · 6.1% of section data
MD5 1c624770f598bb1c99a9b05a9cc5c5ec

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 0dceca5d47f6bd851218de49211ab097.
  • 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.