GridinSoft Threat Intelligence

crdliL64.dll file report

Under review File reputation report
MD5 f38308801defae8f5d7cbd1b458b7d57
Latest seen 2021-03-22 21:20:30 (5 years ago)
First seen 2017-07-20 06:06:17 (8 years ago)
Size 76 KB
Signed by Linkury Ltd

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-07-20 06:06:17 (8 years ago); latest analysis 2021-03-22 21:20:30 (5 years ago).

Digital signature

Signed by Linkury Ltd. 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.

crdliL64.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-03-22 21:20:30 (5 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: f38308801defae8f5d7cbd1b458b7d57
Size: 76 KB
First Published: 2017-07-20 06:06:17 (8 years ago)
Latest Published: 2021-03-22 21:20:30 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-22 21:20:30 (5 years ago)
Signed By: Linkury Ltd
Status: Valid

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

%programfiles%\lpt\resources
%sysdrive%\adwcleaner\quarantine\c\program files (x86)\lpt

ThreatInfo has observed crdliL64.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 100.0%

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

crdliL64.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 0x00001bac
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 69632

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

.text 43520 bytes · 62.5% of section data
MD5 49cbf8aef2b6dba522558cb4f00c3f69
.rdata 15872 bytes · 22.8% of section data
MD5 371b7426b6e49781c989879916696877
.data 5120 bytes · 7.4% of section data
MD5 a43f67189f79dfc0c186d2c173b825c7
.pdata 3072 bytes · 4.4% of section data
MD5 47c9821dc6f405b77f068966f8568c90
.rsrc 512 bytes · 0.7% of section data
MD5 ad9ddea3f5f0bf044a0b8a22b678aa20
.reloc 1536 bytes · 2.2% of section data
MD5 ce785e0c84f97c74078abcf3cf5545e7

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