GridinSoft Threat Intelligence

OIS.EXE file report

Clean record File reputation report
MD5 35550a6c24528fa2d949d7c52350f7ff
Latest seen 2024-05-31 23:01:58 (2 years ago)
First seen 2019-05-28 08:04:37 (6 years ago)
Size 268 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2019-05-28 08:04:37 (6 years ago); latest analysis 2024-05-31 23:01:58 (2 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft Office Picture Manager.

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.

OIS.EXE is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Office Picture Manager. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2024-05-31 23:01:58 (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: Microsoft Office Picture Manager
Company Name: Microsoft Corporation
MD5: 35550a6c24528fa2d949d7c52350f7ff
Size: 268 KB
First Published: 2019-05-28 08:04:37 (6 years ago)
Latest Published: 2024-05-31 23:01:58 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-05-31 23:01:58 (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%\microsoft office

ThreatInfo has observed OIS.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 66.7%
Windows 7 33.3%

The most common operating system signal for OIS.EXE is Windows 10 with 66.7% 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.

OIS.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 0x0000c323
Image base 0x30000000

PE Sections:

Sections 4
Raw data 266752

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

.text 62464 bytes · 23.4% of section data
MD5 abaa21c3c1ccf292d2beeed67999c5cf
.data 3584 bytes · 1.3% of section data
MD5 16b405be2c0258943c151ad75c78b101
.rsrc 196096 bytes · 73.5% of section data
MD5 5c7301ee8b8deba715c33e98d1711245
.reloc 4608 bytes · 1.7% of section data
MD5 e3e13d8fff7c8457773de60ec6d44e6f

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 35550a6c24528fa2d949d7c52350f7ff.
  • 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.