Threat Hunt Report: Unauthorized TOR Usage

Related Project: View Scenario Creation

Tor Browser Threat Hunt

Table of Contents


Platforms and Languages Leveraged

Scenario

Management suspects that some employees may be using TOR browsers to bypass network security controls because recent network logs show unusual encrypted traffic patterns and connections to known TOR entry nodes. Additionally, there have been anonymous reports of employees discussing ways to access restricted sites during work hours. The goal is to detect any TOR usage and analyze related security incidents to mitigate potential risks. If any use of TOR is found, notify management.

High-Level TOR-Related IoC Discovery Plan


Steps Taken

1. Searched the DeviceFileEvents Table

Searched for any file that had the string "tor" in it and discovered what looks like the user "Stefano" downloaded a TOR installer, did something that resulted in many TOR-related files being copied to the desktop, and the creation of a file called Tor Shopping List.txt in Documents at 2026-02-17T15:11:40.544741Z. These events began at 2026-02-17T14:32:44.0801403Z.

View KQL Query: Locate File Events
DeviceFileEvents KQL Results

Figure 1: DeviceFileEvents showing TOR file creation

2. Searched the DeviceProcessEvents Table

Searched for any ProcessCommandLine that contained the string "tor-browser-windows-x86_64-portable-15.0.6.exe". Based on the logs returned, at 2026-02-17T14:40:53.712063Z, an employee on the "stefano-tor-bro" device ran the file tor-browser-windows-x86_64-portable-15.0.6.exe from their Downloads folder, using a command that triggered a silent installation.

View KQL Query: Locate Installation Events
DeviceProcessEvents KQL Results

Figure 2: DeviceProcessEvents showing silent installation

3. Searched the DeviceProcessEvents Table for TOR Browser Execution

Searched for any indication that user "employee" actually opened the TOR browser. There was evidence that they did open it at 2026-02-17T14:46:56.93411Z. There were several other instances of firefox.exe (TOR) as well as tor.exe spawned afterwards.

View KQL Query: Locate Browser Execution
DeviceProcessEvents showing execution

Figure 3: DeviceProcessEvents showing active browser usage

4. Searched the DeviceNetworkEvents Table for TOR Network Connections

Searched for any indication the TOR browser was used to establish a connection using any of the known TOR ports. At 2026-02-17T14:48:32.140446Z, an employee on the "stefano-tor-bro" device successfully established a connection to the remote IP address 164.65.1.77 on port 443. The connection was initiated by the process tor.exe, located in the folder c:\users\stefano\desktop\tor browser\browser\torbrowser\tor\tor.exe. There were a couple of other connections to sites over port 9001.

View KQL Query: Locate Network Connections
DeviceNetworkEvents KQL Results

Figure 4: DeviceNetworkEvents showing external connections


Chronological Event Timeline

1. File Download - TOR Installer

2. Process Execution - TOR Browser Installation

3. Process Execution - TOR Browser Launch

4. Network Connection - TOR Network

5. Additional Network Connections - TOR Browser Activity

6. File Creation - TOR Shopping List


Summary & Response

Summary

The user "stefano" on the "stefano-tor-bro" device initiated and completed the installation of the TOR browser. They proceeded to launch the browser, establish connections within the TOR network, and created various files related to TOR on their desktop, including a file named Tor Shopping List. This sequence of activities indicates that the user actively installed, configured, and used the TOR browser, likely for anonymous browsing purposes, with possible documentation in the form of the "shopping list" file.

Response Taken

TOR usage was confirmed on the endpoint stefano-tor-bro by the user stefano. The device was isolated, and the user's direct manager was notified.