GridinSoft Threat Intelligence

SCANPST.EXE file report

Clean record File reputation report
MD5 06b03d33a53aed183e213d82f01ee9d9
Latest seen 2021-04-21 20:48:26 (5 years ago)
First seen 2021-04-21 20:48:26 (5 years ago)
Size 36 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-04-21 20:48:26 (5 years ago); latest analysis 2021-04-21 20:48:26 (5 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft Office Outlook.

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.

SCANPST.EXE is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Office Outlook. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-04-21 20:48: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: Microsoft Office Outlook
Company Name: Microsoft Corporation
MD5: 06b03d33a53aed183e213d82f01ee9d9
Size: 36 KB
First Published: 2021-04-21 20:48:26 (5 years ago)
Latest Published: 2021-04-21 20:48:26 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-04-21 20:48:26 (5 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%\microsoft office

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

SCANPST.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 0x000050d3
Image base 0x30000000

PE Sections:

Sections 4
Raw data 30208

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

.text 23552 bytes · 78.0% of section data
MD5 acd55daa182e8971418e53e62917db79
.data 512 bytes · 1.7% of section data
MD5 fc0aa7570514d2beb850e66e188a2686
.rsrc 4096 bytes · 13.6% of section data
MD5 10b284b6d0bffc71cc3a429034992e11
.reloc 2048 bytes · 6.8% of section data
MD5 65d91d0c76580d97852662a3ab9ee9e0

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 06b03d33a53aed183e213d82f01ee9d9.
  • 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.