GridinSoft Threat Intelligence

kinst.exe file report

Clean record File reputation report
MD5 d16bf087c2c84269dd152ccd384f97ec
Latest seen 2021-01-14 18:48:10 (5 years ago)
First seen 2020-07-06 12:55:19 (5 years ago)
Size 899 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-07-06 12:55:19 (5 years ago); latest analysis 2021-01-14 18:48:10 (5 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 2021-01-14 18:48:10 (5 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: d16bf087c2c84269dd152ccd384f97ec
Size: 899 KB
First Published: 2020-07-06 12:55:19 (5 years ago)
Latest Published: 2021-01-14 18:48:10 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-14 18:48:10 (5 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
%localappdata%\liebao
%programfiles%\mydrivers
%commonappdata%
%sysdrive%\kinggsoft\kduu_ba
%temp%

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 85.7%
Windows 7 14.3%

The most common operating system signal for kinst.exe is Windows 10 with 85.7% 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 0x0005e782
Image base 0x00400000

PE Sections:

Sections 4
Raw data 901120

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

.text 659456 bytes · 73.2% of section data
MD5 326560c75dee8611f60da4c91667877e
.rdata 139264 bytes · 15.5% of section data
MD5 2ce30094b00ba5bf70774fb829d5f0ae
.data 20480 bytes · 2.3% of section data
MD5 c07b4d1510365db3c35f9ba6435ab53a
.rsrc 81920 bytes · 9.1% of section data
MD5 18774aab1ab4e5406a11010b546163ea

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