GridinSoft Threat Intelligence

ffmpegsumo.dll file report

Clean record File reputation report
MD5 685642623e6aaeca417301ea4ac8124b
Latest seen 2024-12-19 23:03:22 (a year ago)
First seen 2017-05-21 10:03:24 (9 years ago)
Size 1 MB
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 10:03:24 (9 years ago); latest analysis 2024-12-19 23:03:22 (a year ago).

Digital signature

Signed by Google Inc. 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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

ffmpegsumo.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2024-12-19 23:03:22 (a year ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

MD5: 685642623e6aaeca417301ea4ac8124b
Size: 1 MB
First Published: 2017-05-21 10:03:24 (9 years ago)
Latest Published: 2024-12-19 23:03:22 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2024-12-19 23:03:22 (a year ago)
Signed By: Google Inc
Status: Valid

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

%appdata%\chportu\app\chrome-bin\39.0.2171.95
%appdata%\chportu\app\chrome-bin

ThreatInfo has observed ffmpegsumo.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 61.7%
Windows 7 29.9%
Windows 8.1 7.0%
Windows 8 1.0%
Windows Vista 0.5%

The most common operating system signal for ffmpegsumo.dll is Windows 10 with 61.7% 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.

ffmpegsumo.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 0x0011cb90
Image base 0x10000000

PE Sections:

Sections 6
Raw data 1669632

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

.text 1241600 bytes · 74.4% of section data
MD5 fde53646d524e143295def05b31be108
.rdata 373760 bytes · 22.4% of section data
MD5 53c03f66d7630d1e442f4fd568484bbd
.data 11264 bytes · 0.7% of section data
MD5 04a631cc62df4c480afb3eda613ed251
.rodata 4096 bytes · 0.2% of section data
MD5 777241af54fb1c94254addfac2d9d93a
.rsrc 512 bytes · 0.0% of section data
MD5 105fe50374614bb6c4d1ce59bd24acbc
.reloc 38400 bytes · 2.3% of section data
MD5 ecaf62eb8a19207ef34ea171794d23dc

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 685642623e6aaeca417301ea4ac8124b.
  • 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.