GridinSoft Threat Intelligence

CIDCoreLight64.dll file report

Under review File reputation report
MD5 4d4697461f99e4651fc030b052bba344
Latest seen 2024-03-25 23:02:40 (2 years ago)
First seen 2017-05-21 18:10:02 (9 years ago)
Size 3 MB
Publisher CallingID Ltd.
Product CallingID

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 18:10:02 (9 years ago); latest analysis 2024-03-25 23:02:40 (2 years ago).

Publisher context

Company metadata: CallingID Ltd.. Product metadata: CallingID.

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.

CIDCoreLight64.dll is a Windows file recorded in the ThreatInfo database. It is associated with CallingID. The reported company name is CallingID Ltd.. The current detection status is Undefined, based on the latest analysis from 2024-03-25 23:02:40 (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: CallingID
Company Name: CallingID Ltd.
MD5: 4d4697461f99e4651fc030b052bba344
Size: 3 MB
First Published: 2017-05-21 18:10:02 (9 years ago)
Latest Published: 2024-03-25 23:02:40 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-03-25 23:02:40 (2 years ago)
%programfiles%\xfin_portal
%programfiles%

ThreatInfo has observed CIDCoreLight64.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 7 57.1%
Windows 10 39.3%
Windows 8.1 3.6%

The most common operating system signal for CIDCoreLight64.dll is Windows 7 with 57.1% 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.

CIDCoreLight64.dll 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 0x00192af0
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 3593728

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

.text 1879552 bytes · 52.3% of section data
MD5 e434d306c60fece9a66374e4754f377f
.orpc 512 bytes · 0.0% of section data
Uncommon name
MD5 d771fab08926de7bc68be4920f350fd3
.rdata 1494528 bytes · 41.6% of section data
MD5 199c6369eaa8cad9a04b9181291d5377
.data 45568 bytes · 1.3% of section data
MD5 f5d84bec97dbb5b881ea5a800a9cccde
.pdata 106496 bytes · 3.0% of section data
MD5 cec6a4b2657cc97fbbc5a9d64793177e
.rsrc 35328 bytes · 1.0% of section data
MD5 91b7a747f7e9c71c6ba17655a5bdf750
.reloc 31744 bytes · 0.9% of section data
MD5 60685023ccb630f10fa39d3345e2bb71

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 4d4697461f99e4651fc030b052bba344.
  • 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.