GridinSoft Threat Intelligence

mso.dll file report

Clean record File reputation report
MD5 4a68ea31ff624a927e6d3b63fb695cfd
Latest seen 2021-02-12 04:05:23 (5 years ago)
First seen 2018-10-23 14:19:22 (7 years ago)
Size 16 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-10-23 14:19:22 (7 years ago); latest analysis 2021-02-12 04:05:23 (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.

mso.dll 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-02-12 04:05:23 (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: 4a68ea31ff624a927e6d3b63fb695cfd
Size: 16 MB
First Published: 2018-10-23 14:19:22 (7 years ago)
Latest Published: 2021-02-12 04:05:23 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-12 04:05:23 (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.

%sysdrive%\progra~1\common~1\micros~1
%commondir%\microsoft shared
%windir%\installer\$patchcache$\managed\00002109030000000000000000f01fec
%windir%\installer\$patchcache$\managed\00002109110000000000000000f01fec
%windir%\installer\$patchcache$\managed\000021091d00a0c00000000000f01fec
%desktop%\canaima\office2007portable\app\common
%desktop%\canaima\driver\office2007portable\app\common

ThreatInfo has observed mso.dll 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 40.0%
Windows XP 26.7%
Windows 10 26.7%
Windows 8.1 6.7%

The most common operating system signal for mso.dll is Windows 7 with 40.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.

mso.dll 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 0x00de6b31
Image base 0x32600000

PE Sections:

Sections 4
Raw data 17317888

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

.text 15136768 bytes · 87.4% of section data
Large raw data
MD5 2cb4f84bfd510f49c94f5028f04b6ec6
.data 820224 bytes · 4.7% of section data
MD5 e3f22d505033ce512f4da88d61b0fd42
.rsrc 614400 bytes · 3.5% of section data
MD5 a0900b6ce2452e81de62de760a180ea6
.reloc 746496 bytes · 4.3% of section data
MD5 b03c75e9705c95c46118964e2a57c5d0

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 4a68ea31ff624a927e6d3b63fb695cfd.
  • 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.