Windows__Update.exe threat report

MD5 c8874fc9793e6f4b217ff89171c0db26
Latest seen 2022-08-10 00:00:12 (3 years ago)
First seen 2022-08-05 23:29:42 (3 years ago)
Size 650 KB

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
2022-08-10 00:00:12 (3 years ago)
File hash
c8874fc9793e6f4b217ff89171c0db26
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik.

Timeline

First seen 2022-08-05 23:29:42 (3 years ago); latest analysis 2022-08-10 00:00:12 (3 years ago).

Publisher context

Company metadata: php_fFVqfUgQ06lbsT8C. Product metadata: php_fFVqfUgQ06lbsT8C.

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.

Windows__Update.exe is a Windows file recorded in the ThreatInfo database. It is associated with php_fFVqfUgQ06lbsT8C. The reported company name is php_fFVqfUgQ06lbsT8C. The current detection status is Ransom.Sabsik, based on the latest analysis from 2022-08-10 00:00:12 (3 years ago).

If Windows__Update.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: php_fFVqfUgQ06lbsT8C
Company Name: php_fFVqfUgQ06lbsT8C
MD5: c8874fc9793e6f4b217ff89171c0db26
Size: 650 KB
First Published: 2022-08-05 23:29:42 (3 years ago)
Latest Published: 2022-08-10 00:00:12 (3 years ago)
Status: Ransom.Sabsik (on last analysis)
Analysis Date: 2022-08-10 00:00:12 (3 years ago)
Windows__Update.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%

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

50.0%
50.0%

The strongest geographic signal for this file is Bolivia with 50.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 Windows__Update.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.

Windows__Update.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: 0x00052efe

.NET Info:

MVID: 288dc6ad-7e82-4b26-b785-ad4d679aecce
Typelib ID: c1602b31-709e-4671-a7fa-e3949c0c4312

PE Sections:

Name Size of data MD5
.text 331776 532c77ac71b727b2d5ebb5f36c79b65c
.sdata 1024 5071e524b0504f3f20247398b8fed0b5
.rsrc 331776 362104367f5ffb99c61c6ad8be7ebb2c
.reloc 512 af653b8d97d78ee800a32c9112332477

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: