GoToAssist Temporary File Drop in Windows Temp Directory

Flags creation of GoToAssist Remote Support Expert temp installation artefacts under Windows AppData\Temp.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-02-13
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 the creation of a specific GoToAssist temporary artifact by matching file paths under the Windows user Temp directory associated with “GoToAssist Remote Support Expert.” Attackers may use legitimate remote support software to establish interactive access, and transient installation or support artifacts can appear in user-local temporary locations during setup. It relies on Windows file event telemetry that records the target filename/path so the directory substring can be matched.

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
GoToAssist Temporary File Drop in Windows Temp Directory
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.