GridinSoft Threat Intelligence

cce.exe file report

Clean record File reputation report
MD5 7f391cc9a5f028aceb724444709eaacd
Latest seen 2024-04-27 23:02:12 (2 years ago)
First seen 2024-04-27 23:02:12 (2 years ago)
Size 8 MB
Publisher COMODO

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-04-27 23:02:12 (2 years ago); latest analysis 2024-04-27 23:02:12 (2 years ago).

Publisher context

Company metadata: COMODO. Product metadata: COMODO Internet Security.

Digital signature

Signed by Comodo Security Solutions, Inc.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

cce.exe is a Windows file recorded in the ThreatInfo database. It is associated with COMODO Internet Security. The reported company name is COMODO. The current detection status is Clean, based on the latest analysis from 2024-04-27 23:02:12 (2 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: COMODO Internet Security
Company Name: COMODO
MD5: 7f391cc9a5f028aceb724444709eaacd
Size: 8 MB
First Published: 2024-04-27 23:02:12 (2 years ago)
Latest Published: 2024-04-27 23:02:12 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-04-27 23:02:12 (2 years ago)
Signed By: Comodo Security Solutions, Inc.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%\comodo

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

cce.exe 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 0x001ff4a8
Image base 0x0000000140000000

PE Sections:

Sections 6
Raw data 8398336

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

.text 4012544 bytes · 47.8% of section data
MD5 df08aa29c2a6580f6f356461b4ea9a7d
.rdata 1662464 bytes · 19.8% of section data
MD5 c6367019baa531454c89fd108784ec7f
.data 76800 bytes · 0.9% of section data
MD5 4e0813454c082da748eaaa2f7102b232
.pdata 205824 bytes · 2.5% of section data
MD5 daf67f3f46906f82552ae3c6fd8c96aa
.rsrc 2315264 bytes · 27.6% of section data
MD5 8e08c5123d7d8de80a1e905235009726
.reloc 125440 bytes · 1.5% of section data
MD5 ccef120159ff1a6ba86b75d2eb62a56e

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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