Identifier / Programs / Windows
teams.exe
LOLBAS Execute 5 Sigma rules name it 2 ATT&CK techniques 3 documented commands
How teams.exe is abused
Execute T1218.015 System Binary Proxy Execution: Electron Applications
--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 teams.exe.
3 documented commands
Execute T1218.015 System Binary Proxy Execution: Electron Applications User privileges
Generate JavaScript payload and package.json, and save to "%LOCALAPPDATA%\\Microsoft\\Teams\\current\\app\\" before executing.
teams.exeTrips no Sigma process-creation rule.
Execute T1218.015 System Binary Proxy Execution: Electron Applications User privileges
Generate JavaScript payload and package.json, archive in ASAR file and save to "%LOCALAPPDATA%\\Microsoft\\Teams\\current\\app.asar" before executing.
teams.exeTrips no Sigma process-creation rule.
Execute T1218.015 System Binary Proxy Execution: Electron Applications User privileges
Teams spawns cmd.exe as a child process of teams.exe and executes the ping command
teams.exe --disable-gpu-sandbox --gpu-launcher="{CMD} &&"Trips 1 Sigma rule: mediumPotentially Suspicious Electron Application CommandLine by frack113, Nasreddine Bencherchali (Nextron Systems)
1 of the 3 commands the identifier reads trips a Sigma process-creation rule; 2 trip none. These commands and their descriptions are from LOLBAS’s entry for teams.exe, by Andrew Kisliakov, 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 teams.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.