GridinSoft Threat Intelligence

chrome_proxy.exe threat report

Detected as PUP.WebCompanion File reputation report
MD5 3a6b79eb0f303605437f87cfd10aa7a7
Latest seen 2026-02-27 23:00:34 (3 months ago)
First seen 2026-02-27 23:00:34 (3 months ago)
Size 875 KB
Publisher Lavasoft Inc.

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as PUP.WebCompanion. 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
PUP.WebCompanion
Recommended action
Scan and remove
Last analysis
2026-02-27 23:00:34 (3 months ago)
File hash
3a6b79eb0f303605437f87cfd10aa7a7
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as PUP.WebCompanion, part of the PUP threat category.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2026-02-27 23:00:34 (3 months ago); latest analysis 2026-02-27 23:00:34 (3 months ago).

Publisher context

Company metadata: Lavasoft Inc.. Product metadata: Lavasoft quicklaunch browser.

Digital signature

Signed by Lavasoft Software Canada Inc.. The signature is reported as valid, but signed files can still be bundled or abused.

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

chrome_proxy.exe is a Windows file recorded in the ThreatInfo database. It is associated with Lavasoft quicklaunch browser. The reported company name is Lavasoft Inc.. The current detection status is PUP.WebCompanion, based on the latest analysis from 2026-02-27 23:00:34 (3 months ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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 PUP.WebCompanion.

Product Name: Lavasoft quicklaunch browser
Company Name: Lavasoft Inc.
MD5: 3a6b79eb0f303605437f87cfd10aa7a7
Size: 875 KB
First Published: 2026-02-27 23:00:34 (3 months ago)
Latest Published: 2026-02-27 23:00:34 (3 months ago)
Status: PUP.WebCompanion (on last analysis)
Analysis Date: 2026-02-27 23:00:34 (3 months 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: Lavasoft Software Canada Inc.
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%\lavasoft\quick launch\quicklaunch browser

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.

Windows 10 100.0%

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

chrome_proxy.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 0x0007f050
Image base 0x0000000140000000

PE Sections:

Sections 10
Raw data 884224

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

.text 680448 bytes · 77.0% of section data
MD5 00df8f26fd2d8859a478eac5e666228f
.rdata 131072 bytes · 14.8% of section data
MD5 8d97ce7d7db6bcc48a8690de0313550b
.data 37888 bytes · 4.3% of section data
MD5 a8f0396fc4ea3586da78ca65f84b3a91
.pdata 25600 bytes · 2.9% of section data
MD5 8581f5e8e95df9fcf351afe2d98391dc
.00cfg 512 bytes · 0.1% of section data
Uncommon name
MD5 b519d67ea0e934fd78bf063bfda08dad
.tls 512 bytes · 0.1% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.voltbl 512 bytes · 0.1% of section data
Uncommon name
MD5 38997b5aaf2d65bfc172b1a04e671685
_RDATA 512 bytes · 0.1% of section data
Uncommon name
MD5 de8013e6ea9144c75227cc9190d73aad
.rsrc 2560 bytes · 0.3% of section data
MD5 29af883196ad6583c7d5ed1ce6388559
.reloc 4608 bytes · 0.5% of section data
MD5 d7d3aa682c02dbd40ba8afec01e26a6d

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 PUP.WebCompanion

This report identifies chrome_proxy.exe by MD5 3a6b79eb0f303605437f87cfd10aa7a7. It is part of the PUP 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 3a6b79eb0f303605437f87cfd10aa7a7.
  • 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 PUP category to compare similar reports.