Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
105 detections
Filters
Last updated
All Time
Detection languages
50
18
11
8
5
Contributors
26
25
13
10
6
Categories
56
32
31
24
19
Platforms
57
47
6
3
1
Products / Services
29
16
15
11
7
MITRE Techniques
18,116
15,638
12,585
8,395
6,225
CVEs
5
2
2
2
1
IDS Classtypes
1
IDS Protocols
1
Detects unauthorized modifications, creations, or renames of Pluggable Authentication Module (PAM) configuration files or core shared libraries (such as pam_rootok.so or pam_permit.so) by non-root users. Attackers often modify these files to bypass authentication mechanisms and achieve privilege escalation. The rule excludes common package management tools to minimize false positives.
Detects interactive or ad-hoc loading of the SCTP kernel module, which can be indicative of an adversary attempting to gain kernel-level persistence or capabilities. The rule excludes common system-initiated module loads from package managers and system service managers to reduce noise.
Detects interactive or ad-hoc loading of the SCTP kernel module, which can be indicative of an adversary attempting to gain kernel-level persistence or capabilities. The rule excludes common system-initiated module loads from package managers and system service managers to reduce noise.
Detects interactive or ad-hoc loading of the SCTP kernel module, which can be indicative of an adversary attempting to gain kernel-level persistence or capabilities. The rule excludes common system-initiated module loads from package managers and system service managers to reduce noise.
Detects interactive or ad-hoc loading of the SCTP kernel module, which can be indicative of an adversary attempting to gain kernel-level persistence or capabilities. The rule excludes common system-initiated module loads from package managers and system service managers to reduce noise.
This rule detects potential persistence mechanisms in a PostgreSQL database by identifying the creation of a new shared library file (e.g., .so or .dll) within PostgreSQL plugin directories, followed by a modification to the PostgreSQL configuration files (postgresql.conf or postgresql.auto.conf) within a short 30-minute window. This behavior is indicative of an attacker registering a malicious shared library to be loaded upon database startup, a technique associated with PostGREShell-style post-exploitation.
Detects the creation or renaming of files with an 'ELAM' (Early Launch Anti-Malware) naming convention pattern outside of standard system driver directories, performed by processes that are not verified Microsoft-signed binaries. This may indicate an attempt to install or masquerade as a boot-start driver for persistence or subverting security controls.
Detects the creation or renaming of files with an 'ELAM' (Early Launch Anti-Malware) naming convention pattern outside of standard system driver directories, performed by processes that are not verified Microsoft-signed binaries. This may indicate an attempt to install or masquerade as a boot-start driver for persistence or subverting security controls.
Detects potential abuse of Microsoft Defender’s BTR boot-time remediation driver by correlating known driver loads with BootClean.log activity, unexpected loader processes, and driver execution outside normal Defender paths.
Detects the creation or renaming of files with an 'ELAM' (Early Launch Anti-Malware) naming convention pattern outside of standard system driver directories, performed by processes that are not verified Microsoft-signed binaries. This may indicate an attempt to install or masquerade as a boot-start driver for persistence or subverting security controls.
Detects the loading of Linux kernel modules using insmod or modprobe from non-standard, writable directories such as /tmp, /var/tmp, /dev/shm, /home, /root, or /opt. This behavior is highly indicative of an adversary attempting to install a malicious kernel module or rootkit to gain persistence or privilege escalation, while bypassing standard package management paths.
Detects the loading of Linux kernel modules using insmod or modprobe from non-standard, writable directories such as /tmp, /var/tmp, /dev/shm, /home, /root, or /opt. This behavior is highly indicative of an adversary attempting to install a malicious kernel module or rootkit to gain persistence or privilege escalation, while bypassing standard package management paths.
Detects the creation or renaming of files with an 'ELAM' (Early Launch Anti-Malware) naming convention pattern outside of standard system driver directories, performed by processes that are not verified Microsoft-signed binaries. This may indicate an attempt to install or masquerade as a boot-start driver for persistence or subverting security controls.
This rule detects potential persistence mechanisms in a PostgreSQL database by identifying the creation of a new shared library file (e.g., .so or .dll) within PostgreSQL plugin directories, followed by a modification to the PostgreSQL configuration files (postgresql.conf or postgresql.auto.conf) within a short 30-minute window. This behavior is indicative of an attacker registering a malicious shared library to be loaded upon database startup, a technique associated with PostGREShell-style post-exploitation.
This rule detects potential persistence mechanisms in a PostgreSQL database by identifying the creation of a new shared library file (e.g., .so or .dll) within PostgreSQL plugin directories, followed by a modification to the PostgreSQL configuration files (postgresql.conf or postgresql.auto.conf) within a short 30-minute window. This behavior is indicative of an attacker registering a malicious shared library to be loaded upon database startup, a technique associated with PostGREShell-style post-exploitation.
Detects the loading of Linux kernel modules using insmod or modprobe from non-standard, writable directories such as /tmp, /var/tmp, /dev/shm, /home, /root, or /opt. This behavior is highly indicative of an adversary attempting to install a malicious kernel module or rootkit to gain persistence or privilege escalation, while bypassing standard package management paths.
This rule detects potential persistence mechanisms in a PostgreSQL database by identifying the creation of a new shared library file (e.g., .so or .dll) within PostgreSQL plugin directories, followed by a modification to the PostgreSQL configuration files (postgresql.conf or postgresql.auto.conf) within a short 30-minute window. This behavior is indicative of an attacker registering a malicious shared library to be loaded upon database startup, a technique associated with PostGREShell-style post-exploitation.
This rule detects potential persistence mechanisms in a PostgreSQL database by identifying the creation of a new shared library file (e.g., .so or .dll) within PostgreSQL plugin directories, followed by a modification to the PostgreSQL configuration files (postgresql.conf or postgresql.auto.conf) within a short 30-minute window. This behavior is indicative of an attacker registering a malicious shared library to be loaded upon database startup, a technique associated with PostGREShell-style post-exploitation.
Detects the execution of commands containing keywords associated with Linux kernel module management (modprobe) and sensitive memory/kernel modification flags (msr, allow_writes). These keywords are often utilized by malicious actors attempting to load Loadable Kernel Modules (LKMs), manipulate system memory directly, or disable kernel-level protections.
Detects the loading of Linux kernel modules using insmod or modprobe from non-standard, writable directories such as /tmp, /var/tmp, /dev/shm, /home, /root, or /opt. This behavior is highly indicative of an adversary attempting to install a malicious kernel module or rootkit to gain persistence or privilege escalation, while bypassing standard package management paths.
Detects the loading of Linux kernel modules using insmod or modprobe from non-standard, writable directories such as /tmp, /var/tmp, /dev/shm, /home, /root, or /opt. This behavior is highly indicative of an adversary attempting to install a malicious kernel module or rootkit to gain persistence or privilege escalation, while bypassing standard package management paths.
Page 2 of 5