Detections

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

178 detections

Detects connections with Azure Front Door (known legitimate service that can be leveraged for C2)
that fall outside of known benign behavioral baseline (not using common apps or common azurefd.net endpoints)
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
1030
'CreepyDrive uses OneDrive for command and control, however, it makes regular requests to predicatable paths.
This detecton will alert when over 20 sequences are observed in a single day.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1046
Query 1 shows you any network communication happened from endpoints to a specific Remote IP or Remote URL.
Ensure to update RemoteIP and RemoteURL variable.
For questions @MiladMSFT on Twitter or milad.aslaner@microsoft.com by email.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0024
'CreepyDrive uses OneDrive for command and control. This detection identifies URLs specific to CreepyDrive.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0023
This query finds network communication to specific URL.
Please note that in line #7 it filters RemoteUrl using has operator, which looks for a "whole term" and runs faster.
Example: RemoteUrl has "microsoft" matches "www.microsoft.com" but not "microsoftonline.com".
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1117
This analytic identifies a process making a DNS query to Discord, excluding legitimate Discord application paths. It leverages Sysmon logs with Event ID 22 to detect DNS queries containing "discord" in the QueryName field. This activity is significant because Discord can be abused by adversaries to host and download malicious files, as seen in the WhisperGate campaign. If confirmed malicious, this could indicate malware attempting to download additional payloads from Discord, potentially leading to further code execution and compromise of the affected system.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0034
This rule detects suspicious DNS queries specifically targeting 'api.telegram.org'. This domain is used by Telegram Bot API, which can be leveraged by various types of malware (e.g., RATs, ransomware) for command and control (C2) or data exfiltration. Monitoring these queries helps identify systems potentially communicating with malicious Telegram bots.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
3036
This rule detects suspicious network requests to the Telegram API (api.telegram.org) that do not include a standard 'Telegram' or 'Bot' user-agent string. This behavior is often indicative of malware or custom tools attempting to use Telegram's API for command and control or data exfiltration without revealing their identity as a legitimate Telegram client or bot.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
2027
Detects suspicious DNS queries to api.telegram.org used by Telegram Bots of any kind
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
000
This rule detects the LimeRAT backdoor by identifying specific byte patterns associated with its persistence mechanism, cryptocurrency mining capabilities, downloader functionality, and network communication routines. The rule looks for a combination of these distinct patterns within a file to confirm the presence of LimeRAT.
ReversingLabs Yara@ReversingLabsYara
avatar
ReversingLabs Yara
3 years ago
0033
Page 9 of 9