GridinSoft Threat Intelligence

KKPLuaCJSON.dll file report

Under review File reputation report
MD5 243ef83f01d32715eb56bb5455ceb938
Latest seen 2021-07-01 20:28:16 (4 years ago)
First seen 2017-10-19 06:07:05 (8 years ago)
Size 131 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-10-19 06:07:05 (8 years ago); latest analysis 2021-07-01 20:28:16 (4 years ago).

Digital signature

Signed by Shenzhen Video Legend Network Technology Co.,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.

KKPLuaCJSON.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-07-01 20:28:16 (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.

MD5: 243ef83f01d32715eb56bb5455ceb938
Size: 131 KB
First Published: 2017-10-19 06:07:05 (8 years ago)
Latest Published: 2021-07-01 20:28:16 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-07-01 20:28:16 (4 years ago)

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

%appdata%\video legend\rbc\program
%programfiles%\video legend\kkp
%appdata%\video legend\rbc

ThreatInfo has observed KKPLuaCJSON.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 75.0%
Windows 7 25.0%

The most common operating system signal for KKPLuaCJSON.dll is Windows 10 with 75.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.

KKPLuaCJSON.dll 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 0x00012149
Image base 0x10000000

PE Sections:

Sections 5
Raw data 126976

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

.text 74752 bytes · 58.9% of section data
MD5 9fab2ea390ff2fb20872c76707c12afc
.rdata 35328 bytes · 27.8% of section data
MD5 3fa06aec5adfc52ff44d33424a030d3b
.data 4608 bytes · 3.6% of section data
MD5 6eb059078815054e9515ef9f29ad4019
.rsrc 4608 bytes · 3.6% of section data
MD5 9de7d7abeeb31e9592482e03dac32c89
.reloc 7680 bytes · 6.0% of section data
MD5 faffba8070a02148880b0fba2a324774

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 243ef83f01d32715eb56bb5455ceb938.
  • 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.