GridinSoft Threat Intelligence

igxpun.exe file report

Clean record File reputation report
MD5 b20dd9a25878db53bc1a1822239f2a6e
Latest seen 2023-01-28 23:17:33 (3 years ago)
First seen 2023-01-28 23:17:33 (3 years ago)
Size 931 KB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-01-28 23:17:33 (3 years ago); latest analysis 2023-01-28 23:17:33 (3 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) Graphics Media Accelerator Driver.

Digital signature

Signed by Intel Corporation - Software and Firmware Products. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

igxpun.exe is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Graphics Media Accelerator Driver. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2023-01-28 23:17:33 (3 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.

Product Name: Intel(R) Graphics Media Accelerator Driver
Company Name: Intel Corporation
MD5: b20dd9a25878db53bc1a1822239f2a6e
Size: 931 KB
First Published: 2023-01-28 23:17:33 (3 years ago)
Latest Published: 2023-01-28 23:17:33 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-01-28 23:17:33 (3 years ago)
Signed By: Intel Corporation - Software and Firmware Products
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.

%sysdrive%\backup wanderson\turbo bos

ThreatInfo has observed igxpun.exe 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 10 100.0%

The most common operating system signal for igxpun.exe 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.

igxpun.exe 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 0x00038f5d
Image base 0x00400000

PE Sections:

Sections 4
Raw data 942080

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

.text 327680 bytes · 34.8% of section data
MD5 7ee80485497393fca9a885483a25a22b
.rdata 69632 bytes · 7.4% of section data
MD5 2e0cbe8b04bfc25e5ec2136297304d4b
.data 8192 bytes · 0.9% of section data
MD5 3b74ad211545a238377f9dfe4e0ce451
.rsrc 536576 bytes · 57.0% of section data
MD5 c7e295d187bb7357f78ebb95042db563

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.

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