libmfx32-gen.dll file report

MD5 c107aeb2b814de2d8439a4efbc447431
Latest seen 2023-10-26 23:16:34 (2 years ago)
First seen 2023-10-26 23:16:34 (2 years ago)
Size 20 MB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-10-26 23:16:34 (2 years ago); latest analysis 2023-10-26 23:16:34 (2 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel® oneAPI Video Processing Library (oneVPL).

Digital signature

Signed by Intel Corporation;Microsoft Windows Hardware Compatibility Publisher. 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.

libmfx32-gen.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel® oneAPI Video Processing Library (oneVPL). The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2023-10-26 23:16:34 (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: Intel® oneAPI Video Processing Library (oneVPL)
Company Name: Intel Corporation
MD5: c107aeb2b814de2d8439a4efbc447431
Size: 20 MB
First Published: 2023-10-26 23:16:34 (2 years ago)
Latest Published: 2023-10-26 23:16:34 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-10-26 23:16:34 (2 years ago)

The signature on libmfx32-gen.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%\innovative solutions\drivermax\agent\restore\2808wnde4vqx91w191p3io4fgabek2xipahvu7842i7308dqf1\display

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

100.0%

The strongest geographic signal for this file is Brazil with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for libmfx32-gen.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.

libmfx32-gen.dll is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x00059bf0

PE Sections:

Name Size of data MD5
.text 10145280 61308837566cfe2165fd9230d8e89794
IPPCODE 228352 62514ee6aa4630e8372b2f5bfa90d86e
.rdata 9916416 cb0e74778617ec4bd64e47c93f993de1
.data 380928 cd8d46c057b75482b5d55f634bcc85f2
.idata 7168 1b6aaac83a0ac6a413f839d352772b87
.gfids 72192 4e112ab513b477a3f44c3abd6ce5d9f2
IPPDATA 512 227669d528e84e2d1286ea82ce3acfe1
.tls 1024 c573bd7cea296a9c5d230ca6b5aee1a6
.00cfg 512 b5d723ebf10a791b5781f3f2d816e26e
.rsrc 186880 12ddb7a48a558f28381bd3857944f640
.reloc 423424 aa43fa5a5cfbab3029d1c255496c8e88

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.

More information: