Detections

Explore public detection logic contributed by the community across SIEM and rule languages.

122 detections

Detects the Skynet malware's specific behavior of dropping and executing a Tor client with unique command-line arguments in the temporary directory.
avatar
Aaron Shelmire@ashelmire
avatar
Detections.ai Community
1 year ago
0121
Detects the use of Tor or Tor-Browser to connect to onion routing networks
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
008

Tor

KQL
This query looks for Tor client, or for a common Tor plugin called Meek.
We query for active Tor connections, but could have alternatively looked for active Tor runs (ProcessCreateEvents) or Tor downloads (DeviceFileEvents).
To read more about this technique, see:.
Tor: https://attack.mitre.org/wiki/Software/S0183#Techniques_Used.
Meek plugin: https://attack.mitre.org/wiki/Software/S0175.
Multi-hop proxy technique: https://attack.mitre.org/wiki/Technique/T1188.
Tags: #Tor, #MultiHopProxy, #CnC.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1040
Detects the use of Tor or Tor-Browser to connect to onion routing networks
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
006
Detects DNS resolution of an .onion address related to Tor routing networks
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
005
Detects DNS queries to an ".onion" address related to Tor routing networks
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
This rule detects when a file, identified as malicious by Google Safe Browsing, initiates an outbound network connection to an IP address known to be a Tor Exit Node, as identified by Google Cloud Threat Intelligence (GCTI) Feed. This indicates potential command and control (C2) communication or data exfiltration by malware attempting to anonymize its network traffic.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0063
This rule detects outbound network connections to known Tor exit nodes. It leverages a Google Cloud Threat Intelligence (GCTI) feed that provides a list of current Tor exit node IP addresses. The rule specifically looks for allowed network connections where the target IP address is identified as a Tor exit node by the GCTI feed. This can indicate an attempt to anonymize network traffic, which is often associated with malicious activity.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
1050
This rule detects when a known 'benign' binary, as identified by the Google Cloud Threat Intelligence (GCTI) Feed, initiates an outbound network connection to an IP address identified as a Tor exit node, also from the GCTI Feed. The rule also increases the risk score if the Tor exit node is located in specific high-risk countries (Cuba, Iran, North Korea, Russia, Syria). This indicates potential malicious activity where an otherwise legitimate program might be compromised or used for covert communication.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0042
This rule detects when a file, identified by its SHA256 hash, initiates a network connection to an IP address that is identified as a Tor exit node. The rule leverages VirusTotal relationships to link the file hash to the contacted IP address and Google Cloud Threat Intelligence (GCTI) Feed to identify Tor exit nodes. The risk score is increased if the Tor IP's geolocation is in certain countries (Cuba, Iran, North Korea, Russia, Syria).
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
1032
Alert traffic destined for known Tor exit nodes
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
001
Alert on known Hash contacting Tor IP with VT Relationships.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
001
Alert on Benign Binary contacting a TOR IP
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
000
A malicious file contacting a known Tor Exit Node.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
000
This rule detects activity associated with the Tor network within an AWS account, as identified by AWS GuardDuty. It specifically looks for GuardDuty findings related to TorIPCaller, TorRelay, or TorClient, indicating potential use of Tor for anonymization or command and control.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
0034
Amazon GuardDuty detects Tor Network activity in an AWS account.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
2 years ago
000
This rule detects the execution of the Tor client or Tor Browser, which are used to connect to the Tor anonymity network. Specifically, it looks for process creation events where the image path ends with '\tor.exe' or '\Tor Browser\Browser\firefox.exe'. This indicates an attempt to establish an anonymous connection, potentially for malicious command and control, data exfiltration, or to bypass network restrictions.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1034
Page 6 of 6