Ceplin Command Identifier

Identifier / Programs / Windows

applaunch.exe

Microsoft .NET ClickOnce Launch Utility file version info (xCyclopedia)

LOLBAS AWL Bypass 1 ATT&CK technique 1 documented command 4 known copies with hashes

Opens the identifier with your command. It is read in your browser and sent nowhere.

How applaunch.exe is abused

documented by LOLBAS

AWL Bypass T1127.002 Trusted Developer Utilities Proxy Execution: ClickOnce

-activate

Each abuse is LOLBAS's category and the options and words it uses; the full write-up is on LOLBAS's page for applaunch.exe.

1 documented command

from LOLBAS, each read by the identifier

AWL Bypass T1127.002 Trusted Developer Utilities Proxy Execution: ClickOnce User privileges

Launches a ClickOnce application via Applaunch.exe. Bypasses SmartScreen and default AppLocker rules when the application is published as partial trust.

"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Applaunch.exe" /activate "{REMOTEURL}#APPLICATION_METADATA_HERE"
Identify

The command the identifier reads trips no Sigma process-creation rule. These commands and their descriptions are from LOLBAS’s entry for applaunch.exe, by Nathan Sawyer, 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 applaunch.exe. The identifier reads it 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

Sigma process creation rules
T1127.002Trusted Developer Utilities Proxy Execution: ClickOnce

Is it the real applaunch.exe?

file version info and known copies
Installed inC:\Windows\Microsoft.NET\Framework64\v4.0.30319\
C:\Windows\Microsoft.NET\Framework\v4.0.30319\
Signed byMicrosoft Windows
ProductMicrosoft .NET Framework, Microsoft Corporation
DescriptionMicrosoft .NET ClickOnce Launch Utility

4 known copies

4.8.4161.0 built by: NET48REL1 · C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe · signed by Microsoft Windows

1830afacaa1f2cee9cb28918f9a0163e39f47b527b2cbaf62edbda54d6a8ac28

4.8.4161.0 built by: NET48REL1 · C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\AppLaunch.exe · signed by Microsoft Windows

e759747d776ab3a306291617a47e8c7e8828441905560081028b95d84f2d24db

4.8.4084.0 built by: NET48REL1 · C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AppLaunch.exe · signed by Microsoft Windows

3682f6c9357e653150b1b7a96c30347e1abfa368a356db7c65a4c805f4eeb25e

4.8.4084.0 built by: NET48REL1 · C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe · signed by Microsoft Windows

dc5ac8d4d6d5b230ab73415c80439b4da77da1cfde18214ef601897f661abdac

From 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.