chrome_proxy.exe threat report

MD5 5dd3990201f8e44ad46151e786addd53
Latest seen 2023-08-09 23:11:59 (2 years ago)
First seen 2020-09-21 22:53:23 (5 years ago)
Size 498 KB
Publisher Google Inc.
Product Google Chrome
Signed by Google LLC

This report summarizes the file identity, detection status, publisher metadata, observed locations, and technical indicators for chrome_proxy.exe. ThreatInfo currently classifies this sample as Adware.Yelloader.

GridinSoft Anti-Malware detection

GridinSoft already detects this file

The latest ThreatInfo record shows chrome_proxy.exe detected as Adware.Yelloader. You can download GridinSoft Anti-Malware to scan the system and remove this detection if the file is present on your device.

Detection name
Adware.Yelloader
Last analysis
2023-08-09 23:11:59 (2 years ago)
File hash
5dd3990201f8e44ad46151e786addd53
Download Anti-Malware

chrome_proxy.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google Chrome. The reported company name is Google Inc.. The current detection status is Adware.Yelloader, based on the latest analysis from 2023-08-09 23:11:59 (2 years ago).

If chrome_proxy.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 Adware.Yelloader.

Product Name: Google Chrome
Company Name: Google Inc.
MD5: 5dd3990201f8e44ad46151e786addd53
Size: 498 KB
First Published: 2020-09-21 22:53:23 (5 years ago)
Latest Published: 2023-08-09 23:11:59 (2 years ago)
Status: Adware.Yelloader (on last analysis)
Analysis Date: 2023-08-09 23:11:59 (2 years ago)
chrome_proxy.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: Valid

The signature on chrome_proxy.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%appdata%\view\chrome
%appdata%\view\chrome
%appdata%\view\chrome
%appdata%\view\chrome
%appdata%\view\chrome
%appdata%\view\chrome
%appdata%\view\chrome
%appdata%\view\chrome
%appdata%\view\chrome
%appdata%\view\chrome

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

10.1%
10.1%
9.0%
7.9%
6.7%
6.7%
5.6%
4.5%
4.5%
4.5%
4.5%
3.4%
2.2%
2.2%
2.2%
2.2%
2.2%
2.2%
1.1%
1.1%
1.1%
1.1%
1.1%
1.1%
1.1%
1.1%

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

Windows 10 97.9%
Windows 7 1.0%
Windows 8.1 1.0%

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

chrome_proxy.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: 0x00041a50

PE Sections:

Name Size of data MD5
.text 380928 f9c0a92532907227171dd7d723c96b63
.rdata 93184 0195fb6be52ef7c759e8aa0c424bc5d6
.data 6656 a3dc293d889f106bf29af4d04905a5c8
.00cfg 512 291d56dc833c4f50dc65c027d1163ae9
.tls 512 1f354d76203061bfdd5a53dae48d5435
.voltbl 1024 c87f67ded3753ba835ed5e1f583eddef
.rsrc 2560 a66e08d44ec9a6ee64d5dcb549ff719d
.reloc 16896 df3991bf9a2c8f7e06a0c88e77c89077

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: