GridinSoft Threat Intelligence

FabFilter Pro-R 2.dll file report

Under review File reputation report
MD5 c61797e7f5057905b0aa1dc15756b677
Latest seen 2024-05-12 23:00:36 (2 years ago)
First seen 2024-05-06 23:00:36 (2 years ago)
Size 3 MB
Publisher FabFilter
Product FabFilter Pro-R

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

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

Publisher context

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

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

ThreatInfo has observed FabFilter Pro-R 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-R 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-R 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 0x00177ddc
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 3810816

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

.text 1890304 bytes · 49.6% of section data
MD5 7bcff6b8acd34cbc5a9ddde4edb21d9b
.rdata 487936 bytes · 12.8% of section data
MD5 8de5e174515a8a341f87ff417e36b0d1
.data 81408 bytes · 2.1% of section data
MD5 ae4edf840576a85399fbdcb76fd9b050
.pdata 85504 bytes · 2.2% of section data
MD5 301d6f074dda1c4af1802896442ae475
_RDATA 159232 bytes · 4.2% of section data
Uncommon name
MD5 18a5b82fb0ed045bcdf49ff65e45c370
.rsrc 1085440 bytes · 28.5% of section data
MD5 c9a904f053b97da8c813cd2e318fa151
.reloc 20992 bytes · 0.6% of section data
MD5 45334b98f8d147940f0b5876333b3803

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