Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
5,155 detections
Filters
Last updated
All Time
Detection languages
2,301
1,070
640
289
288
Contributors
918
814
769
696
224
Categories
20,456
11,839
5,876
5,155
4,865
Platforms
2,858
2,017
816
524
213
Products / Services
1,336
1,144
831
576
366
MITRE Techniques
1,822
1,307
787
747
577
CVEs
9
7
7
6
6
IDS Classtypes
538
151
101
57
48
IDS Protocols
375
373
132
64
42
This rule monitors for DNS queries and TLS certificate attributes associated with the SilkParasite threat actor. The rule specifically targets domains that impersonate Central Asian government entities and monitors for suspicious TLS certificate issuers and subjects, indicating potential C2 infrastructure or phishing activity.
Detects network communication associated with the SilkParasite campaign. This includes detection of TLS traffic using self-signed LokiDev certificates (CN=localhost, O=LokiDev), direct connections to known malicious C2 IP addresses, and DNS queries for the domain normativ.dushanbeidc.org, which is linked to the LokiDev infrastructure.
Detects network communication associated with the SilkParasite campaign, specifically identifying TLS traffic using fraudulent certificates impersonating the Uzbekistan railway authority (azure.uzrailwaystax.com) and connections to identified malicious infrastructure using specific JA4X TLS fingerprinting.
Detects potential cross-family Command and Control (C2) activity by correlating multiple network infrastructure indicators associated with the SilkParasite threat actor. The rule identifies source hosts that interact with at least two distinct indicator sets (specific malicious domains, shared TLS certificates, or cloned homepage content hashes) within a one-hour timeframe.
This rule monitors for suspicious credential-related activity targeting ONVIF interfaces on network devices (such as IP cameras). It detects a pattern where a successful 'global.login' RPC authentication is quickly followed (within 300 seconds) by commands or RPC methods related to credential dumping or user enumeration (e.g., OnvifUser, GetUsers). This sequence is indicative of an adversary using legitimate access to gain unauthorized information from a device.
Identifies network communication to known malicious infrastructure used by the SilkParasite threat actor. The rule specifically monitors DNS queries and destination connections to subdomains associated with 'hoster-kg.com' and 'tdtu.org', which are linked to the operation of SpiceRAT, NodeEdgeRAT, and NomadRAT malware.
Detects network traffic attempting to impersonate the Uzbekistan railway authority via suspicious TLS certificates. The rules identify specific SNI domains, certificate subjects, and issuers associated with the 'SilkParasite' campaign, which uses Chinese state-affiliated certificate authorities to facilitate C2 communications.
Detects RDP-over-TLS/NLA traffic occurring over non-standard high ports, which is often indicative of C2 communication or lateral movement associated with the SilkParasite infrastructure cluster.
Detects network activity associated with the SilkParasite C2 infrastructure (used by SpiceRAT and NodeEdgeRAT malware). The rule monitors for specific impersonated TLS certificates, known malicious IP addresses, and unique JA4X TLS fingerprints associated with these threat actors.
Detects DNS, TLS SNI, and HTTP Host header requests to known phishing domains mimicking Passkey or Single Sign-On (SSO) authentication services. These domains attempt to deceive users into providing credentials or performing unauthorized authentication actions.
This rule detects repeated HTTP POST requests to a Polygon blockchain endpoint ('eth_call') containing specific contract address and method identifiers. This behavior is indicative of 'EtherHiding', a technique where attackers use blockchain smart contracts to host malicious C2 configurations or update C2 infrastructure, allowing for stealthy dynamic command and control rotation.
Detects activity associated with the 'MovieReaper' threat campaign by identifying known malicious file hashes, command and control (C2) IP addresses, and communication with identified malicious domains. This rule monitors process execution, file operations, and network connections within the campaign's active timeframe.
Detects network traffic where the SilverFox malware relay (api.php) attempts to evade detection by returning a legitimate WeChat installer download link as a decoy response, rather than its intended malicious payload, when communicating with external analysis environments.
This rule detects network connections or DNS queries to known typosquatted and malicious domains associated with the SilverFox campaign. These domains impersonate legitimate software (e.g., SteelSeries GG, Bcut, DeepSeek) to lure users into downloading malware via SEO poisoning and deceptive downloads.
This rule detects activity associated with the 'Ghostcode' threat campaign by monitoring multiple telemetry sources. It identifies connections to known malicious IP addresses and domains, patterns consistent with phishing kit hosting, and specific URL structures used in credential harvesting or payload delivery. The rule correlates sign-in logs, device network events, DNS queries, and email telemetry to identify potential compromise.
This rule monitors network traffic and internal logs for connections to known malicious IP addresses or domain names associated with 'ClickFix' social engineering campaigns (often impersonating services like HBO Max). The logic explicitly filters out known threat intelligence scanners and security researcher probes. It performs correlation by requiring domain/message matches for generic IP-based alerts to reduce noise, and aggregates events per host over 15-minute windows to produce consolidated alerts.
Detects HTTP responses containing JavaScript-based anti-bot challenge pages consistent with the GhostCode toolkit, and subsequent HTTP requests containing tracking tokens used for victim verification after passing the challenge.
This rule monitors for indicators of compromise (IOCs) associated with the Rapuncel/Cruciferra 'Bring Your Own Vulnerable Driver' (BYOVD) malware-as-a-service (MaaS) campaign. It detects malicious file hashes (associated with dropped binaries or drivers), connections to known malicious command-and-control (C2) IP addresses, and network requests to domains used by the infrastructure.
This rule monitors for indicators of compromise (IOCs) associated with the Rapuncel/Cruciferra 'Bring Your Own Vulnerable Driver' (BYOVD) malware-as-a-service (MaaS) campaign. It detects malicious file hashes (associated with dropped binaries or drivers), connections to known malicious command-and-control (C2) IP addresses, and network requests to domains used by the infrastructure.
This rule monitors for indicators of compromise (IOCs) associated with the Rapuncel/Cruciferra 'Bring Your Own Vulnerable Driver' (BYOVD) malware-as-a-service (MaaS) campaign. It detects malicious file hashes (associated with dropped binaries or drivers), connections to known malicious command-and-control (C2) IP addresses, and network requests to domains used by the infrastructure.
Detects network requests targeting specific public Polygon RPC endpoints that query a known smart contract associated with EtherHiding-style C2 activity. This rule monitors for RPC methods (eth_call, eth_getStorageAt) commonly used to retrieve embedded C2 instructions stored within blockchain state data, a technique known as leveraging smart contracts for command-and-control communication.
Page 49 of 246