GridinSoft Threat Intelligence

win32api.pyd file report

Under review File reputation report
MD5 cd646e722c515cd13540b4b3d0e46e4b
Latest seen 2026-02-05 23:01:25 (3 months ago)
First seen 2026-02-05 23:01:25 (3 months ago)
Size 96 KB
Product PyWin32

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-02-05 23:01:25 (3 months ago); latest analysis 2026-02-05 23:01:25 (3 months 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.

win32api.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 2026-02-05 23:01:25 (3 months 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: cd646e722c515cd13540b4b3d0e46e4b
Size: 96 KB
First Published: 2026-02-05 23:01:25 (3 months ago)
Latest Published: 2026-02-05 23:01:25 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-05 23:01:25 (3 months ago)
%programfiles%

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

Windows 10 100.0%

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

win32api.pyd 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 0x0000d712
Image base 0x1e8c0000

PE Sections:

Sections 5
Raw data 97792

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

.text 53760 bytes · 55.0% of section data
MD5 e947926042bc238a46f632ea56b01c30
.rdata 30720 bytes · 31.4% of section data
MD5 bb7d5b94a644da6c39a118e1e1ef61a0
.data 4096 bytes · 4.2% of section data
MD5 99e94385addc4fd1c736d041042b2609
.rsrc 1024 bytes · 1.0% of section data
MD5 cc5f505111ecdf4f6d36c58b401c73ba
.reloc 8192 bytes · 8.4% of section data
MD5 c0b0d89d1fdac5c644a77021e588d2f3

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 cd646e722c515cd13540b4b3d0e46e4b.
  • 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.