GridinSoft Threat Intelligence

kavdr.exe file report

Clean record File reputation report
MD5 c2fe879da481ae9e41f2d55def4cb93e
Latest seen 2021-12-12 21:31:33 (4 years ago)
First seen 2021-12-12 21:31:33 (4 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-12-12 21:31:33 (4 years ago); latest analysis 2021-12-12 21:31:33 (4 years ago).

Digital signature

Signed by Beijing Kingsoft Security software Co.,Ltd. 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.

kavdr.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-12-12 21:31:33 (4 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.

MD5: c2fe879da481ae9e41f2d55def4cb93e
Size: 1 MB
First Published: 2021-12-12 21:31:33 (4 years ago)
Latest Published: 2021-12-12 21:31:33 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-12-12 21:31:33 (4 years ago)
Signed By: Beijing Kingsoft Security software Co.,Ltd
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%\kingsoft\kingsoft antivirus\vipapp

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

kavdr.exe 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 0x0037f000
Image base 0x00400000

PE Sections:

Sections 6
Raw data 1589248

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

360448 bytes · 22.7% of section data
Uncommon name
MD5 9ba37962abedff379219a00a9676f8d9
.rsrc 151552 bytes · 9.5% of section data
MD5 648bcbde2767022019c8c5024eee76eb
.idata 4096 bytes · 0.3% of section data
Uncommon name
MD5 41b1e81070f35fbf92db208a13023732
4096 bytes · 0.3% of section data
Uncommon name
MD5 ad48d72f528798bcd4a7dfeffad392ec
ctvvyexm 1064960 bytes · 67.0% of section data
Uncommon name
MD5 98e4756303f5d94d4f78690d7d056729
ykedbbxm 4096 bytes · 0.3% of section data
Uncommon name
MD5 6a673511f7fa0a696b0c14916e304f77

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