GridinSoft Threat Intelligence

FabFilter Pro-C 2.dll file report

Under review File reputation report
MD5 a91cb2bcb5ef8f0b83873cbc773f222e
Latest seen 2024-05-12 23:00:37 (2 years ago)
First seen 2024-05-06 23:00:33 (2 years ago)
Size 2 MB
Publisher FabFilter
Product FabFilter Pro-C

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-05-06 23:00:33 (2 years ago); latest analysis 2024-05-12 23:00:37 (2 years ago).

Publisher context

Company metadata: FabFilter. Product metadata: FabFilter Pro-C.

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.

FabFilter Pro-C 2.dll is a Windows file recorded in the ThreatInfo database. It is associated with FabFilter Pro-C. The reported company name is FabFilter. The current detection status is Undefined, based on the latest analysis from 2024-05-12 23:00:37 (2 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: FabFilter Pro-C
Company Name: FabFilter
MD5: a91cb2bcb5ef8f0b83873cbc773f222e
Size: 2 MB
First Published: 2024-05-06 23:00:33 (2 years ago)
Latest Published: 2024-05-12 23:00:37 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-05-12 23:00:37 (2 years ago)
%commondir%

ThreatInfo has observed FabFilter Pro-C 2.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 10 100.0%

The most common operating system signal for FabFilter Pro-C 2.dll is Windows 10 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.

FabFilter Pro-C 2.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x0011c7e8
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 2795008

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

.text 1495552 bytes · 53.5% of section data
MD5 0e196e2507828b3316c5cfa5316a9a53
.rdata 407552 bytes · 14.6% of section data
MD5 547615a9be8e9ebf60c6b273d1302b6a
.data 62976 bytes · 2.3% of section data
MD5 0995b111d9b6057388904933825698c9
.pdata 70144 bytes · 2.5% of section data
MD5 16c7d2e0a8660fc67b3c0715ecd9bbca
_RDATA 91136 bytes · 3.3% of section data
Uncommon name
MD5 125546ff3bb7594b7fa3be239856ff53
.rsrc 650752 bytes · 23.3% of section data
MD5 a31b78b7e7ab5c710297edaf6ad0968c
.reloc 16896 bytes · 0.6% of section data
MD5 e5e05bc89ca30302296031104b0d9df6

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