Ibrahim Saud
@tektrixIndiaCompletionist
2 followers18,458 downloads7,120 copies47 likes38,562 views
11,679 detections
Filters
Last updated
All Time
Detection languages
3,760
1,874
1,586
966
944
Categories
4,878
3,246
1,529
1,303
1,122
Platforms
7,678
1,824
1,066
999
986
Products / Services
2,963
1,768
1,278
953
798
MITRE Techniques
3,615
3,555
2,488
1,474
1,186
CVEs
36
27
26
25
23
IDS Classtypes
360
113
38
24
24
IDS Protocols
315
114
93
47
10
Detects instances of a force push to a GitHub repository where the commit author and committer names do not match, potentially indicating identity spoofing or tampering within the repository's history.
This rule detects the creation of named pipes commonly used by Cobalt Strike beaconing payloads (e.g., those starting with 'nb_', 'pivot_', or 'beacon_'). The detection excludes known system processes that might otherwise generate similar traffic, focusing on suspicious inter-process communication.
Detects the use of Windows API functions associated with token impersonation, such as ImpersonateLoggedOnUser and DuplicateTokenEx, or the RevertToSelf function, which can be indicators of token theft or privilege escalation attempts by an adversary.
Detects unauthorized modifications to GitHub Actions workflow configuration files (.github/workflows/*.yml) that explicitly enable automated publishing triggers (push to main branch). The rule looks for specific content patterns in the workflow file indicating a push-to-main trigger and monitors for suspicious or known bad commit hashes associated with such changes.
Detects a suspicious sequence of events where a user performs a device-code authentication followed by a device registration or PRT issuance within a 30-minute window. This behavior is indicative of an adversary using an OAuth device code flow to phish an initial access token, subsequently using it to register an adversary-controlled device for persistent access or to bypass Conditional Access policies.
Detects the loading or installation of specific NVIDIA file system filter drivers ('Alinubx.sys', 'CcProtect.sys', 'nvfsflt64.sys') or services related to the 'NvFsFilter'. These drivers are associated with NVIDIA driver components; however, they can be targeted for unauthorized usage or mimicry.
This rule detects anomalous high-frequency search activity within Microsoft 365 environments targeting sensitive keyword terms like 'invoice', 'payment', 'wire', or 'bank.details'. The detection identifies users performing multiple searches across mailbox or graph activity within a short period, which may indicate account compromise or unauthorized email exfiltration attempts.
Detects instances where the Visual Studio Debugger (vsdbg.exe) spawns a child process that is not expected, such as common VS diagnostic tools or standard Microsoft/Windows binaries. This is used to identify potential process injection or abuse of the debugger for executing unauthorized payloads.
This rule detects attempts to bypass Windows User Account Control (UAC) by identifying processes that use specific command-line arguments (such as /Elevation:Administrator, /shell:RunAs, or /runas /savecred) combined with known binaries (such as vsdbg, rundll32, or cmstp) often abused to achieve elevated privileges or proxy execution of malicious code.
This rule detects potential security software tampering by identifying the loading of a specific driver (Alinubx.sys) followed by the termination or interference of common security agent processes within a short timeframe. This behavior is indicative of an adversary attempting to disable endpoint protection using a Bring Your Own Vulnerable Driver (BYOVD) or malicious driver approach.
Page 461 of 1168