GridinSoft Threat Intelligence
CC_MOD_PE.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2017-05-22 11:25:39 (9 years ago); latest analysis 2021-10-12 20:52:13 (4 years ago).
Product metadata: PE_Explorer Module.
Signed by CompuClever Systems Inc.. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
CC_MOD_PE.dll is a Windows file recorded in the ThreatInfo database. It is associated with PE_Explorer Module. The current detection status is Undefined, based on the latest analysis from 2021-10-12 20:52:13 (4 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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: | PE_Explorer Module |
| MD5: | 34e32d95f55b4f8ba807423547ff3ef0 |
| Size: | 445 KB |
| First Published: | 2017-05-22 11:25:39 (9 years ago) |
| Latest Published: | 2021-10-12 20:52:13 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-10-12 20:52:13 (4 years ago) |
Overview
| Signed By: | CompuClever Systems Inc. |
| Status: | Valid |
The signature on CC_MOD_PE.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %localappdata%\compuclever\ultra file opener |
| %sysdrive%\adwcleaner\quarantine\ozolmrbayf |
| %sysdrive%\data backup 19 januari 2018\appdata\local\compuclever |
| %localappdata%\compuclever |
ThreatInfo has observed CC_MOD_PE.dll 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.
Geographic signal
Observed country distribution
ThreatInfo has seen CC_MOD_PE.dll across 4 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Australia with 25.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for CC_MOD_PE.dll is Windows 10 with 75.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
CC_MOD_PE.dll 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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
c2362fd54385af99e632775be01d5953
c695c599eee15f5900bf970db56e0983
c5099130821ae5a1b3d8d165c634ba28
d2ae240046c15530212bf24a194ae227
eb5cb677afa1cfa66cd9d85049b9fff7
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.