VirtualDriveModuleSeeting.exe threat report

MD5 cc41b79363bc6f8e9d6bec0720b2403a
Latest seen 2021-12-06 21:59:05 (4 years ago)
First seen 2021-12-06 21:59:05 (4 years ago)
Size 2 MB
Publisher Google Chrome
Product Google LLC

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Ransom.Sabsik. 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.Sabsik
Recommended action
Scan and remove
Last analysis
2021-12-06 21:59:05 (4 years ago)
File hash
cc41b79363bc6f8e9d6bec0720b2403a
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik.

Timeline

First seen 2021-12-06 21:59:05 (4 years ago); latest analysis 2021-12-06 21:59:05 (4 years ago).

Publisher context

Company metadata: Google Chrome. Product metadata: Google LLC.

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.

VirtualDriveModuleSeeting.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google LLC. The reported company name is Google Chrome. The current detection status is Ransom.Sabsik, based on the latest analysis from 2021-12-06 21:59:05 (4 years ago).

If VirtualDriveModuleSeeting.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.Sabsik.

Product Name: Google LLC
Company Name: Google Chrome
MD5: cc41b79363bc6f8e9d6bec0720b2403a
Size: 2 MB
First Published: 2021-12-06 21:59:05 (4 years ago)
Latest Published: 2021-12-06 21:59:05 (4 years ago)
Status: Ransom.Sabsik (on last analysis)
Analysis Date: 2021-12-06 21:59:05 (4 years ago)
VirtualDriveModuleSeeting.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.

%commonappdata%

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

100.0%

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

Windows 10 100.0%

The most common operating system signal for VirtualDriveModuleSeeting.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.

VirtualDriveModuleSeeting.exe is identified as pe for 64 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: 64
Image Base: 0x0000000000400000
Entry Address: 0x00001bea

PE Sections:

Name Size of data MD5
.text 3584 9653ddd57d6f9b204a11ed4137d74935
.rdata 2736128 1c206e155a62592967b1570938067756
.data 512 64c6a5512d4ecfa976f314a3b6da9387
.pdata 512 ab5f1851d977ec07f0fb7f849fc8abbf
.rsrc 1536 24354cd2d941c685bab90090fbbad31b

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: