GridinSoft Threat Intelligence

WsmanClient.dll file report

Under review File reputation report
MD5 09c0dadb8e079ae3df46b1072f4d0ca1
Latest seen 2021-01-10 23:53:15 (5 years ago)
First seen 2020-07-28 13:57:54 (5 years ago)
Size 1 MB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-07-28 13:57:54 (5 years ago); latest analysis 2021-01-10 23:53:15 (5 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) Management and Security Application User Notification Service.

Digital signature

Signed by Intel(R) Embedded Subsystems and IP Blocks Group;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

WsmanClient.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Management and Security Application User Notification Service. The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2021-01-10 23:53:15 (5 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Intel(R) Management and Security Application User Notification Service
Company Name: Intel Corporation
MD5: 09c0dadb8e079ae3df46b1072f4d0ca1
Size: 1 MB
First Published: 2020-07-28 13:57:54 (5 years ago)
Latest Published: 2021-01-10 23:53:15 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-10 23:53:15 (5 years ago)

The signature on WsmanClient.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%commonappdata%\winzip\winzip driver updater\downloads\49
%commonappdata%\winzip\winzip driver updater\downloads\4261e630-c954-432a-9b0b-dc286365b7e4
%commonappdata%\winzip\winzip driver updater\downloads\98b3b50a-d973-4aac-9761-e2f9e2815b9e
%commonappdata%\winzip\winzip driver updater\downloads\116
%commonappdata%\reviversoft\driver reviver\downloads\102
%commonappdata%\reviversoft\driver reviver\downloads\d0152a05-cd94-46da-b29d-53fccc8dcae7
%commonappdata%\reviversoft\driver reviver\downloads\125
%commonappdata%\reviversoft\driver reviver\downloads\c7732c27-c61d-40cd-803e-f082f2d6563a
%commonappdata%\reviversoft\driver reviver\downloads\129
%commonappdata%\reviversoft\driver reviver\downloads\d63d5422-0650-42f1-8c1a-d8b7b5232af9

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

WsmanClient.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 0x000d21b0
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1901056

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

.text 1198592 bytes · 63.0% of section data
MD5 e8ed19985ce3021e34bc32d7473065cb
.rdata 428032 bytes · 22.5% of section data
MD5 fe5bfcc406dfcf07acc5670d81e89a04
.data 146432 bytes · 7.7% of section data
MD5 b337be9f5d63271bd2806bafe29fd695
.rsrc 1536 bytes · 0.1% of section data
MD5 9270f1249016b1e4d4a05ad46cdd538d
.reloc 126464 bytes · 6.7% of section data
MD5 d6d65956bdeab2a16f2891c7933f40bb

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 09c0dadb8e079ae3df46b1072f4d0ca1.
  • 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.