GridinSoft Threat Intelligence
libblendbench_plugin.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2020-10-13 12:18:20 (5 years ago); latest analysis 2025-10-02 23:00:32 (7 months ago).
Company metadata: VideoLAN. Product metadata: VLC media player.
Signed by VideoLAN. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
libblendbench_plugin.dll is a Windows file recorded in the ThreatInfo database. It is associated with VLC media player. The reported company name is VideoLAN. The current detection status is Undefined, based on the latest analysis from 2025-10-02 23:00:32 (7 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.
File Details
| Product Name: | VLC media player |
| Company Name: | VideoLAN |
| MD5: | 00131d3ddded743fb8c300c6653215fe |
| Size: | 35 KB |
| First Published: | 2020-10-13 12:18:20 (5 years ago) |
| Latest Published: | 2025-10-02 23:00:32 (7 months ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2025-10-02 23:00:32 (7 months ago) |
Overview
| Signed By: | VideoLAN |
| Status: | Valid |
The signature on libblendbench_plugin.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.
Common Places:
| %commonappdata%\ubar\ubar\modules\vlc\plugins |
| %programfiles%\kernel video repair\plugins |
ThreatInfo has observed libblendbench_plugin.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.
Geographic signal
Observed country distribution
ThreatInfo has seen libblendbench_plugin.dll across 7 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Bulgaria with 22.2% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for libblendbench_plugin.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.
Analysis
libblendbench_plugin.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
93f276b78cf2d29057891d1301d09c79
0c7fb84004f07459b0672568826669ca
8d663d89f7fbfe27261bbe388ee3e5f0
0007c891c888488fdb5bb817d7fa7593
d41d8cd98f00b204e9800998ecf8427e
7546e342e42e8a1eeb7b65b63449dafa
3347ee892c049bc5c74ca723df99988c
761fdde05dde8bd22819a397edc2e9ce
6ddae7401c22530790241062fd44382f
a5d87f5e1fbc18a4df85b60e3e8a8a48
399682595f4215c716424910feb70953
8c25547ee68ddf5c114dfff57631f883
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.