Windows File Writes of TeamViewer Session Logs

Flags Windows file creation events for TeamViewer session log artifacts like vprint.db and TVNetwork.log.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-01-30
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 file creation events involving TeamViewer-specific log and remote printing database paths. Attackers and remote-access tools may generate these artifacts during interactive sessions, making them useful for confirming remote activity or investigation timelines. It relies on Windows file event telemetry capturing target file paths and filenames ending in or containing the specified TeamViewer log/database patterns.

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 Writes of TeamViewer Session Logs
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.