GridinSoft Threat Intelligence

CC_MOD_GMWTL.dll file report

Under review File reputation report
MD5 8ce84a5d1f864625396f4f11348ef1d7
Latest seen 2021-10-12 20:42:56 (4 years ago)
First seen 2017-05-22 11:25:41 (8 years ago)
Size 385 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:25:41 (8 years ago); latest analysis 2021-10-12 20:42:56 (4 years ago).

Digital signature

Signed by CompuClever Systems Inc.. The signature is reported as valid, but signed files can still be bundled or abused.

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.

CC_MOD_GMWTL.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-10-12 20:42:56 (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.

MD5: 8ce84a5d1f864625396f4f11348ef1d7
Size: 385 KB
First Published: 2017-05-22 11:25:41 (8 years ago)
Latest Published: 2021-10-12 20:42:56 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-10-12 20:42:56 (4 years ago)
Signed By: CompuClever Systems Inc.
Status: Valid

The signature on CC_MOD_GMWTL.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.

%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_GMWTL.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.

Windows 10 75.0%
Windows 7 25.0%

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

CC_MOD_GMWTL.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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x000346b9
Image base 0x10000000

PE Sections:

Sections 5
Raw data 387584

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

.text 228352 bytes · 58.9% of section data
MD5 3ad097ea241178599a633faedcb030f5
.rdata 71680 bytes · 18.5% of section data
MD5 9c4d2a8250193e126e439b2791fe26c1
.data 9728 bytes · 2.5% of section data
MD5 9dac08ff1b31366da991ad82a63b6145
.rsrc 60416 bytes · 15.6% of section data
MD5 b6a7cc8b40be8dcbc02d680ae0a87f9e
.reloc 17408 bytes · 4.5% of section data
MD5 77b29586ad391b30373586616eef6170

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 8ce84a5d1f864625396f4f11348ef1d7.
  • 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.