Identifier / Programs / Windows
wfc.exe
Microsoft Windows Workflow Foundation Compiler file version info (xCyclopedia)
LOLBAS AWL Bypass 1 Sigma rule name it 1 ATT&CK technique 1 documented command 1 known copy with hashes
How wfc.exe is abused
AWL Bypass T1127 Trusted Developer Utilities Proxy Execution
Each abuse is LOLBAS's category and the options and words it uses; the full write-up is on LOLBAS's page for wfc.exe.
1 documented command
AWL Bypass T1127 Trusted Developer Utilities Proxy Execution User privileges
Execute arbitrary C# code embedded in a XOML file.
wfc.exe {PATH_ABSOLUTE:.xoml}Trips 1 Sigma rule: mediumUse of Wfc.exe by Christopher Peacock @SecurePeacock, SCYTHE @scythe_io
The command the identifier reads trips a Sigma process-creation rule. These commands and their descriptions are from LOLBAS’s entry for wfc.exe, by Jimmy (@bohops), 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 wfc.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
Is it the real wfc.exe?
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\1 known copy
4.8.4084.0 built by: NET48REL1 · C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\WFC.exe · signed by Microsoft Corporation
8b66ef24a75aefd4392210b3f340fde5d3506ebc4ba1484e4e91e44570b85bfcFrom 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.