GridinSoft Threat Intelligence

igdumdx32.dll file report

Under review File reputation report
MD5 f5eceaf5132d00b3da565dbdd14e430f
Latest seen 2023-06-15 23:22:33 (2 years ago)
First seen 2020-01-07 07:13:45 (6 years ago)
Size 558 KB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-07 07:13:45 (6 years ago); latest analysis 2023-06-15 23:22:33 (2 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel Graphics Accelerator Drivers for Windows XP(R).

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.

igdumdx32.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel Graphics Accelerator Drivers for Windows XP(R). The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2023-06-15 23:22:33 (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 Graphics Accelerator Drivers for Windows XP(R)
Company Name: Intel Corporation
MD5: f5eceaf5132d00b3da565dbdd14e430f
Size: 558 KB
First Published: 2020-01-07 07:13:45 (6 years ago)
Latest Published: 2023-06-15 23:22:33 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-06-15 23:22:33 (2 years ago)
%localappdata%\slimware utilities inc\slimdrivers\backups\20190617t095227932455\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20230607t192055131894\pci

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

Windows 7 100.0%

The most common operating system signal for igdumdx32.dll is Windows 7 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.

igdumdx32.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 0x00053dde
Image base 0x10000000

PE Sections:

Sections 5
Raw data 570880

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

.text 481280 bytes · 84.3% of section data
MD5 2e2b0719209fb9ee16cc4ac7ee144f28
.rdata 45056 bytes · 7.9% of section data
MD5 8cd94c9dfe72334fb4906a909a3ce64e
.data 26624 bytes · 4.7% of section data
MD5 20901ee9a8d1461b0bd7297fad2c066e
.rsrc 1536 bytes · 0.3% of section data
MD5 2b11a3ae05ffcbcffd4e114a6d07d580
.reloc 16384 bytes · 2.9% of section data
MD5 ee9ad08110f70e90f85dd9bd91860a05

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