GridinSoft Threat Intelligence

mspview.exe file report

Clean record File reputation report
MD5 8cd92cb3176a49fe8dda63b0c2446d64
Latest seen 2021-04-21 20:52:10 (5 years ago)
First seen 2021-04-21 20:52:10 (5 years ago)
Size 425 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

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

Publisher context

Company metadata: Microsoft Corporation. Product metadata: 2007 Microsoft Office system.

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.

mspview.exe is a Windows file recorded in the ThreatInfo database. It is associated with 2007 Microsoft Office system. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-04-21 20:52:10 (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: 2007 Microsoft Office system
Company Name: Microsoft Corporation
MD5: 8cd92cb3176a49fe8dda63b0c2446d64
Size: 425 KB
First Published: 2021-04-21 20:52:10 (5 years ago)
Latest Published: 2021-04-21 20:52:10 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-04-21 20:52:10 (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.

%commondir%\microsoft shared\modi

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

mspview.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 0x0004d13c
Image base 0x30000000

PE Sections:

Sections 5
Raw data 429056

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

.text 364032 bytes · 84.8% of section data
MD5 2a7c3c3e919761a689c9af901aa384c3
.data 13312 bytes · 3.1% of section data
MD5 1ddee6dc3cf27331b11b3eb79470eac9
.mspdta 512 bytes · 0.1% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 19456 bytes · 4.5% of section data
MD5 3e59d73a6736dfdd2feb05fff9ffcda0
.reloc 31744 bytes · 7.4% of section data
MD5 518cc21532c0947a5ef829d2f232a60a

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 8cd92cb3176a49fe8dda63b0c2446d64.
  • 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.