vncutil.exe threat report

MD5 e5c80184304e0e74e1ac60b54fd24633
Latest seen 2022-04-23 23:19:07 (4 years ago)
First seen 2022-04-06 23:12:30 (4 years ago)
Size 7 MB
Publisher RtkSmbus.exe

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Ransom.Wacatac. 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
Ransom.Wacatac
Recommended action
Scan and remove
Last analysis
2022-04-23 23:19:07 (4 years ago)
File hash
e5c80184304e0e74e1ac60b54fd24633
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Wacatac.

Timeline

First seen 2022-04-06 23:12:30 (4 years ago); latest analysis 2022-04-23 23:19:07 (4 years ago).

Publisher context

Company metadata: RtkSmbus.exe. Product metadata: © Microsoft Corporation. All rights reserved.

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.

vncutil.exe is a Windows file recorded in the ThreatInfo database. It is associated with © Microsoft Corporation. All rights reserved. The reported company name is RtkSmbus.exe. The current detection status is Ransom.Wacatac, based on the latest analysis from 2022-04-23 23:19:07 (4 years ago).

If vncutil.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 Ransom.Wacatac.

Product Name: © Microsoft Corporation. All rights reserved
Company Name: RtkSmbus.exe
MD5: e5c80184304e0e74e1ac60b54fd24633
Size: 7 MB
First Published: 2022-04-06 23:12:30 (4 years ago)
Latest Published: 2022-04-23 23:19:07 (4 years ago)
Status: Ransom.Wacatac (on last analysis)
Analysis Date: 2022-04-23 23:19:07 (4 years ago)
vncutil.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.

%temp%
%commonappdata%

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

33.3%
33.3%
33.3%

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

Windows 10 66.7%
Windows 7 33.3%

The most common operating system signal for vncutil.exe is Windows 10 with 66.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.

vncutil.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: 0x007f2c2e

.NET Info:

MVID: c01f7f57-a8c4-4ab8-b16f-682c8b7cd4fe
Typelib ID: b84c135b-a8d6-4716-9615-5af0962eb287

PE Sections:

Name Size of data MD5
.text 8326656 be8d43d488fbaee8109d3caedf2d2836
.rsrc 14336 b457e0b3af165668b2d94bee75d366cd
.reloc 512 01fcce776a41366e073fe38a0a695789

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: