GridinSoft Threat Intelligence
mfxplugin64_hw.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2021-01-05 16:16:38 (5 years ago); latest analysis 2021-01-05 16:16:38 (5 years ago).
Company metadata: Intel Corporation. Product metadata: Intel® Media SDK Plugin.
Signed by Microsoft Windows Hardware Compatibility Publisher. ThreatInfo marks this publisher as trusted for this record.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
mfxplugin64_hw.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel® Media SDK Plugin. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-05 16:16:38 (5 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Intel® Media SDK Plugin |
| Company Name: | Intel Corporation |
| MD5: | 4c2d79710942bf6e1f061ac86e613680 |
| Size: | 23 MB |
| First Published: | 2021-01-05 16:16:38 (5 years ago) |
| Latest Published: | 2021-01-05 16:16:38 (5 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-01-05 16:16:38 (5 years ago) |
Overview
| Signed By: | Microsoft Windows Hardware Compatibility Publisher |
| Status: | Trusted Publisher |
ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.
Common Places:
| %localappdata%\slimware utilities inc\slimdrivers\backups\20190906t111820386595\swc |
ThreatInfo has observed mfxplugin64_hw.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 mfxplugin64_hw.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United Kingdom 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:
The most common operating system signal for mfxplugin64_hw.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
mfxplugin64_hw.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
d0ec72196fae7837232b0fbd473b3151
3a07fa063a341201287ebe459b4e7fef
39fb1c9c5780b345071a98c153f3dde7
cc49f06a29ab3ac7bbeb92f2033682b4
3a9440607fd38bd89baada8379971698
a5766926b5528825570049a17b082c8c
8b060cc7faee843ae113bba1203cd823
20cba0cf82919d7adadd9fee3b42f393
beb4019e532dd38e5c81f4d07573940b
acc81bebb315f5c6dd7f3ed668b8914e
d6e4b26aef895d2094373ddbbd674120
c836238295d29891fe75999e5f713db0
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 hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.