GridinSoft Threat Intelligence

PCMedikRegister.exe file report

Under review File reputation report
MD5 74e40e9c5e19d7c51c1a9b2d2ae2704f
Latest seen 2023-09-19 23:16:59 (2 years ago)
First seen 2023-09-19 23:16:59 (2 years ago)
Size 3 MB
Product PCMedikRegister

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

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

Publisher context

Product metadata: PCMedikRegister.

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.

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

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

PCMedikRegister.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 0x002b82fc
Image base 0x00400000

PE Sections:

Sections 11
Raw data 3809280

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

.text 2834944 bytes · 74.4% of section data
MD5 c87dbbcb5c98263a2e6b1de71eb41fc3
.itext 9216 bytes · 0.2% of section data
Uncommon name
MD5 913397b51ee5243be7257daaf4f54f8c
.data 51712 bytes · 1.4% of section data
MD5 fda7ee515ceb66236c57298522ac0282
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 13312 bytes · 0.3% of section data
MD5 fb89a93d379bf1675ee266e90bb74e2e
.didata 3072 bytes · 0.1% of section data
Uncommon name
MD5 2a662ee2c74725b528e3a2e41878db54
.edata 512 bytes · 0.0% of section data
MD5 4751d4e5d815e6e158e315266a9886d3
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.0% of section data
MD5 a355609810088bbc68487467468524b3
.reloc 258560 bytes · 6.8% of section data
MD5 117fae60aa0cb823918cce42dd08ee6d
.rsrc 637440 bytes · 16.7% of section data
MD5 6a57e3825de2ed5428979e5a554c8d5e

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 74e40e9c5e19d7c51c1a9b2d2ae2704f.
  • 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.