GridinSoft Threat Intelligence

chrome_proxy.exe file report

Under review File reputation report
MD5 3a1d53250367caf5ce9cde182dfd8835
Latest seen 2026-02-04 23:01:28 (3 months ago)
First seen 2026-02-04 23:01:28 (3 months ago)
Size 688 KB
Publisher OneLaunch
Product OneLaunch

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-02-04 23:01:28 (3 months ago); latest analysis 2026-02-04 23:01:28 (3 months ago).

Publisher context

Company metadata: OneLaunch. Product metadata: OneLaunch.

Digital signature

Signed by ONELAUNCH TECHNOLOGIES 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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

chrome_proxy.exe is a Windows file recorded in the ThreatInfo database. It is associated with OneLaunch. The reported company name is OneLaunch. The current detection status is Undefined, based on the latest analysis from 2026-02-04 23:01:28 (3 months ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: OneLaunch
Company Name: OneLaunch
MD5: 3a1d53250367caf5ce9cde182dfd8835
Size: 688 KB
First Published: 2026-02-04 23:01:28 (3 months ago)
Latest Published: 2026-02-04 23:01:28 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-04 23:01:28 (3 months ago)
Signed By: ONELAUNCH TECHNOLOGIES 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.

%localappdata%\onelaunch\5.31.4

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 32-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 32-bit
Subsystem Windows GUI
Entry point 0x00065a80
Image base 0x00400000

PE Sections:

Sections 7
Raw data 699904

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

.text 562688 bytes · 80.4% of section data
MD5 61b9cf975f9abc27c060d2c3ae6f5897
.rdata 95232 bytes · 13.6% of section data
MD5 de41c5f137c30f5aedf8b692e9f72411
.data 12800 bytes · 1.8% of section data
MD5 2a3535f834c66f772f761013d1e144d2
.00cfg 512 bytes · 0.1% of section data
Uncommon name
MD5 e82b2a0711cce57f4d70fb0dda1cb7d3
.tls 512 bytes · 0.1% of section data
MD5 a101d9e5de6b38f727fa072684c28862
.rsrc 2560 bytes · 0.4% of section data
MD5 f54f36e6c55e0fb1450088bb8ccf97c7
.reloc 25600 bytes · 3.7% of section data
MD5 a6433177e776a710fa9ebdfb3f7db728

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

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 3a1d53250367caf5ce9cde182dfd8835.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.