GridinSoft Threat Intelligence

vsfilter.dll file report

Under review File reputation report
MD5 b02f3586906305fb4e401f2bef18e0cb
Latest seen 2022-08-25 23:14:32 (3 years ago)
First seen 2022-08-25 23:14:32 (3 years ago)
Size 1 MB
Publisher MPC-HC Team
Product VSFilter

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-08-25 23:14:32 (3 years ago); latest analysis 2022-08-25 23:14:32 (3 years ago).

Publisher context

Company metadata: MPC-HC Team. Product metadata: VSFilter.

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.

vsfilter.dll is a Windows file recorded in the ThreatInfo database. It is associated with VSFilter. The reported company name is MPC-HC Team. The current detection status is Undefined, based on the latest analysis from 2022-08-25 23:14:32 (3 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: VSFilter
Company Name: MPC-HC Team
MD5: b02f3586906305fb4e401f2bef18e0cb
Size: 1 MB
First Published: 2022-08-25 23:14:32 (3 years ago)
Latest Published: 2022-08-25 23:14:32 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-25 23:14:32 (3 years ago)
%programfiles%\software\note5\note5_5.1.4.36469\main

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

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

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x000d6071
Image base 0x10000000

PE Sections:

Sections 8
Raw data 1622528

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

.text 1203200 bytes · 74.2% of section data
MD5 632d426a5c6f5a8ea7c3fd219fbc43da
.rdata 282112 bytes · 17.4% of section data
MD5 30281527a5898eeb692f112b052e77a2
.data 33280 bytes · 2.1% of section data
MD5 7e7c69394e2c865ab8232c377d615dc4
.gfids 10752 bytes · 0.7% of section data
Uncommon name
MD5 188788d81948acf2e38800c003a29c39
.giats 512 bytes · 0.0% of section data
Uncommon name
MD5 65ac3d20ef05e8669cd4fde3e1b68731
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 20992 bytes · 1.3% of section data
MD5 e175d89663339977beb465259faba68b
.reloc 71168 bytes · 4.4% of section data
MD5 44854dd9ba441f0b42a6ad97060120f9

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 b02f3586906305fb4e401f2bef18e0cb.
  • 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.