setup.exe threat report

MD5 ba512ff5f12ef339c6058112d52cf477
Latest seen 2024-12-31 23:01:00 (a year ago)
First seen 2024-12-31 23:01:00 (a year ago)
Size 4 MB
Publisher 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 Trojan.Heur!. 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
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2024-12-31 23:01:00 (a year ago)
File hash
ba512ff5f12ef339c6058112d52cf477
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2024-12-31 23:01:00 (a year ago); latest analysis 2024-12-31 23:01:00 (a year ago).

Publisher context

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

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.

setup.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google Chrome Installer. The reported company name is Google LLC. The current detection status is Trojan.Heur!, based on the latest analysis from 2024-12-31 23:01:00 (a year ago).

If setup.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 Trojan.Heur!.

Product Name: Google Chrome Installer
Company Name: Google LLC
MD5: ba512ff5f12ef339c6058112d52cf477
Size: 4 MB
First Published: 2024-12-31 23:01:00 (a year ago)
Latest Published: 2024-12-31 23:01:00 (a year ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-12-31 23:01:00 (a year ago)
setup.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 setup.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.

%sysdrive%\新增資料夾\program files (x86)\google\chrome\application\109.0.5414.120

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

setup.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: 0x0000000140000000
Entry Address: 0x00242950

PE Sections:

Name Size of data MD5
.text 3728384 bce93d449e2baf52009c985180337e9c
.rdata 557056 5fd7d9813b7790d0248d5d793b14ea63
.data 73728 765c0daeedfbe9782d6eb210d35b6bb7
.pdata 107008 8953d8bbf80848066eb793ddba95da72
.00cfg 512 8a1f75338df05ca87db4f663e5cfdb0c
.gxfg 12800 facee5b044282420c9cd1a8f42524f34
.retplne 512 bcec33437cee81632e97175fa62079b7
.rodata 2560 2bba450d4a6430a036ff63f564c6b415
.tls 512 279b7014011437ed8f1293c2bc83ba37
.voltbl 512 78fc150c909a4613fe767a18d69d23a0
CPADinfo 512 60d3ea61d541c9be2e845d2787fb9574
LZMADEC 4608 05e9eab8428a551a281ab278073669fa
_RDATA 512 79408950abddab58e9e1114fc17ca3c7
.rsrc 441344 c1ae26a3820a41abbf3af67c49c045b5
.reloc 14848 d5957cfce05a09b2e0d851855c52bcc8

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: