GridinSoft Threat Intelligence

ChromeUpdate.exe threat report

Detected as Ransom.Sabsik File reputation report
MD5 280145832729b23d0ec3a9a46c5fd34b
Latest seen 2023-07-25 23:02:36 (2 years ago)
First seen 2023-07-25 23:01:38 (2 years ago)
Size 4 MB
Publisher Google Update
Product Google LLC
Signed by 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
2023-07-25 23:02:36 (2 years ago)
File hash
280145832729b23d0ec3a9a46c5fd34b
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik, part of the Ransom threat category.

Category context

Ransomware families and files associated with encryption or extortion workflows. Related Ransom reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2023-07-25 23:01:38 (2 years ago); latest analysis 2023-07-25 23:02:36 (2 years ago).

Publisher context

Company metadata: Google Update. Product metadata: Google LLC.

Digital signature

Signed by Google LLC. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.

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. Review the Ransom category for related samples and common context.

ChromeUpdate.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google LLC. The reported company name is Google Update. The current detection status is Ransom.Sabsik, based on the latest analysis from 2023-07-25 23:02:36 (2 years ago). ThreatInfo groups this verdict with Ransom reports for broader family-level investigation.

If ChromeUpdate.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 Update
MD5: 280145832729b23d0ec3a9a46c5fd34b
Size: 4 MB
First Published: 2023-07-25 23:01:38 (2 years ago)
Latest Published: 2023-07-25 23:02:36 (2 years ago)
Status: Ransom.Sabsik (on last analysis)
Analysis Date: 2023-07-25 23:02:36 (2 years ago)
ChromeUpdate.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.

Signed By: Google LLC
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on ChromeUpdate.exe is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

%programfiles%\google
%appdata%

ThreatInfo has observed ChromeUpdate.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 100.0%

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

ChromeUpdate.exe is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x000014b0
Image base 0x0000000140000000

PE Sections:

Sections 11
Raw data 4713984

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

.text 108544 bytes · 2.3% of section data
MD5 291d7a78255441dd090dc5c673b179ae
.data 4558848 bytes · 96.7% of section data
MD5 9358892a448df253cab1d5322d260655
.rdata 20480 bytes · 0.4% of section data
MD5 e0dfd80300a0b5e9c56ae02204737a53
.pdata 4608 bytes · 0.1% of section data
MD5 194ff9132f2b98a28e3873b9e29275f2
.xdata 4096 bytes · 0.1% of section data
Uncommon name
MD5 d1f85e50393d213c9eeaf9e367d3218f
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 3072 bytes · 0.1% of section data
MD5 cbce3c83c0d13138a02f42bee32c4f46
.CRT 512 bytes · 0.0% of section data
MD5 0c9760c4bd947df2021ed11554f136b3
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 12288 bytes · 0.3% of section data
MD5 d269c3d7769f6cef8cb65d94c1a8d89e
.reloc 1024 bytes · 0.0% of section data
MD5 651b2684cf7b60a80c8f04d64d742eb6

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

GridinSoft detects this file as Ransom.Sabsik

This report identifies ChromeUpdate.exe by MD5 280145832729b23d0ec3a9a46c5fd34b. It is part of the Ransom report group. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 280145832729b23d0ec3a9a46c5fd34b.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found. Use the Ransom category to compare similar reports.