GridinSoft Threat Intelligence

mfx_mft_h265ve_64.dll file report

Under review File reputation report
MD5 ad0196d029886d0ff54808e9458ca6c5
Latest seen 2021-08-21 20:40:33 (4 years ago)
First seen 2021-08-21 20:40:33 (4 years ago)
Size 3 MB
Publisher Intel Corporation
Product Intel® Media SDK
Signed by IntelVPGSigning2021;Microsoft Windows Hardware Compatibility Publisher

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-08-21 20:40:33 (4 years ago); latest analysis 2021-08-21 20:40:33 (4 years ago).

Publisher context

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

Digital signature

Signed by IntelVPGSigning2021;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.

File context

mfx_mft_h265ve_64.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-21 20:40:33 (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: ad0196d029886d0ff54808e9458ca6c5
Size: 3 MB
First Published: 2021-08-21 20:40:33 (4 years ago)
Latest Published: 2021-08-21 20:40:33 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-08-21 20:40:33 (4 years ago)

Overview

Signed By: IntelVPGSigning2021;Microsoft Windows Hardware Compatibility Publisher
Status: Valid

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

%localappdata%\innovative solutions\drivermax\agent\uploads\2tk2890158n60lu0cg9ly83dy1rv9m52px829u308hnte174cm\display

ThreatInfo has observed mfx_mft_h265ve_64.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_h265ve_64.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 100.0%
Low High activity

The strongest geographic signal for this file is United States with 100.0% 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_h265ve_64.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_h265ve_64.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x000e1c70
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 3162624

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

.text 1638400 bytes · 51.8% of section data
MD5 13475c3275088ed8855cac0f12c53721
TRSCODE 851968 bytes · 26.9% of section data
Uncommon name
MD5 439b6022ef6927afeb801d07b6dca31f
.rdata 535552 bytes · 16.9% of section data
MD5 ba49ba588d0d1ddc79cb9fd67bac271c
.data 27136 bytes · 0.9% of section data
MD5 c3c59a63b4220ab340ed5ed911394449
.pdata 95232 bytes · 3.0% of section data
MD5 466ae86f0202328732d3b2c15710ce6d
.rsrc 1024 bytes · 0.0% of section data
MD5 a142469bff25b9f722c88f0437c32985
.reloc 13312 bytes · 0.4% of section data
MD5 b06750b2dde78b2a0f8d3036611e046f

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 ad0196d029886d0ff54808e9458ca6c5.
  • 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.