Detections

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

8,395 detections

Detects the usage of the 'usermod' command to add a user to either the 'root' or 'sudoers' group on a Linux system. This activity can indicate privilege escalation or persistence mechanisms by an attacker.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1025
Detects the execution of the 'jamf' binary with specific commands that could be used by attackers for privilege escalation, bypassing security controls, or modifying system configurations. This includes creating user accounts, managing the JAMF framework, removing MDM profiles, resetting passwords, and setting computer names.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1025
Detects BGP failures which may be indicative of brute force attacks to manipulate routing.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0025
This rule detects the creation or modification of AppX packages in suspicious file system locations. Adversaries may place malicious AppX packages in common temporary or public directories to evade detection or achieve persistence. The rule specifically looks for Event ID 854 from the 'appxdeployment-server' service, indicating an AppX package being added to the processing pipeline, and checks if the package's path contains known suspicious locations such as public user directories, temporary folders, or desktop/downloads folders.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0025
Detects suspicious WMI event filter and command line event consumer creation or modification based on WMI and Security Logs. This rule specifically looks for EventID 5861 (WMI filter to consumer binding) and EventID 5859 (WMI filter registration) in conjunction with common consumer keywords like 'ActiveScriptEventConsumer' and 'CommandLineEventConsumer'. It excludes legitimate SCM Event Provider activity.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
2025
This rule detects when a driver is loaded from a temporary directory. Adversaries may load malicious drivers from temporary locations as part of persistence, privilege escalation, or defense evasion techniques. Loading drivers from temporary directories is often an unusual behavior for legitimate system operations and can indicate suspicious activity.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0025
This rule detects the creation of executable files with suspicious names or extensions. Specifically, it looks for files ending with '.exe' that are appended to common system directory names (e.g., ':\$Recycle.Bin.exe', ':\MSOCache.exe') or other executable extensions (e.g., '.bat.exe', '.sys.exe'). This pattern is often used in unquoted service path vulnerabilities or to masquerade malicious executables as legitimate system files.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0025
This rule detects the creation of specific files that indicate interactive PowerShell usage within the SYSTEM user context. The rule looks for the creation of 'ConsoleHost_history.txt' or 'StartupProfileData-Interactive' files in the 'C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\' or 'C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\PowerShell\' directories respectively. The presence of these files in the SYSTEM profile suggests that PowerShell was used interactively by the SYSTEM account, which is highly unusual and could indicate privilege escalation or malicious activity.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0025
Detects execution of the "mofcomp" utility as a child of a suspicious shell or script running utility or by having a suspicious path in the commandline. The "mofcomp" utility parses a file containing MOF statements and adds the classes and class instances defined in the file to the WMI repository. Attackers abuse this utility to install malicious MOF scripts.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0025
Detects the registration of a debugger for a program that is available in the logon screen, commonly known as a sticky key backdoor. This technique involves modifying the Image File Execution Options (IFEO) registry key to launch an arbitrary executable (debugger) when a legitimate accessibility program (like sethc.exe or utilman.exe) is invoked from the logon screen. This can be used for persistence and privilege escalation to gain SYSTEM privileges.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0025
Detects the execution of the 'execve_hijack' component of the Triple Cross eBPF rootkit. This specific file is used by the rootkit to elevate privileges by hijacking the 'execve' system call, often in conjunction with the 'sudo' command.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
2024
Detects the loading of a kernel driver that has been revoked by Code Integrity. This indicates an attempt to load a driver that is no longer trusted, potentially for malicious purposes or due to a known vulnerability. Event ID 3021 signifies a revoked driver load, while 3022 indicates a revoked driver load allowed due to a kernel mode debugger being attached.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0024
This rule detects attempts to load an image (e.g., a DLL or executable) that has been blocked by Windows Code Integrity because its signing certificate has been revoked. This indicates that a potentially malicious or untrusted module is trying to execute on the system, and the operating system's integrity checks are preventing it.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0024
Detects a threat actor creating a file named `wbemcomn.dll` in the `C:\Windows\System32\wbem\` directory over the network for a WMI DLL Hijack scenario. This is identified by monitoring Windows Security Event ID 5145 for file creations ending with `\wbem\wbemcomn.dll` and filtering out legitimate system accounts (those ending with '$').
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
2024
Detects the creation of a service named 'ZzNetSvc' which is associated with the Moriya rootkit, as described in the 'Operation TunnelSnake' report by Securelist. This rule specifically looks for Event ID 7045 from the 'Service Control Manager' provider, indicating a service installation.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1024
Detects when adversaries delete important scheduled tasks related to system restore, Windows Defender, BitLocker, Windows Backup, Windows Update, Update Orchestrator, or Exploit Guard. This activity could indicate an attempt to disrupt system services or processes, potentially as a precursor to data destructive activities or to hinder defensive capabilities.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0024
This rule detects PowerShell scripts attempting to use specific Windows API functions that are commonly associated with malicious activities such as process injection (VirtualAlloc, OpenProcess, WriteProcessMemory, CreateRemoteThread), token manipulation (OpenProcessToken, LookupPrivilegeValue, AdjustTokenPrivileges, DuplicateTokenEx), and memory operations (ReadProcessMemory, VirtualFree). Detection relies on PowerShell Script Block Logging being enabled to capture the script content.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0024
Detects changes to the "AutodialDLL" registry key, which can be used as a persistence method to load custom DLLs via the "ws2_32" library. This technique allows an attacker to execute malicious code every time a process loads the Winsock2 library.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1024
This rule detects suspicious behaviors associated with the SOURGUM actor, as tracked by Microsoft. Specifically, it looks for the creation of processes with specific image paths related to 'Physmem.sys' or 'WimBootConfigurations.ini' within IME directories. Additionally, it identifies attempts to modify registry keys associated with Component Object Model (COM) objects, specifically InprocServer32 entries for CLSIDs {7c857801-7381-11cf-884d-00aa004b2e24} and {cf4cc405-e2c5-4ddd-b3ce-5e7582d8c9fa}, using the 'reg add' command.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0023
Detects the creation, deletion, or update of AWS Glue Development Endpoints. This activity can be indicative of privilege escalation attempts or unauthorized resource manipulation within an AWS environment, as development endpoints provide an interactive environment for data processing.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1023
Rule to detect the use of the SCX RunAsProvider Invoke_ExecuteShellCommand to execute any UNIX/Linux command using the /bin/sh shell. SCXcore, started as the Microsoft Operations Manager UNIX/Linux Agent, is now used in a host of products including Microsoft Operations Manager, Microsoft Azure, and Microsoft Operations Management Suite. This activity is indicative of the OMIGOD vulnerability exploitation.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1023
Page 388 of 400