Google Chrome Web Browser
Chrome-proxy.exe is a dedicated helper process used by Google Chrome to manage network proxy settings, PAC files, and proxy Auto-Config interactions. It runs alongside the main browser to apply, retrieve, and refresh proxy configurations without interrupting tab rendering, enabling Chrome to route traffic according to corporate or user-defined rules.
Chrome-proxy.exe handles Proxy Auto-Config (PAC) lookups, negotiates with proxy servers, and coordinates with chrome.exe to apply per-site or per-profile proxy rules. It isolates proxy logic to improve reliability and security during page loads.
Chrome-proxy.exe is a legitimate component of Google Chrome. When located in the official installation directory and signed by Google LLC, it functions as a proxy-management helper that enables PAC resolution, proxy scripting, and secure routing of browser traffic. Like any system process, it should be monitored if unusual behavior arises, but by itself it is expected in standard Chrome deployments and is not a stand-alone executable for external software.
While chrome-proxy.exe is a normal Chrome component, malware can masquerade under similar names. If the file is outside the Google Chrome installation path or lacks a valid digital signature, it could be malicious. Always verify its location, signature, and behavior. In typical Chrome setups, chrome-proxy.exe usage is stable and non-malicious, but anomalies warrant inspection.
Red Flags: If chrome-proxy.exe is missing from the Chrome installation folder, has an invalid signature, resides in an unexpected path, or consumes excessive network or CPU without Chrome actively using a proxy, treat it as suspicious and investigate with a security tool.
Reasons it's running:
Chrome-proxy.exe is a helper process that manages proxy settings and PAC script resolution for Chrome, enabling correct traffic routing without blocking page loads.
Yes, when located in the official Chrome installation directory and signed by Google LLC, it is a legitimate component; verify location and signature if you suspect issues.
Proxy resolution tasks or network policy checks can run in the background. If there is a problematic PAC script or a misconfigured proxy, it may spike CPU usage.
You can adjust Chrome’s proxy settings to bypass automatic proxy detection or disable per-profile PAC scripts, but some proxies may require it for proper traffic routing.
Check its path (C:\Program Files\Google\Chrome\Application or C:\Program Files (x86)\Google\Chrome\Application), verify a Google LLC signature, and confirm the hash matches Google's release.
Repair or reinstall Google Chrome from the official source. After reinstall, verify the chrome_proxy.exe file is present in the Chrome application folder and properly signed.