GridinSoft Threat Intelligence

psexec.exe file report

Clean record File reputation report
MD5 78a2c9d79c21ddfcb7ced32f5ebec618
Latest seen 2024-03-16 23:11:12 (2 years ago)
First seen 2024-03-16 23:11:12 (2 years ago)
Size 229 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-03-16 23:11:12 (2 years ago); latest analysis 2024-03-16 23:11:12 (2 years ago).

Publisher context

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

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.

psexec.exe is a Windows file recorded in the ThreatInfo database. It is associated with Sysinternals PsExec. The reported company name is Sysinternals - www.sysinternals.com. The current detection status is Clean, based on the latest analysis from 2024-03-16 23:11:12 (2 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 PsExec
Company Name: Sysinternals - www.sysinternals.com
MD5: 78a2c9d79c21ddfcb7ced32f5ebec618
Size: 229 KB
First Published: 2024-03-16 23:11:12 (2 years ago)
Latest Published: 2024-03-16 23:11:12 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-03-16 23:11:12 (2 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%

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

The most common operating system signal for psexec.exe is Windows Vista 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.

psexec.exe is identified as pe for 32-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 32-bit
Subsystem Windows CUI
Entry point 0x00007a39
Image base 0x00400000

PE Sections:

Sections 4
Raw data 221184

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

.text 77824 bytes · 35.2% of section data
MD5 cbb1360cee5e1423cba49dbcd81961d5
.rdata 32768 bytes · 14.8% of section data
MD5 7bf7f98e4ed54d447500c8097c729844
.data 8192 bytes · 3.7% of section data
MD5 7bdb64e805368e02f844f1c8cb904b47
.rsrc 102400 bytes · 46.3% of section data
MD5 1dfceb168da430d2215d82329d1b6d23

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 78a2c9d79c21ddfcb7ced32f5ebec618.
  • 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.