GridinSoft Threat Intelligence

klswapiproxy.kdl file report

Under review File reputation report
MD5 857949069d9d765e8cd2ffc531260da5
Latest seen 2022-09-01 23:29:55 (3 years ago)
First seen 2017-05-28 14:07:38 (8 years ago)
Size 58 KB
Publisher Kaspersky Lab ZAO

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-28 14:07:38 (8 years ago); latest analysis 2022-09-01 23:29:55 (3 years ago).

Publisher context

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

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.

klswapiproxy.kdl is a Windows file recorded in the ThreatInfo database. It is associated with Kaspersky Anti-Virus. The reported company name is Kaspersky Lab ZAO. The current detection status is Undefined, based on the latest analysis from 2022-09-01 23:29:55 (3 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: Kaspersky Anti-Virus
Company Name: Kaspersky Lab ZAO
MD5: 857949069d9d765e8cd2ffc531260da5
Size: 58 KB
First Published: 2017-05-28 14:07:38 (8 years ago)
Latest Published: 2022-09-01 23:29:55 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-09-01 23:29:55 (3 years ago)
%commonappdata%\baidu\baidusd\kav\bases
%allusersprofile%\\application data\baidu\baidusd\kav\bases
%allusersprofile%\\application data\baidu\baidusd\kav
%commonappdata%\baidu\baidusd\kav

ThreatInfo has observed klswapiproxy.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 50.0%
Windows 10 30.0%
Windows 8.1 12.5%
Windows XP 5.0%
Windows 8 2.5%

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

klswapiproxy.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 0x00005ef3
Image base 0x00400000

PE Sections:

Sections 4
Raw data 58368

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

.text 47616 bytes · 81.6% of section data
MD5 39ac7e400ba1b3db092e7c841d42e153
.data 3584 bytes · 6.1% of section data
MD5 c65af9fe32b4fe4a482e88d594f7cbc4
.rsrc 1536 bytes · 2.6% of section data
MD5 31a6ed9f8fcb4d8fabc3d9fd1522ab04
.reloc 5632 bytes · 9.6% of section data
MD5 866f275695f561035df4987442da3eed

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 857949069d9d765e8cd2ffc531260da5.
  • 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.