GridinSoft Threat Intelligence

win32file.pyd file report

Under review File reputation report
MD5 35e1334f4d1809d95906197678ce789d
Latest seen 2022-02-26 23:13:27 (4 years ago)
First seen 2022-02-26 23:13:27 (4 years ago)
Size 153 KB
Product PyWin32

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-02-26 23:13:27 (4 years ago); latest analysis 2022-02-26 23:13:27 (4 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.

File context

win32file.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 2022-02-26 23:13:27 (4 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.

File Details

Product Name: PyWin32
MD5: 35e1334f4d1809d95906197678ce789d
Size: 153 KB
First Published: 2022-02-26 23:13:27 (4 years ago)
Latest Published: 2022-02-26 23:13:27 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-02-26 23:13:27 (4 years ago)

Common Places:

%commonappdata%\majaovca\chia-blockchain\app-1.2.9\resources\app.asar.unpacked

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

Geography:

1 observed countries
100.0%

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

OS Version:

Windows 10 100.0%

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

Analysis

win32file.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 0x00014c48
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 156160

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

.text 86016 bytes · 55.1% of section data
MD5 4f6d4bf6d4a7e5115595705034dcabe1
.rdata 51712 bytes · 33.1% of section data
MD5 8ea7a170f5e1401a7f674ff5a124adf7
.data 8704 bytes · 5.6% of section data
MD5 dd238abded6ff373ae75288e3a96ab55
.pdata 7680 bytes · 4.9% of section data
MD5 3dbe79e4171c962348ba740e4eba1e18
.gfids 512 bytes · 0.3% of section data
Uncommon name
MD5 6b4d76af2bdc9aaf78dda6f2390e8eec
.rsrc 1024 bytes · 0.7% of section data
MD5 6c0b338b012caf8d83d70f8149f43a55
.reloc 512 bytes · 0.3% of section data
MD5 a683d74bbb7ade7b750714937f86983a

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 35e1334f4d1809d95906197678ce789d.
  • 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.