GridinSoft Threat Intelligence

kinst.exe file report

Clean record File reputation report
MD5 247030641ed60a19498c9b2c2388a05d
Latest seen 2023-02-20 23:26:17 (3 years ago)
First seen 2023-02-20 23:26:17 (3 years ago)
Size 920 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-02-20 23:26:17 (3 years ago); latest analysis 2023-02-20 23:26:17 (3 years ago).

Publisher context

Company metadata: Kingsoft Corporation. Product metadata: Kingsoft Internet Security.

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.

kinst.exe is a Windows file recorded in the ThreatInfo database. It is associated with Kingsoft Internet Security. The reported company name is Kingsoft Corporation. The current detection status is Clean, based on the latest analysis from 2023-02-20 23:26:17 (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: Kingsoft Internet Security
Company Name: Kingsoft Corporation
MD5: 247030641ed60a19498c9b2c2388a05d
Size: 920 KB
First Published: 2023-02-20 23:26:17 (3 years ago)
Latest Published: 2023-02-20 23:26:17 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-02-20 23:26:17 (3 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.

%localappdata%\liebao\2023116212531379_1

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

kinst.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 0x000635e2
Image base 0x00400000

PE Sections:

Sections 4
Raw data 929792

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

.text 684032 bytes · 73.6% of section data
MD5 d3a6fae4a1c8f432c6286f52186ad510
.rdata 143360 bytes · 15.4% of section data
MD5 8dc1892a17dc3a8864516fea4ad80c41
.data 20480 bytes · 2.2% of section data
MD5 dd72b8bf56c7e0e954f85207caed3d45
.rsrc 81920 bytes · 8.8% of section data
MD5 d45ecccaba5f0fc436fbda514e5cdd66

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 247030641ed60a19498c9b2c2388a05d.
  • 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.