Product
Remote Desktop File Opened from Suspicious Path
2 rules 2 TTPsAdversaries may abuse RDP files delivered via phishing from suspicious locations to gain unauthorized access to systems.
Command Shell Activity Started via RunDLL32
2 rules 4 TTPsThis rule detects command shell activity, such as cmd.exe or powershell.exe, initiated by RunDLL32, a technique commonly abused by attackers to execute malicious code and bypass security controls.
Code Signing Policy Modification Through Built-in Tools
2 rules 1 TTPAttackers may attempt to disable or modify code signing policies on Windows systems by using built-in tools like bcdedit.exe in order to execute unsigned or self-signed malicious code.
Windows Console History Clearing
2 rules 2 TTPsAdversaries may clear the command history of a compromised account to conceal the actions undertaken during an intrusion on a Windows system.
Suspicious Managed Code Hosting Process
2 rules 1 TTPThis rule detects suspicious managed code hosting processes on Windows systems, potentially indicating code injection or defense evasion tactics by monitoring file events associated with processes commonly used to host managed code, such as wscript.exe, cscript.exe, and mshta.exe.
Suspicious Alternate Data Stream (ADS) File Creation
2 rules 1 TTPDetects suspicious creation of Alternate Data Streams (ADS) on targeted files using script or command interpreters, indicative of malware hiding in ADS for defense evasion.
Group Policy Discovery via Microsoft GPResult Utility
2 rules 1 TTPDetects the execution of `gpresult.exe` with arguments `/z`, `/v`, `/r`, or `/x` on Windows systems, which attackers may use during reconnaissance to enumerate Group Policy Objects and identify opportunities for privilege escalation or lateral movement.
Windows Script Execution from Archive File
2 rules 3 TTPsThis rule identifies attempts to execute Jscript/Vbscript files from an archive file, a common delivery method for malicious scripts on Windows systems.
Windows Account Discovery of Administrator Accounts
2 rules 4 TTPsAdversaries may execute the `net.exe` or `wmic.exe` commands to enumerate administrator accounts or groups, both locally and within the domain, to gather information for follow-on actions.
Proxy Execution via Windows OpenSSH Client
2 rulesDetection of command execution via proxy using the Windows OpenSSH client (ssh.exe or sftp.exe) to bypass application control using trusted Windows binaries.
Potential DNS Tunneling via NsLookup
2 rules 2 TTPsDetection of multiple nslookup.exe executions with explicit query types from a single host, potentially indicating command and control activity via DNS tunneling, where attackers abuse DNS for data infiltration or exfiltration.
NullSessionPipe Registry Modification for Lateral Movement
3 rules 2 TTPsAttackers modify the NullSessionPipe registry setting in Windows to enable anonymous access to named pipes, potentially facilitating lateral movement and unauthorized access to network resources.
Execution via Local SxS Shared Module
2 rules 2 TTPsThis rule detects the creation, modification, or deletion of DLL files within Windows SxS local folders, which could indicate an attempt to execute malicious payloads by abusing shared module loading.
Adding Hidden File Attribute via Attrib.exe
2 rules 2 TTPsAdversaries can use attrib.exe to add the 'hidden' attribute to files to hide them from users and evade detection, which can be detected by monitoring process executions related to attrib.exe.
Detecting Execution from Alternate Data Streams
2 rules 1 TTPAdversaries may execute malicious code from Alternate Data Streams (ADS) on Windows to evade defenses by hiding malware within legitimate files, which this detection identifies by monitoring process execution paths and arguments.