vknt.exe threat report

MD5 22f0b237a3da4957d17bb0e8dd5bce3e
Latest seen 2021-03-07 04:29:50 (5 years ago)
First seen 2017-05-21 12:05:57 (8 years ago)
Size 77 KB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as General Threat. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
General Threat
Recommended action
Scan and remove
Last analysis
2021-03-07 04:29:50 (5 years ago)
File hash
22f0b237a3da4957d17bb0e8dd5bce3e
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as General Threat.

Timeline

First seen 2017-05-21 12:05:57 (8 years ago); latest analysis 2021-03-07 04:29:50 (5 years ago).

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

vknt.exe is a Windows file recorded in the ThreatInfo database. The current detection status is General Threat, based on the latest analysis from 2021-03-07 04:29:50 (5 years ago).

If vknt.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as General Threat.

MD5: 22f0b237a3da4957d17bb0e8dd5bce3e
Size: 77 KB
First Published: 2017-05-21 12:05:57 (8 years ago)
Latest Published: 2021-03-07 04:29:50 (5 years ago)
Status: General Threat (on last analysis)
Analysis Date: 2021-03-07 04:29:50 (5 years ago)
vknt.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%programfiles%\vietkey2000
%programfiles%
%programfiles%

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

VKNT.EXE
vknt.exe

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

58.3%
41.7%

The strongest geographic signal for this file is Vietnam with 58.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 7 83.3%
Windows 8.1 8.3%
Windows 10 8.3%

The most common operating system signal for vknt.exe is Windows 7 with 83.3% 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.

vknt.exe is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x00027000

PE Sections:

Name Size of data MD5
pec1 22528 bf4b3794e0e3307953a654f4c3f164e0
.rsrc 50176 2b5ab1550625235eb2370f965a62adbc
.pec 4096 74575d94e896d99a97dfeab008416930
.rsrc 1024 b115ea1628fff31fa0c1d5c7f225fff5

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.

More information: