GridinSoft Threat Intelligence

K-Lite.exe file report

Under review File reputation report
MD5 7741210abfcc866f3d450d7d2818f590
Latest seen 2022-02-27 23:54:11 (4 years ago)
First seen 2022-02-27 23:54:11 (4 years ago)
Size 23 MB
Publisher KLCP

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-02-27 23:54:11 (4 years ago); latest analysis 2022-02-27 23:54:11 (4 years ago).

Publisher context

Company metadata: KLCP . Product metadata: K-Lite Codec Pack .

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.

K-Lite.exe is a Windows file recorded in the ThreatInfo database. It is associated with K-Lite Codec Pack . The reported company name is KLCP . The current detection status is Undefined, based on the latest analysis from 2022-02-27 23:54:11 (4 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: K-Lite Codec Pack
Company Name: KLCP
MD5: 7741210abfcc866f3d450d7d2818f590
Size: 23 MB
First Published: 2022-02-27 23:54:11 (4 years ago)
Latest Published: 2022-02-27 23:54:11 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-02-27 23:54:11 (4 years ago)
%appdata%\driverpack cloud

ThreatInfo has observed K-Lite.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 8.1 100.0%

The most common operating system signal for K-Lite.exe is Windows 8.1 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.

K-Lite.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 0x00039de8
Image base 0x00400000

PE Sections:

Sections 10
Raw data 401408

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

.text 227328 bytes · 56.6% of section data
MD5 4eb9b16177faf7dff46f3db64e245671
.itext 5632 bytes · 1.4% of section data
Uncommon name
MD5 3ce90feeb448b0f7894c94b97d34841b
.data 10752 bytes · 2.7% of section data
MD5 fa263132070bf86cd19382710007bbf4
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 3584 bytes · 0.9% of section data
MD5 52501ab6c2b2d5632f51d215c008d727
.didata 512 bytes · 0.1% of section data
Uncommon name
MD5 e829a65dadd4dcae80047d6781b5bd38
.edata 512 bytes · 0.1% of section data
MD5 0eb5fd06814d8fb6aa4590ffcdae9d15
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.1% of section data
MD5 1decb6051aae7901c27961431e73195e
.rsrc 152576 bytes · 38.0% of section data
MD5 911a9fb86417c25df8a3d5bfd523dc65

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 7741210abfcc866f3d450d7d2818f590.
  • 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.