Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
3,989 detections
Filters
Last updated
All Time
Detection languages
1,774
868
397
195
188
Contributors
1,070
924
756
221
96
Categories
2,448
1,307
1,164
785
713
Platforms
2,415
1,310
658
528
133
Products / Services
1,307
886
808
561
337
MITRE Techniques
18,127
15,648
12,596
8,407
6,231
3,989
CVEs
6
5
5
5
5
IDS Classtypes
564
275
11
8
6
IDS Protocols
537
174
64
64
12
This rule detects outbound network connections from Adobe Reader (AcroRd32.exe) or Adobe Acrobat (Acrobat.exe) processes on Windows platforms to known malicious C2 IP addresses. This activity is indicative of potential compromise, likely stemming from an exploit targeting Adobe products, as observed in a sophisticated zero-day campaign.
Detects user agent and URI paths used by empire agents
Detects direct access to raw pastes in different paste services often used by malware in their second stages to download malicious code in encrypted or encoded form
Telegram API Access
Sigma
Detects suspicious requests to Telegram API without the usual Telegram User-Agent
Detects Bitsadmin connections to IP addresses instead of FQDN names
Detects a potentially suspicious empty user agent strings in proxy log.
Could potentially indicate an uncommon request method.
Could potentially indicate an uncommon request method.
Detects Windows PowerShell Web Access
Detects the execution of malicious artifacts associated with the Sapphire Sleet (UNC1069) Axios npm supply chain attack, including the initial plain-crypto-js setup, specific curl commands posting to C2, and OS-specific second-stage payload executions.
Detects the execution of malicious artifacts associated with the Sapphire Sleet (UNC1069) Axios npm supply chain attack, including the initial plain-crypto-js setup, specific curl commands posting to C2, and OS-specific second-stage payload executions.
This rule detects suspicious network communication patterns indicative of command and control (C2) activity by analyzing the jitter (variability) in connection gaps and byte transfer sizes. It identifies connections with a high number of events, a consistent average gap between connections, and low jitter in both connection timing and data transfer sizes (bytes out and bytes in). This pattern can suggest automated, scheduled communication often associated with C2 channels.
This rule detects DNS requests for domain names that combine Middle Eastern-themed keywords (dubai, emirates, iran, saudi, etisalat) with suspicious or cheap Top-Level Domains (TLDs) such as .top, .cyou, .click, .life, .mom, .sbs, or .xyz. This pattern can indicate potential phishing attempts, malicious infrastructure, or C2 communication attempting to blend in with legitimate traffic by using seemingly relevant but low-cost domains.
This rule detects DNS resolution requests to specific malicious command and control (C2) domains, 'sfrclak.com' and 'callnrwise.com', which have been linked to the 'Axios attack'. Detection of these domains indicates potential compromise and active C2 communication.
Detects suspicious network connections to 'sfrclak.com' on port 8000 or command-line activity involving 'curl' targeting 'packages.npm.org' on port 8000, potentially indicating malicious activity such as malware download or command and control communication. The rule specifically looks for various command-line patterns including 'cmd.exe' with PowerShell scripts, 'python' scripts, or 'com.apple.act.mond' related commands.
Detects network connections to malicious domains, associated IPs, execution of related malicious file hashes, registry persistence, and postinstall script executions related to UNC1069 NPM/Axios supply chain attacks deploying SILKBELL and WAVESHAPER.V2. Categorized into risk-scored scenarios.
Detects network connections to a suspicious Vercel application URL ('vscode-ext-git.vercel.app') combined with file events initiated by command-line shells (cmd.exe, powershell.exe, pwsh.exe) using 'curl' in their command line. This correlation suggests potential ingress tool transfer or data exfiltration attempts.
Detects network communication to IP addresses associated with BRICKSTORM malware operations targeting vSphere environments. These IPs have been observed in active campaigns compromising VMware vCenter and ESXi infrastructure.
Detects network connections to a suspicious Vercel application URL combined with file events initiated by command-line shells (cmd.exe, powershell.exe, pwsh.exe) using 'curl' in their command line. This correlation suggests potential data exfiltration attempts as noted in the linked blog post.
This rule detects unusual network connections from processes to legitimate service endpoints that are commonly abused for Command and Control (C2) activities (LOLC2). It specifically looks for connections to services like Telegram, Slack, Discord, GitHub, Google APIs, Pastebin, Dropbox, and others, originating from processes that are not recognized as legitimate applications for those services, and not from common system processes or standard program file paths. This helps identify potential adversary communication channels masquerading as legitimate traffic.
This detection helps you spot activity linked to TeamPCP LiteLLM PyPI compromise (litellm 1.82.7 / 1.82.8) using the specific indicators in the linked source. It is written to be high confidence by focusing on exact versions, domains, paths, or file fingerprints that were observed in the reporting. A match does not prove a system is compromised by itself, but it is a strong reason to investigate. Confirm the affected host and user, check whether the access was expected, and review nearby activity for follow-on steps like additional downloads, new persistence, or repeated connections. Use the source link to support incident.
This rule detects network connections from devices to known malicious infrastructure, specifically the domain 'sfrclak.com' or the IP address '142.11.206.73'. These indicators are associated with potential compromise or command and control activity.
Detects network connections to a known Sapphire Sleet (APT38) command and control (C2) IP address and port, or DNS resolution requests for a malicious Sapphire Sleet C2 domain. This rule identifies direct communication with infrastructure associated with the Sapphire Sleet threat actor.
Page 160 of 190