How to remove chrome_proxy.exe
chrome_proxy.exe
The module chrome_proxy.exe has been detected as PUP.WaveBrowser
chrome_proxy.exe is a Windows file recorded in the ThreatInfo database. It is associated with Wave Browser. The reported company name is The Wave Authors. The current detection status is PUP.WaveBrowser, based on the latest analysis from 2023-07-01 23:16: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 PUP.WaveBrowser.
File Details
| Product Name: | Wave Browser |
| Company Name: | The Wave Authors |
| MD5: | 79e19cdd188164ad5e6512c119c050d9 |
| Size: | 881 KB |
| First Published: | 2023-07-01 23:16:59 (2 years ago) |
| Latest Published: | 2023-07-01 23:16:59 (2 years ago) |
| Status: | PUP.WaveBrowser (on last analysis) | |
| Analysis Date: | 2023-07-01 23:16:59 (2 years ago) |
Common Places:
| %programfiles% |
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.
Geography:
| 100.0% |
The strongest geographic signal for this file is United States with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
| 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.
Analysis
chrome_proxy.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: | 0x00085610 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 707584 | 1f28b544ce99c3e0c3e674c80234636d |
| .rdata | 143360 | 4e9e129857f6f4bec53cade261de9961 |
| .data | 13312 | 80a86a1cc9d8fbf20c661563712a2ea5 |
| .pdata | 27136 | 7266a6dd7b70bba75c5c1a392ae51ee1 |
| .00cfg | 512 | 0ec26a9e629706b86a1b2332a5c6b7e9 |
| .tls | 512 | 1f354d76203061bfdd5a53dae48d5435 |
| .voltbl | 512 | d50fee10662cc21787b3b4f0787cd43f |
| _RDATA | 512 | 73a228b59a6fe5991844344789562440 |
| .rsrc | 2560 | 95a38e44293c5cdad22e7068ab1afd3e |
| .reloc | 5632 | 1387b953f004237c28117510c1ff19ef |
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: