
Ibrahim Saud
@tektrixIndiaCompletionist
2 followers18,458 downloads7,120 copies47 likes38,601 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
This rule detects potential email spoofing attempts where an email claims to originate from a specific domain ('gasparinutrition.com') or is intended for external recipients, but fails critical authentication checks. Specifically, it identifies emails with DMARC failure, SPF failure, and a suspicious DKIM signing domain associated with 'gappssmtp.com', indicating an attempt to bypass sender authentication mechanisms.
Detects the LegionLoader infection chain, specifically identifying the use of dllhost.exe as a proxy to load malicious .cpl files or COM objects (e.g., COpenControlPanel) from AppData\Roaming. This rule correlates an initial msiexec.exe MSI staging event with the subsequent dllhost.exe execution and its child process spawn behavior within a 30-minute window.
Detects behavior indicative of LegionLoader where an unsigned process spawned by msiexec.exe or cmd.exe from the AppData\Roaming directory dynamically loads system DLLs (ntdll.dll, kernel32.dll, etc.) followed immediately by API function resolution via GetProcAddress. This sequence is a common technique used by malware to obfuscate function imports, evade static analysis, and hide malicious functionality.
This rule detects the creation of a 'mcp.json' configuration file within an '.amazonq' directory shortly after version control system operations such as 'git clone', 'git pull', 'npm install', or 'pip install'. This activity may indicate an attempt to configure or persist unauthorized developer tools or malicious assistant configurations within a development environment.
This rule detects potentially suspicious host reconnaissance activities by monitoring for frequent execution of system information gathering utilities (reg.exe, wmic.exe, systeminfo.exe) or registry queries against HKLM software hives. It identifies users or hosts performing an anomalous volume of these activities, which is often indicative of post-exploitation discovery efforts.
This rule detects the presence of a specific malicious Chrome extension ID (flkebkiofojicogddingbdmcmkpbplcd) in process command lines or file paths on Windows endpoints, originating from browser processes such as Chrome, Edge, or Brave.
Detects the execution of 'aws sts get-caller-identity' by common IDEs or code editor helper processes. This activity is often used by adversaries to verify the current AWS identity and permissions after gaining access to a developer's workstation.
Detects the use of Node.js package managers (npm, node, npx) to execute 'install' commands in conjunction with the creation of specific Model Context Protocol (MCP) configuration files (.vscode/mcp.json, .amazonq/mcp.json, or .cursor/mcp.json). This pattern may indicate the installation of potentially untrusted or malicious development extensions or AI-assistant integrations within common development environments.
This rule detects processes running from suspicious temporary directories (AppData, Temp, LocalAppData, TCC) initiating frequent outbound network connections to a specific non-standard destination port (18848). This behavior is often indicative of automated Command and Control (C2) heartbeats or beacons, particularly when associated with binaries executing from untrusted or user-writeable locations.
Detects the execution of Lua interpreter binaries (LuaJit or lua) spawned from a specific process named 'HFY.exe', which is associated with the BeepRAT dropper. The rule also correlates this execution with suspicious raw disk read activity to identify potential in-memory payload loading or malicious interaction with system files.
Page 840 of 1168
