GridinSoft Threat Intelligence

infinst_autol.exe file report

Clean record File reputation report
MD5 c249f504333032ec159766f3fc512b1a
Latest seen 2021-01-09 00:27:26 (5 years ago)
First seen 2021-01-09 00:27:26 (5 years ago)
Size 2 MB
Publisher Intel Corporation
Signed by Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-01-09 00:27:26 (5 years ago); latest analysis 2021-01-09 00:27:26 (5 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel® Chipset Device Software.

Digital signature

Signed by Intel Corporation. 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.

infinst_autol.exe is a Windows file recorded in the ThreatInfo database. It is associated with Intel® Chipset Device Software. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-09 00:27:26 (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.

Product Name: Intel® Chipset Device Software
Company Name: Intel Corporation
MD5: c249f504333032ec159766f3fc512b1a
Size: 2 MB
First Published: 2021-01-09 00:27:26 (5 years ago)
Latest Published: 2021-01-09 00:27:26 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-09 00:27:26 (5 years ago)
Signed By: Intel Corporation
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%\طرح4\aaa\new folder (2)\driver\chipset\intel\intel chipset driver

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

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

infinst_autol.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 0x00016e42
Image base 0x00400000

PE Sections:

Sections 4
Raw data 2777088

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

.text 131072 bytes · 4.7% of section data
MD5 43978df75a9191f6223d716726c92db4
.rdata 16384 bytes · 0.6% of section data
MD5 d7fe197d52f22768131f5b40b8bed656
.data 8192 bytes · 0.3% of section data
MD5 73505ce94bc82a06f74624aba0b8a47b
.rsrc 2621440 bytes · 94.4% of section data
MD5 3d20ac4c90477188059c61eea91f2cc1

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