GridinSoft Threat Intelligence

iga64.dll file report

Under review File reputation report
MD5 b1f48389518987044685a0291a3380f1
Latest seen 2021-01-01 15:10:04 (5 years ago)
First seen 2021-01-01 14:43:58 (5 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-01 14:43:58 (5 years ago); latest analysis 2021-01-01 15:10:04 (5 years ago).

Digital signature

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

iga64.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-01-01 15:10:04 (5 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.

MD5: b1f48389518987044685a0291a3380f1
Size: 2 MB
First Published: 2021-01-01 14:43:58 (5 years ago)
Latest Published: 2021-01-01 15:10:04 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-01 15:10:04 (5 years ago)

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

%localappdata%\innovative solutions\drivermax\agent\restore\0o5q32f50y910891x62n5c5shgnsvrjvt35o1j4f1lbt0sb81b\display

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

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

iga64.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.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x000af740
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 2843648

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

.text 887296 bytes · 31.2% of section data
MD5 d7de30cd5b463ca50dd77932581b33a0
.rdata 1748480 bytes · 61.5% of section data
MD5 3ca5a68c1e31b3674cdbed7909e1410a
.data 107520 bytes · 3.8% of section data
MD5 d7a0a92f84c12b2b5955bd9054671e6d
.pdata 31744 bytes · 1.1% of section data
MD5 70ffca2e5ac749b8b1b407d33832248c
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 02bb0d22ca0d236bbe07040078803639
.reloc 68096 bytes · 2.4% of section data
MD5 5b6b1105f28d1106578fe238adbeef1c

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