GridinSoft Threat Intelligence
igdde32.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2024-12-27 23:01:40 (a year ago); latest analysis 2024-12-27 23:01:40 (a year ago).
Company metadata: Intel Corporation. Product metadata: Intel® Media SDK Plugin.
Signed by Intel(R) Software Development Products;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
igdde32.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 Undefined, based on the latest analysis from 2024-12-27 23:01:40 (a year 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 Plugin |
| Company Name: | Intel Corporation |
| MD5: | 9a1e8f1025cccba1fda948c1241d7769 |
| Size: | 4 MB |
| First Published: | 2024-12-27 23:01:40 (a year ago) |
| Latest Published: | 2024-12-27 23:01:40 (a year ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2024-12-27 23:01:40 (a year ago) |
Overview
| Signed By: | Intel(R) Software Development Products;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on igdde32.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%\slimware utilities inc\driverupdate\backups\20180305t090738920\pci |
ThreatInfo has observed igdde32.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 igdde32.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 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:
The most common operating system signal for igdde32.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
igdde32.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. 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.
2012bf2c36beda5ac01c361e9f7df96b
d4de8e4d81d0fa7bf5925532e65a32a2
d3b27f7710fdcbf25ca0d2cee1cac24a
1d12c1cef8bdaaff84413aa7df9980da
27b33e56dad256f7bcd3352b2152c30d
1f354d76203061bfdd5a53dae48d5435
ea36891d86b7fd788351bee04330a9f1
da20a9a315b3014d743421095dded9f7
c56a915d0f7ee12a984edc8e4fee620f
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.