Windows File Creation of TeamViewer_Desktop.exe During Install

Alerts on Windows when TeamViewer_Desktop.exe is created, indicating potential installation or dropped remote-access binaries.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-01-28
Updated
2026-07-31

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule identifies creation of the TeamViewer_Desktop.exe file on Windows by matching file creation events where the target filename ends with \TeamViewer_Desktop.exe. Attackers may install remote access or support tooling to enable command-and-control or remote interaction. The detection relies on Windows file creation telemetry that records the target file path and name.

Related detections9 linkedT1219 — drag to rearrange
Possible AnyDesk RMM Silent MSI Installation via Windows Installer (via process_creation)
macOS Process Creation: MeshAgent Remote Access via --meshServiceName
Windows MeshAgent Remote Access Tool Command Line Execution Indicators
Windows Process Creation: Microsoft QuickAssist.exe Execution
Windows MeshAgent remote command execution via cmd.exe or PowerShell child processes
Windows Incoming AnyDesk Connection via AnyDesk.exe or AnyDeskMSI.exe
Windows File Drop Indicators for RemoteKrbRelay SMB Relay Secret Dump Module
Windows DNS Queries to azurewebsites.net From Non-Browser Processes
Windows CSharp Streamer RAT Potentially Loaded .NET Executable from Temp dat####.tmp
Windows File Creation of TeamViewer_Desktop.exe During Install
Pivot detection · T1219 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.