GridinSoft Threat Intelligence

servicemanager.pyd file report

Under review File reputation report
MD5 641a0bda0b318d866fd74fddbff11211
Latest seen 2023-03-13 23:43:47 (3 years ago)
First seen 2018-11-01 13:21:36 (7 years ago)
Size 31 KB
Product PyWin32

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-11-01 13:21:36 (7 years ago); latest analysis 2023-03-13 23:43:47 (3 years ago).

Publisher context

Product metadata: PyWin32.

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.

servicemanager.pyd is a Windows file recorded in the ThreatInfo database. It is associated with PyWin32. The current detection status is Undefined, based on the latest analysis from 2023-03-13 23:43:47 (3 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: PyWin32
MD5: 641a0bda0b318d866fd74fddbff11211
Size: 31 KB
First Published: 2018-11-01 13:21:36 (7 years ago)
Latest Published: 2023-03-13 23:43:47 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-03-13 23:43:47 (3 years ago)
%programfiles%\nemesys

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

100.0%

The strongest geographic signal for this file is Italy with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

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

servicemanager.pyd is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00003c08
Image base 0x000000001e7d0000

PE Sections:

Sections 6
Raw data 31232

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

.text 12800 bytes · 41.0% of section data
MD5 8f8dfd3d71e9ba600c9d521fce1cbd69
.rdata 10240 bytes · 32.8% of section data
MD5 51053d2cc9fa40879761c8157004d3fa
.data 1536 bytes · 4.9% of section data
MD5 d50984772c4d4afc210ac072b6b5a240
.pdata 1024 bytes · 3.3% of section data
MD5 ad78df3d78ccf33ef258f9536d1b8b35
.rsrc 5120 bytes · 16.4% of section data
MD5 a649c826000f4fe8844804b5779ba044
.reloc 512 bytes · 1.6% of section data
MD5 2c087cef8e92d8176408aaf7593918f1

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 641a0bda0b318d866fd74fddbff11211.
  • 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.