GridinSoft Threat Intelligence

OLCFG.EXE file report

Clean record File reputation report
MD5 150b76ff2d2d7a12d92ac8241434f881
Latest seen 2021-09-26 20:36:37 (4 years ago)
First seen 2021-07-05 20:27:52 (4 years ago)
Size 113 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-07-05 20:27:52 (4 years ago); latest analysis 2021-09-26 20:36:37 (4 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft 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.

OLCFG.EXE is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Outlook. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-09-26 20:36:37 (4 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 Outlook
Company Name: Microsoft Corporation
MD5: 150b76ff2d2d7a12d92ac8241434f881
Size: 113 KB
First Published: 2021-07-05 20:27:52 (4 years ago)
Latest Published: 2021-09-26 20:36:37 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-09-26 20:36:37 (4 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\root

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

OLCFG.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 0x00001360
Image base 0x00400000

PE Sections:

Sections 5
Raw data 97280

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

.text 49664 bytes · 51.1% of section data
MD5 22e4c9b1c34d2837fef90a5b7b4991cd
.rdata 21504 bytes · 22.1% of section data
MD5 b6430bd5eb23bd7ebd845b6f1f6fc833
.data 2560 bytes · 2.6% of section data
MD5 231e6a8a950a979a5d9ecd7ffb0d587c
.rsrc 19456 bytes · 20.0% of section data
MD5 c5eda9f070bf260e4556d207068e8f30
.reloc 4096 bytes · 4.2% of section data
MD5 9c5e633de19548ee5023c38c26321ae7

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 150b76ff2d2d7a12d92ac8241434f881.
  • 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.