January 2024 (30)
Potential Masquerading as Communication Apps
2 rules 3 TTPsAttackers may attempt to evade defenses by masquerading malicious processes as legitimate communication applications such as Slack, WebEx, Teams, Discord, RocketChat, Mattermost, WhatsApp, Zoom, Outlook and Thunderbird.
Potential Persistence via Mandatory User Profile Modification
2 rules 2 TTPsAdversaries may abuse Windows mandatory profiles by dropping a malicious NTUSER.MAN file containing pre-populated persistence-related registry keys to establish persistence, which can evade traditional registry-based monitoring.
Potential Port Monitor or Print Processor Registration Abuse
2 rules 4 TTPsThis rule detects registry modifications indicative of privilege escalation and persistence attempts by adversaries abusing port monitors and print processors to execute malicious DLLs with SYSTEM privileges on Windows systems.
Potential PowerShell Obfuscation via Special Character Overuse
2 rules 3 TTPsThis rule detects PowerShell scripts heavily obfuscated with whitespace and special characters, often used to evade static analysis and AMSI, by identifying scripts with low symbol diversity and a high proportion of whitespace and special characters.
Potential Vcruntime140 DLL Sideloading
2 rules 3 TTPsDetects potential DLL sideloading of vcruntime140.dll, a common C++ runtime library, often used by threat actors like APT29 (via WinELOADER) to load malicious payloads under the guise of legitimate applications, leading to defense evasion, persistence, and privilege escalation.
Potential Windows Error Manager Masquerading
2 rules 1 TTPAdversaries may masquerade malicious processes as legitimate Windows Error Reporting processes (WerFault.exe or Wermgr.exe) to evade detection by establishing network connections without arguments, thus blending into normal system activity.
PowerShell MiniDump Script Detection
2 rules 1 TTPThis brief detects PowerShell scripts that reference MiniDumpWriteDump or full-memory minidump types, potentially used to capture process memory from credential-bearing processes like LSASS.
PowerShell Obfuscation via Character Array Reconstruction
2 rules 1 TTPDetects PowerShell scripts using character array reconstruction to hide commands, URLs, or payloads, evading static analysis and AMSI.
PowerShell Obfuscation via String Concatenation
2 rules 1 TTPThis rule detects PowerShell scripts employing string concatenation to evade static analysis and AMSI by fragmenting keywords or URLs at runtime.
PowerShell P/Invoke API Chain for Process Injection
3 rules 7 TTPsThis brief details detection of PowerShell scripts leveraging P/Invoke API calls to perform process injection, covering techniques like self-injection, remote thread injection, APC injection, thread-context hijacking, process hollowing, section-map injection, reflective DLL loading, and DLL injection.
PowerShell Script with Encryption/Decryption Capabilities
2 rules 3 TTPsPowerShell scripts employing .NET cryptography APIs are used to encrypt data for impact or decrypt payloads for defense evasion.
PowerShell Token Obfuscation via Process Creation
3 rules 1 TTPAdversaries employ token obfuscation techniques within PowerShell commands to evade detection by security tools, leveraging methods such as character insertion, string concatenation, and environment variable manipulation to mask their malicious intent.
PowerShell Used to Disable Windows Defender Security Monitoring
3 rules 1 TTPAttackers are using PowerShell commands with specific Set-MpPreference parameters to disable Windows Defender's real-time behavior monitoring, a common tactic for malware to evade detection and persist on compromised systems.
Print.exe Used to Dump Sensitive Files for Credential Access
2 rules 2 TTPsAttackers are abusing the legitimate Windows Print.exe utility to copy sensitive files like NTDS.DIT and SAM in order to extract credentials, enabling local or remote credential access.
Privileged Identity Management (PIM) Alerting Disabled
2 rules 1 TTPAn adversary disables Privileged Identity Management (PIM) alerts in Azure to evade detection and maintain persistent access with escalated privileges.
Process Created with a Duplicated Token
2 rules 2 TTPsThis rule identifies the creation of a process impersonating the token of another user logon session on Windows, potentially indicating privilege escalation.
PsExec Lateral Movement via Network Connection
2 rules 3 TTPsThe rule identifies the use of PsExec.exe making a network connection, indicative of potential lateral movement by adversaries executing commands with SYSTEM privileges on Windows systems to disable defenses.
pygeoapi Path Traversal Vulnerability in STAC FileSystemProvider
2 rules 1 TTPA path traversal vulnerability exists in pygeoapi versions 0.23.0 to 0.23.2 within the STAC FileSystemProvider plugin, allowing unauthenticated access to directories when deployed without a URL-normalizing proxy.
pygeoapi Unauthenticated SSRF Vulnerability in OGC API - Processes Subscriber
2 rules 1 TTPpygeoapi versions 0.23.0 to 0.23.2 contain an unauthenticated server-side request forgery (SSRF) vulnerability where OGC API process execution requests can use the subscriber object to make requests to internal HTTP services, which is resolved in version 0.23.3 by disabling internal requests by default.
pyp2spec Code Injection Vulnerability
3 rules 1 TTPpyp2spec before 0.14.1 is vulnerable to code injection by writing PyPI package metadata into generated spec files without escaping RPM macro directives, allowing malicious packages to execute arbitrary commands on the build machine.
Raccine Scheduled Task Deletion via Schtasks
2 rulesDetection of adversaries deleting the Raccine Rules Updater scheduled task via `schtasks.exe` to disable the ransomware protection tool, potentially leading to data encryption and loss.
Rare Connection to WebDAV Target via Rundll32
2 rules 2 TTPsThis rule identifies rare connection attempts to a Web Distributed Authoring and Versioning (WebDAV) resource, where attackers may inject WebDAV paths in files opened by a victim to leak NTLM credentials via forced authentication using rundll32.exe.
RDP Enabled via Registry Modification
2 rules 2 TTPsAn adversary may enable Remote Desktop Protocol (RDP) access by modifying the `fDenyTSConnections` registry key, potentially indicating lateral movement preparation or defense evasion.
Registry Persistence via AppCert DLL Modification
2 rules 2 TTPsDetection of registry modifications related to AppCert DLLs, a persistence mechanism where malicious DLLs are loaded by every process using common API functions.
Registry Persistence via AppInit DLL Modification
2 rules 2 TTPsModification of the AppInit DLLs registry keys on Windows systems allows attackers to execute code in every process that loads user32.dll, establishing persistence and potentially escalating privileges.
Regsvr32 Silent and Install Parameter DLL Loading
2 rules 2 TTPsDetection of regsvr32.exe being used with the silent and DLL install parameter to load a DLL, a technique used by RATs like Remcos and njRAT to execute arbitrary code.
Remote File Copy to a Hidden Share
2 rules 3 TTPsThis rule detects remote file copy attempts to hidden network shares, which may indicate lateral movement or data staging activity, by identifying suspicious file copy operations using command-line tools like cmd.exe and powershell.exe focused on hidden share patterns.
Remote File Download via Desktopimgdownldr Utility
3 rules 1 TTPThe desktopimgdownldr utility can be abused to download remote files, potentially bypassing standard download restrictions and acting as an alternative to certutil for malware or tool deployment.
Remote Management Access Launch After MSI Install
2 rulesDetects an MSI installer execution followed by the execution of commonly abused Remote Management Software like ScreenConnect, potentially indicating abuse where an attacker triggers an MSI install then connects via a guest link with a known session key.
Remote Scheduled Task Creation via RPC
2 rules 2 TTPsThe creation of scheduled tasks from a remote source via RPC, where the RpcCallClientLocality and ClientProcessId are 0, indicates potential adversary lateral movement within a Windows environment.