Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
232 detections
Filters
Last updated
All Time
Detection languages
92
81
28
10
8
Contributors
42
40
36
26
17
Categories
110
82
65
31
22
Platforms
87
83
18
17
11
Products / Services
32
28
25
23
21
MITRE Techniques
18,108
15,613
12,573
8,384
6,203
CVEs
6
5
5
3
3
IDS Classtypes
2
IDS Protocols
2
The following analytic detects the execution of fodhelper.exe, which is known to exploit a User Account Control (UAC) bypass by leveraging specific registry keys. The detection method uses Endpoint Detection and Response (EDR) telemetry to identify when fodhelper.exe spawns a child process and accesses the registry keys. This activity is significant because it indicates a potential privilege escalation attempt by an attacker. If confirmed malicious, the attacker could execute commands with elevated privileges, leading to unauthorized system changes and potential full system compromise.
The following analytic detects an Eventvwr UAC bypass by identifying suspicious registry modifications in the path that Eventvwr.msc references upon execution. This detection leverages data from Endpoint Detection and Response (EDR) agents, focusing on registry changes and process execution details. This activity is significant because it indicates a potential privilege escalation attempt, allowing an attacker to execute arbitrary commands with elevated privileges. If confirmed malicious, this could lead to unauthorized code execution, persistence, and further compromise of the affected system.
Detects a non-root user invoking 'busctl call' against the system bus - the core of the
ptrace_may_dream / AccountsService abuse path (CVE-2026-46333 class). Enriched by decoding
the D-Bus call target (service/member), a CallCategory verdict (AccountsService account
modification, systemd run-as-root, polkit, PackageKit, generic mutating call), a burst
counter that surfaces the pidfd_getfd race loop, RiskScore / TriagePriority and DeviceInfo
context. NOTE: the FD-theft primitive itself is invisible to MDE; this detects the busctl
trigger and account-modification aftermath. Detection logic adapted from Elastic Security Labs.
ptrace_may_dream / AccountsService abuse path (CVE-2026-46333 class). Enriched by decoding
the D-Bus call target (service/member), a CallCategory verdict (AccountsService account
modification, systemd run-as-root, polkit, PackageKit, generic mutating call), a burst
counter that surfaces the pidfd_getfd race loop, RiskScore / TriagePriority and DeviceInfo
context. NOTE: the FD-theft primitive itself is invisible to MDE; this detects the busctl
trigger and account-modification aftermath. Detection logic adapted from Elastic Security Labs.
Detects Android malware attempting to abuse accessibility services or system settings to enable wireless debugging and spawn an ADB shell with elevated privileges. This behavior is indicative of unauthorized control over the device via Android Debug Bridge (ADB).
Detects the execution of the suspicious shared library 'liblocal-service.so' from the '/data/local/tmp/' directory, initiated by the 'shell' user or an ADB parent process. This activity is associated with malicious behavior where Android debug bridge (ADB) is abused to stage and execute native daemons for privilege escalation or unauthorized system access.
This rule monitors Android device process events for the execution of 'adb' commands aimed at modifying sensitive system configurations. It specifically tracks attempts to enable accessibility services, toggle wireless debugging, or establish unauthorized ADB pairings. The rule identifies potential malicious intent by aggregating multiple suspicious configuration changes on the same device within a short time window.
Detects unauthorized privilege escalation for AI agent identities within an orchestration platform. The rule triggers when an AI agent account receives an IAM role change, API scope grant, or tool permission update that lacks a corresponding human-approval audit event, or occurs shortly after the agent generates logs indicating potential prompt injection or anomalous behavior.
Detects the creation or modification of Google Cloud Config Connector (KCC) IAM resources (IAMPolicyMember, IAMPartialPolicy, IAMPolicy) that assign high-privilege roles like 'roles/owner' or 'roles/resourcemanager.organizationAdmin'. This monitors for potential privilege escalation where a low-privilege actor leverages the KCC controller's high-privilege service account to perform unauthorized IAM binding changes on Google Cloud resources.
Detects the loading of a known malicious 136KB browser injection helper DLL (SHA256: 75018b06c7105a1dca391805d17b402aed35ebd515b92d461236eafbd606cb40) into Google Chrome or Microsoft Edge processes. The rule further correlates this activity with command line arguments indicative of abusing the browser's elevation service, which is a technique often used for process injection or local privilege escalation.
Detects an accelerated sequence of attack phases—specifically recon, privilege escalation, lateral movement, and persistence—occurring on a single device within a short timeframe (15 minutes). This behavioral pattern indicates potential automated or script-orchestrated intrusion activity.
Detects a specific sequence of Android Debug Bridge (ADB) commands typical of malicious Android agents, specifically those running with elevated privileges (UID 2000/shell/root). The rule identifies combinations of permission grants, battery optimization bypasses, and package tampering (disabling or uninstalling) occurring within the same context.
Detects a specific sequence of Android Debug Bridge (ADB) commands typical of malicious Android agents, specifically those running with elevated privileges (UID 2000/shell/root). The rule identifies combinations of permission grants, battery optimization bypasses, and package tampering (disabling or uninstalling) occurring within the same context.
Detects specific Android device admin command sequences that indicate attempts to establish persistent access by hardening the device against removal (e.g., enabling uninstall protection, setting device admin passwords, disabling biometrics) or destructive actions like performing a factory reset or self-uninstallation.
Detects an accelerated sequence of attack phases—specifically recon, privilege escalation, lateral movement, and persistence—occurring on a single device within a short timeframe (15 minutes). This behavioral pattern indicates potential automated or script-orchestrated intrusion activity.
Detects unauthorized usage of the Android Accessibility Service to navigate system settings, specifically targeting the toggling of developer options and the extraction of 6-digit ADB pairing codes, as observed in the RatHat Android malware.
Detects the loading or execution of pkexec.so, which is indicative of exploitation attempts targeting CVE-2021-4034 (PwnKit). This vulnerability allows for local privilege escalation on Linux systems, including within compromised containers.
Detects anomalous process execution where a non-privileged process spawns a child process with root/SYSTEM (uid 0) privileges without passing through recognized elevation binaries (e.g., sudo, su, pkexec). This behavior is consistent with post-exploitation privilege escalation techniques, such as exploiting hijacked file descriptors or callback structures to gain root authority.
Detects unauthorized shell-level ADB commands characteristic of the RatHat Go Agent, including modifying doze/standby settings, granting security permissions (WRITE_SECURE_SETTINGS), and disabling or uninstalling system packages via the 'pm' command after self-pairing.
Detects a malicious chain of events on Android devices, likely attributed to the RatHat malware, where the 'SystemHelperService' abuses Accessibility Services to programmatically enable Developer Options and Wireless Debugging. It further monitors for the capture of a 6-digit pairing code to facilitate unauthorized local ADB self-pairing.
Detects anomalous ADB commands used by the RatHat Android malware to achieve persistence. This includes adding apps to the battery optimization whitelist, changing application standby buckets to 'active' to bypass background restrictions, disabling specific user-mode applications, or modifying accessibility service configurations.
Detects a malicious browser helper DLL (Rapuncel) that attempts to inject into web browsers like Chrome and Edge. The rule identifies code that interacts with the browser's Elevation Service 'DecryptData' method, a technique used to bypass app-bound encryption, potentially to extract sensitive information like stored credentials.
Page 1 of 12