Detections

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

840 detections

HxTsr.exe is a Microsoft compressed executable file called Microsoft Outlook Communications.
HxTsr.exe is part of Outlook apps, because it resides in a hidden "WindowsApps" subfolder of "C:\Program Files".
Any instances of hxtsr.exe not in this folder may be malware camouflaging itself as HxTsr.exe
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
Detects the presence of unicode characters which are homoglyphs, or identical in appearance, to ASCII letter characters.
This is used as an obfuscation and masquerading techniques. Only "perfect" homoglyphs are included; these are characters that
are indistinguishable from ASCII characters and thus may make excellent candidates for homoglyph attack characters.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
Detects suspicious use of 'calc.exe' with command line parameters or in a suspicious directory, which is likely caused by some PoC or detection evasion.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
Detects the creation of a process via the Windows task manager. This might be an attempt to bypass UAC
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
Detects a CodePage modification using the "mode.com" utility to Russian language.
This behavior has been used by threat actors behind Dharma ransomware.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
Detects suspicious use of XORDump process memory dumping utility
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
Detects a CodePage modification using the "mode.com" utility.
This behavior has been used by threat actors behind Dharma ransomware.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
Detects Windows executables that write files with suspicious extensions
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
004
Finds legitimate system32 or syswow64 executables being run under a different name and in a different location.
The rule will require tuning for your environment.
MITRE: Masquerading https://attack.mitre.org/techniques/T1036.
Get a list of all processes run, except those run from system32 or SysWOW64.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0019
'This query looks for writes of PE files to C:\Windows\System32\spool\drivers\color\.
This is a common directory used by malware, as well as some legitimate programs, and writes of PE files to the folder should be monitored.
Ref: https://www.microsoft.com/security/blog/2022/07/27/untangling-knotweed-european-private-sector-offensive-actor-using-0-day-exploits/'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0011
Identify masqueraded DLLHost.exe file created by PowerShell.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
008
Detects suspicious use of an .exe extension after a non-executable file extension like .pdf.exe, or a set of spaces or underlines to cloak the executable file, often used in spear phishing campaigns to trick users into executing malicious files.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
1 year ago
1020
Correlate process events with hashes that have a low rolling max over the past 10 days
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
302
The following analytic detects processes with names consisting of a single letter, which is often indicative of malware or an attacker attempting to evade detection. This detection leverages data from Endpoint Detection and Response (EDR) agents, focusing on process names and command-line executions. This activity is significant because attackers use such techniques to obscure their presence and carry out malicious activities like data theft or ransomware attacks. If confirmed malicious, this behavior could lead to unauthorized access, data exfiltration, or system compromise. Immediate investigation is required to determine the legitimacy of the process.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0177
This analytic identifies `mmc.exe` spawning a Living Off The Land Binaries and Scripts (LOLBAS) execution process. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process creation events where `mmc.exe` is the parent process. This activity is significant because adversaries can abuse the DCOM protocol and MMC20 COM object to execute malicious code, using Windows native binaries documented by the LOLBAS project. If confirmed malicious, this behavior could indicate lateral movement, allowing attackers to execute code remotely, potentially leading to further compromise and persistence within the environment.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0043
This analytic identifies a Living Off The Land Binaries and Scripts (LOLBAS) process being executed where its process name does not match its original file name attribute. Processes that have been renamed and executed may indicate an adversary attempting to evade defenses or execute malicious code. The LOLBAS project documents Windows native binaries that can be abused by threat actors to perform tasks like executing malicious code. The detection logic specifically looks for process creation events where the `original_file_name` field (which stores the original name of the executable) does not match the `process_name` (the name of the process as it's currently running). It also filters out common system paths and uses a lookup table (`lolbas_file_path`) to identify known LOLBAS binaries.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0043
This rule detects the execution of common debugger tools (x32dbg, x64dbg, windbg) on Windows endpoints. While these tools have legitimate uses for software development and analysis, they are frequently abused by malware, such as PlugX and DarkGate, for malicious purposes like DLL side-loading or code injection. Detecting their presence and execution, especially in environments where they are not typically used by non-technical users, can indicate suspicious activity and potential compromise. This rule is designed to help Security Operations Centers (SOCs) identify such potentially malicious tool usage.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0041
The following analytic identifies instances where explorer.exe is spawned by unusual parent processes such as cmd.exe, powershell.exe, or regsvr32.exe. This detection leverages data from Endpoint Detection and Response (EDR) agents, focusing on process and parent process relationships. This activity is significant because explorer.exe is typically initiated by userinit.exe, and deviations from this norm can indicate code injection or process masquerading attempts by malware like Qakbot. If confirmed malicious, this behavior could allow attackers to execute arbitrary code, evade detection, and maintain persistence within the environment.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0038
The following analytic detects `wmiprvse.exe` spawning a LOLBAS execution process. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process creation events where `wmiprvse.exe` is the parent process and the child process is a known LOLBAS binary. This activity is significant as it may indicate lateral movement or remote code execution by an adversary abusing Windows Management Instrumentation (WMI). If confirmed malicious, this behavior could allow attackers to execute arbitrary code, escalate privileges, or maintain persistence within the environment, posing a severe security risk.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
3036
This analytic identifies the execution of Living Off The Land Binaries and Scripts (LOLBAS) from unexpected file paths. LOLBAS are legitimate Windows binaries that can be abused by threat actors for malicious purposes, such as defense evasion or code execution. The rule specifically looks for processes that are identified as LOLBAS tools but are executed from a directory other than their standard or expected system locations (e.g., outside of Program Files, System32, or SysWOW64). This behavior can indicate an adversary attempting to bypass security controls or execute malicious code in a stealthy manner.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0035
The following analytic detects an anomaly where an svchost.exe process is spawned by a parent process other than the standard services.exe. In a typical Windows environment, svchost.exe is a system process that hosts Windows service DLLs, and is expected to be a child of services.exe. A process deviation from this hierarchy may indicate suspicious behavior, such as malicious code attempting to masquerade as a legitimate system process or evade detection. It is essential to investigate the parent process and associated behavior for further signs of compromise or unauthorized activity.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0033
Page 38 of 40