GridinSoft Threat Intelligence

mfx_mft_h264ve_32.dll file report

Under review File reputation report
MD5 58ea2d64349e9084caf1859a4fab5010
Latest seen 2021-08-26 20:38:10 (4 years ago)
First seen 2018-04-22 17:08:48 (8 years ago)
Size 2 MB
Publisher Intel Corporation
Product Intel® Media SDK
Signed by IntelVPGSigning2018

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-04-22 17:08:48 (8 years ago); latest analysis 2021-08-26 20:38:10 (4 years ago).

Publisher context

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

Digital signature

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

File context

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 2021-08-26 20:38:10 (4 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.

File Details

Product Name: Intel® Media SDK
Company Name: Intel Corporation
MD5: 58ea2d64349e9084caf1859a4fab5010
Size: 2 MB
First Published: 2018-04-22 17:08:48 (8 years ago)
Latest Published: 2021-08-26 20:38:10 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-08-26 20:38:10 (4 years ago)

Overview

Signed By: IntelVPGSigning2018
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.

Common Places:

%appdata%\uniblue\driverscanner\drivers\154853\gfx_win10_64_15.65.4.4944
%localappdata%\innovative solutions\drivermax\agent\restore\9r3tj8eaft28q0f18x01gik3l5kng349ka29l5on1524583im3\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.

Geographic signal

Observed country distribution

ThreatInfo has seen mfx_mft_h264ve_32.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Canada
Share 33.3%
Low High activity

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

OS Version:

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.

Analysis

mfx_mft_h264ve_32.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 0x000b46e0
Image base 0x10000000

PE Sections:

Sections 6
Raw data 2555904

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

.text 2134528 bytes · 83.5% of section data
MD5 9f221af90cafc306b36a77ee8f5efcec
.rdata 316416 bytes · 12.4% of section data
MD5 32156aa37c3bfa5f5f09a1a8f09ede6e
.data 20992 bytes · 0.8% of section data
MD5 4874a382abad89a996c47478a89e3c4f
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 3584 bytes · 0.1% of section data
MD5 1fe508233d032212e71c6f19b97201b4
.reloc 79872 bytes · 3.1% of section data
MD5 8804680576e65b4ddc430c9b70add9bd

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 58ea2d64349e9084caf1859a4fab5010.
  • 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.