GridinSoft Threat Intelligence

PCMedik.exe file report

Under review File reputation report
MD5 b443a11c524008bc061aa4a7ba239231
Latest seen 2023-09-19 23:19:08 (2 years ago)
First seen 2023-09-19 23:19:08 (2 years ago)
Size 3 MB
Product PCMedik

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-09-19 23:19:08 (2 years ago); latest analysis 2023-09-19 23:19:08 (2 years ago).

Publisher context

Product metadata: PCMedik.

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.

PCMedik.exe is a Windows file recorded in the ThreatInfo database. It is associated with PCMedik. The current detection status is Undefined, based on the latest analysis from 2023-09-19 23:19:08 (2 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: PCMedik
MD5: b443a11c524008bc061aa4a7ba239231
Size: 3 MB
First Published: 2023-09-19 23:19:08 (2 years ago)
Latest Published: 2023-09-19 23:19:08 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-09-19 23:19:08 (2 years ago)
%programfiles%\pgware

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

PCMedik.exe 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 0x002f649c
Image base 0x00400000

PE Sections:

Sections 11
Raw data 4174336

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

.text 3091456 bytes · 74.1% of section data
MD5 2795eb615f9a8e29ba4b650d5831ac57
.itext 11264 bytes · 0.3% of section data
Uncommon name
MD5 e2812c6de93912204d35f3264c44b91a
.data 54784 bytes · 1.3% of section data
MD5 98847d184eb2c8098efa4e332e600f45
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 13824 bytes · 0.3% of section data
MD5 cca3bf40e01f1be4cca8e9ca264b4080
.didata 3072 bytes · 0.1% of section data
Uncommon name
MD5 e288a500116a96ef3a5a728f82a00199
.edata 512 bytes · 0.0% of section data
MD5 621f1f3a1f6b371a83c77c48d74dd346
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.0% of section data
MD5 9c5f4b173e4ef4db15b78dd7f6d0740c
.reloc 272896 bytes · 6.5% of section data
MD5 ebf6484779c6d70d766c3382fd4d5f79
.rsrc 726016 bytes · 17.4% of section data
MD5 74cefdc88d2935ab139b49a515b440fa

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