GridinSoft Threat Intelligence

libbluray.dll file report

Under review File reputation report
MD5 87daee61c5c5f80a4fbfc2ce06b5cd3c
Latest seen 2025-07-24 23:01:12 (10 months ago)
First seen 2017-05-21 12:05:42 (9 years ago)
Size 235 KB
Signed by Hendrik Leppkes

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 12:05:42 (9 years ago); latest analysis 2025-07-24 23:01:12 (10 months ago).

Digital signature

Signed by Hendrik Leppkes. 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.

libbluray.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-07-24 23:01:12 (10 months 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: 87daee61c5c5f80a4fbfc2ce06b5cd3c
Size: 235 KB
First Published: 2017-05-21 12:05:42 (9 years ago)
Latest Published: 2025-07-24 23:01:12 (10 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-07-24 23:01:12 (10 months ago)
Signed By: Hendrik Leppkes
Status: Valid

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

%programfiles%\freecodecpack\lavfilters
%programfiles%\freecodecpack
%sysdrive%\programmi\freecodecpack

ThreatInfo has observed libbluray.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 7 47.7%
Windows 10 39.9%
Windows 8.1 7.6%
Windows XP 2.4%
Windows Vista 1.2%
Windows 8 0.9%
Windows Embedded 8.1 0.3%

The most common operating system signal for libbluray.dll is Windows 7 with 47.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.

libbluray.dll is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x0001d818
Image base 0x10000000

PE Sections:

Sections 5
Raw data 233472

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

.text 175616 bytes · 75.2% of section data
MD5 3221ea156f668e732698b51125bab9d8
.rdata 43520 bytes · 18.6% of section data
MD5 0de673a7410da03fa245b270bedc5069
.data 5120 bytes · 2.2% of section data
MD5 9bdab76ace3a0ad2db9ad5d7c81fc500
.rsrc 512 bytes · 0.2% of section data
MD5 160af15b40db62e01247e4a74b5b10b1
.reloc 8704 bytes · 3.7% of section data
MD5 40587a4911d33e8d396382ea65a09818

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 87daee61c5c5f80a4fbfc2ce06b5cd3c.
  • 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.