GridinSoft Threat Intelligence

autoruns.exe file report

Clean record File reputation report
MD5 ca66a832a2872bd0c40bf7611f9562e7
Latest seen 2023-05-26 23:01:35 (3 years ago)
First seen 2023-05-26 23:01:35 (3 years ago)
Size 737 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-05-26 23:01:35 (3 years ago); latest analysis 2023-05-26 23:01:35 (3 years ago).

Publisher context

Company metadata: Sysinternals - www.sysinternals.com. Product metadata: Sysinternals autoruns.

Digital signature

Signed by Microsoft 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.

autoruns.exe is a Windows file recorded in the ThreatInfo database. It is associated with Sysinternals autoruns. The reported company name is Sysinternals - www.sysinternals.com. The current detection status is Clean, based on the latest analysis from 2023-05-26 23:01:35 (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: Sysinternals autoruns
Company Name: Sysinternals - www.sysinternals.com
MD5: ca66a832a2872bd0c40bf7611f9562e7
Size: 737 KB
First Published: 2023-05-26 23:01:35 (3 years ago)
Latest Published: 2023-05-26 23:01:35 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-05-26 23:01:35 (3 years ago)
Signed By: Microsoft 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.

%programfiles%\totalcommander2021\tools

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

autoruns.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 0x0004d6ae
Image base 0x00400000

PE Sections:

Sections 5
Raw data 745472

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

.text 458240 bytes · 61.5% of section data
MD5 03557f00b60c6d5e7d4a50ec0f51c972
.rdata 141312 bytes · 19.0% of section data
MD5 d130db1b879f76ac81eee547817a0b19
.data 10240 bytes · 1.4% of section data
MD5 f862e980a70256b15b77df98427cdeab
.rsrc 107520 bytes · 14.4% of section data
MD5 0858eb28ec9a8302f5dbbe699b0d7dfa
.reloc 28160 bytes · 3.8% of section data
MD5 18a6a4383c565bc224ea15c4f2614950

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