GridinSoft Threat Intelligence

ffmpeg.dll file report

Under review File reputation report
MD5 cbc18a817926b58087aca53fe9c4021f
Latest seen 2025-02-04 23:01:28 (a year ago)
First seen 2025-02-04 23:01:28 (a year ago)
Size 2 MB
Signed by WeMod LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-02-04 23:01:28 (a year ago); latest analysis 2025-02-04 23:01:28 (a year ago).

Digital signature

Signed by WeMod LLC. 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.

ffmpeg.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-02-04 23:01:28 (a year 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.

MD5: cbc18a817926b58087aca53fe9c4021f
Size: 2 MB
First Published: 2025-02-04 23:01:28 (a year ago)
Latest Published: 2025-02-04 23:01:28 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-02-04 23:01:28 (a year ago)
Signed By: WeMod LLC
Status: Valid

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

%localappdata%\squirreltemp\tempb\lib

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

ffmpeg.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x00097bb0
Image base 0x10000000

PE Sections:

Sections 7
Raw data 2524160

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

.text 2045952 bytes · 81.1% of section data
MD5 21b180cb9eea8a1c5ec0f53e5dbdc03d
.rdata 414208 bytes · 16.4% of section data
MD5 5a89a7e4ab6dee8e6461012f64b25e47
.data 7168 bytes · 0.3% of section data
MD5 ffc4ca575eaffef208f606b44b86cab2
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 b27c0d2eab8cb54dc7e3de122471913b
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.voltbl 512 bytes · 0.0% of section data
Uncommon name
MD5 2d62e8c1295f516000c19e0da706d9a4
.reloc 55296 bytes · 2.2% of section data
MD5 eb35a80a0f37617c43d435416092ebe2

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