GridinSoft Threat Intelligence

ffmpegsumo.dll file report

Under review File reputation report
MD5 6c77d076fb1633b02170ecf1b4c4cb11
Latest seen 2024-01-03 23:31:54 (2 years ago)
First seen 2024-01-03 23:31:54 (2 years ago)
Size 1 MB
Product Orbitum
Signed by Bergarius Limited

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-01-03 23:31:54 (2 years ago); latest analysis 2024-01-03 23:31:54 (2 years ago).

Publisher context

Company metadata: The Orbitum Authors. Product metadata: Orbitum.

Digital signature

Signed by Bergarius Limited. 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.

ffmpegsumo.dll is a Windows file recorded in the ThreatInfo database. It is associated with Orbitum. The reported company name is The Orbitum Authors. The current detection status is Undefined, based on the latest analysis from 2024-01-03 23:31:54 (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: Orbitum
Company Name: The Orbitum Authors
MD5: 6c77d076fb1633b02170ecf1b4c4cb11
Size: 1 MB
First Published: 2024-01-03 23:31:54 (2 years ago)
Latest Published: 2024-01-03 23:31:54 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-03 23:31:54 (2 years ago)
Signed By: Bergarius Limited
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.

%localappdata%\orbitum\application

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.

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 0x0014fb48
Image base 0x10000000

PE Sections:

Sections 7
Raw data 1904128

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

.text 1456640 bytes · 76.5% of section data
MD5 8c51eea7e5a6bc23429a2d2b32f017e1
.rdata 387072 bytes · 20.3% of section data
MD5 314f884d300e37d8709af82feb629204
.data 10752 bytes · 0.6% of section data
MD5 8cf3b2622ac5be82bf885137669bac4d
.rodata 4096 bytes · 0.2% of section data
MD5 1acec14dd55d7655a1a89caa13d853fd
_RDATA 2560 bytes · 0.1% of section data
Uncommon name
MD5 4ff3a55e87ee8fab107480d46511ddcc
.rsrc 2048 bytes · 0.1% of section data
MD5 bd3f5d9d04f1446e31b9eb8c885a14bc
.reloc 40960 bytes · 2.2% of section data
MD5 dae7e61230577f16b93c6affbda54551

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 6c77d076fb1633b02170ecf1b4c4cb11.
  • 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.