GridinSoft Threat Intelligence

MSPTLS.DLL file report

Clean record File reputation report
MD5 34b820ce0b0a26cfaf78f6e57709ffb7
Latest seen 2022-04-18 23:34:45 (4 years ago)
First seen 2022-04-18 23:34:45 (4 years ago)
Size 738 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-04-18 23:34:45 (4 years ago); latest analysis 2022-04-18 23:34:45 (4 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.

MSPTLS.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 2022-04-18 23:34:45 (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: 2007 Microsoft Office system
Company Name: Microsoft Corporation
MD5: 34b820ce0b0a26cfaf78f6e57709ffb7
Size: 738 KB
First Published: 2022-04-18 23:34:45 (4 years ago)
Latest Published: 2022-04-18 23:34:45 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-04-18 23:34:45 (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.

%commondir%\microsoft shared

ThreatInfo has observed MSPTLS.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 10 100.0%

The most common operating system signal for MSPTLS.DLL 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.

MSPTLS.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 0x000033f5
Image base 0x6bdc0000

PE Sections:

Sections 4
Raw data 748544

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

.text 731136 bytes · 97.7% of section data
MD5 7cb52bef634d5b94e7a800f7dd6e3640
.data 10752 bytes · 1.4% of section data
MD5 19aacdefa3a3534b2c7ee6d46f8b1acf
.rsrc 2048 bytes · 0.3% of section data
MD5 f67894f3e13e0ac9d42d1ad9e67280a9
.reloc 4608 bytes · 0.6% of section data
MD5 d4c8c260940ebe0f564410aff51e9c27

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 34b820ce0b0a26cfaf78f6e57709ffb7.
  • 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.