GridinSoft Threat Intelligence

pdm.kdl file report

Clean record File reputation report
MD5 3e8b21cf357ecefe6529658c1ae62636
Latest seen 2022-09-01 23:30:25 (3 years ago)
First seen 2017-05-28 14:07:38 (9 years ago)
Size 421 KB
Publisher Kaspersky Lab ZAO
Signed by Kaspersky Lab

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-28 14:07:38 (9 years ago); latest analysis 2022-09-01 23:30:25 (3 years ago).

Publisher context

Company metadata: Kaspersky Lab ZAO. Product metadata: Kaspersky Anti-Virus engine.

Digital signature

Signed by Kaspersky Lab. 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. 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.

pdm.kdl is a Windows file recorded in the ThreatInfo database. It is associated with Kaspersky Anti-Virus engine. The reported company name is Kaspersky Lab ZAO. The current detection status is Clean, based on the latest analysis from 2022-09-01 23:30:25 (3 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: Kaspersky Anti-Virus engine
Company Name: Kaspersky Lab ZAO
MD5: 3e8b21cf357ecefe6529658c1ae62636
Size: 421 KB
First Published: 2017-05-28 14:07:38 (9 years ago)
Latest Published: 2022-09-01 23:30:25 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-09-01 23:30:25 (3 years ago)
Signed By: Kaspersky Lab
Status: Valid

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

%commonappdata%\baidu\baidusd\kav\bases
%allusersprofile%\\application data\baidu\baidusd\kav\bases
%commonappdata%\baidu\baidusd\kav
%allusersprofile%\\application data\baidu\baidusd\kav

ThreatInfo has observed pdm.kdl 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 48.9%
Windows 10 31.9%
Windows 8.1 12.8%
Windows XP 4.3%
Windows 8 2.1%

The most common operating system signal for pdm.kdl is Windows 7 with 48.9% 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.

pdm.kdl 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 0x00059c40
Image base 0x38000000

PE Sections:

Sections 5
Raw data 423936

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

.text 366592 bytes · 86.5% of section data
MD5 59f79b47bb546bcf311918ae8fb3cc4c
.rdata 40448 bytes · 9.5% of section data
MD5 ad1ea76937f0d8d2dbbfa28e718c0568
.data 2560 bytes · 0.6% of section data
MD5 4983f0aed17d45e62912886a97509c58
.rsrc 1536 bytes · 0.4% of section data
MD5 f2c71e5e96fc0fdb0345edcb5b67087d
.reloc 12800 bytes · 3.0% of section data
MD5 6c7422b0a54a7914103f3f7534501124

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 3e8b21cf357ecefe6529658c1ae62636.
  • 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.