mfx_mft_h264ve_32.dll file report

MD5 c71aa9b1fcccaa1995c267a8a38caef9
Latest seen 2023-12-11 23:33:59 (2 years ago)
First seen 2017-05-22 09:04:50 (8 years ago)
Size 1 MB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 09:04:50 (8 years ago); latest analysis 2023-12-11 23:33:59 (2 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel® Media SDK.

Digital signature

Signed by IntelVPGSigning2016. 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.

mfx_mft_h264ve_32.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel® Media SDK. The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2023-12-11 23:33:59 (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® Media SDK
Company Name: Intel Corporation
MD5: c71aa9b1fcccaa1995c267a8a38caef9
Size: 1 MB
First Published: 2017-05-22 09:04:50 (8 years ago)
Latest Published: 2023-12-11 23:33:59 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-12-11 23:33:59 (2 years ago)
Signed By: IntelVPGSigning2016
Status: Valid

The signature on mfx_mft_h264ve_32.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\uploads\55qm5eg6mj3jhs8t9878e2a485a00lbffog7w6ybk1yv266x31\display\pci_ven_8086@amp;dev_0416
%localappdata%\innovative solutions\drivermax\agent\uploads\3g8928js2t22o4o26mw3283l0wqb0f5x19de6304t0vvxn0k8a\display
%localappdata%\innovative solutions\drivermax\agent\uploads\bbcur974lee8586295185ctc6ep64xl0wu53riscob127mi1tb\display
%localappdata%\innovative solutions\drivermax\agent\uploads\227n90436fqy3b9wo9k78xvbg4b0yw4ou8w5c6w31334lt9608\display

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

50.0%
25.0%
25.0%

The strongest geographic signal for this file is Brazil with 50.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 mfx_mft_h264ve_32.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.

mfx_mft_h264ve_32.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: 0x000ae536

PE Sections:

Name Size of data MD5
.text 1029632 31850adf0ebb986259adcf880f53047c
.rdata 280576 44eb233d4a71a783e3fce5ede3bb856d
.data 27136 abc437fabe4e5420e9a17152919d6553
.rsrc 3584 40e6ce58e6c64385294d8f0684984826
.reloc 61440 5c0ead75238aad712cc6771284fca629

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: