Detections

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

368 detections

The following analytic detects attempts to install unsigned MSIX/AppX packages using the -AllowUnsigned parameter. This detection leverages Windows event logs from the AppXDeployment-Server, specifically focusing on EventID 603 which indicates the start of a deployment operation with specific deployment flags. The flag value 8388608 corresponds to the -AllowUnsigned option in PowerShell's Add-AppxPackage cmdlet. This activity is significant as adversaries have been observed leveraging unsigned MSIX packages to deliver malware, bypassing signature verification that would normally protect users from malicious packages. If confirmed malicious, this could allow attackers to execute arbitrary code, establish persistence, or deliver malware while evading traditional detection mechanisms.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0037
This detection identifies the installation of developer-signed MSIX packages that lack Microsoft Store signatures. All malicious MSIX packages observed in recent threat campaigns (including those from FIN7, Zloader/Storm-0569, and FakeBat/Storm-1113) were developer-signed rather than Microsoft Store signed. Microsoft Store apps have specific publisher IDs containing '8wekyb3d8bbwe' or 'cw5n1h2txyewy', while developer-signed packages lack these identifiers. This detection focuses on EventID 855 from the Microsoft-Windows-AppXDeployment-Server/Operational logs, which indicates a completed package installation.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0038
This analytic detects successful MSIX/AppX package installations on Windows systems by monitoring EventID 854 in the Microsoft-Windows-AppXDeployment-Server/Operational log. This event is generated when an MSIX/AppX package has been successfully installed on a system. While most package installations are legitimate, monitoring these events can help identify unauthorized or suspicious package installations, especially when correlated with other events such as unsigned package installations (EventID 603 with Flags=8388608) or full trust package installations (EventID 400 with HasFullTrust=true).
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0031
This hunting query detects user interactions with MSIX packages by monitoring EventCode 171 in the Microsoft-Windows-AppXPackaging/Operational logs. These events are generated when a user clicks on or attempts to interact with an MSIX package, even if the package is not fully installed. This information can be valuable for security teams to identify what MSIX packages users are attempting to open in their environment, which may help detect malicious MSIX packages before they're fully installed. Monitoring these interactions can provide early warning of potential MSIX package abuse, which has been leveraged by threat actors such as FIN7, Zloader (Storm-0569), and FakeBat (Storm-1113).
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0031
The following analytic detects the creation or connection of anonymous pipes for inter-process communication (IPC) within a Windows environment. Anonymous pipes are commonly used by legitimate system processes, services, and applications to transfer data between related processes. However, adversaries frequently abuse anonymous pipes to facilitate stealthy process injection, command-and-control (C2) communication, credential theft, or privilege escalation. This detection monitors for unusual anonymous pipe activity, particularly involving non-system processes, unsigned executables, or unexpected parent-child process relationships. While legitimate use cases exist—such as Windows services, software installers, or security tools—unusual or high-frequency anonymous pipe activity should be investigated for potential malware, persistence mechanisms, or lateral movement techniques.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0045
Detects potential exploitation of Dell ControlVault vulnerabilities (dubbed 'ReVault') by monitoring for related service crashes or the abnormal loading of the `bcmbipdll.dll` module. An attacker with local access can exploit these vulnerabilities for privilege escalation or persistence.
avatar
sumanth markapuarapu@sumanth
avatar
Detections.ai Community
1 year ago
0122
Detects the execution of Sysinternals ADExplorer with the "-snapshot" flag in order to save a local copy of the active directory database. This can be used by attackers to extract data for Bloodhound, usernames for password spraying or use the meta data for social engineering. The snapshot doesn't contain password hashes but there have been cases, where administrators put passwords in the comment field.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
1 year ago
001
The analytic detects potentially suspicious modifications to Windows Audit Policy auditing options registry values. It focuses on changes to specific auditing option values ("CrashOnAuditFail", "FullPrivilegeAuditing", "AuditBaseObjects", "AuditBaseDirectories") within the "HKLM\System\CurrentControlSet\Control\Lsa\" registry key. Such modifications could indicate a threat actor attempting to tamper with audit policy configurations, potentially disabling SACLs (System Access Control Lists) to bypass defenses and facilitate further malicious activities like machine compromise or lateral movement.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
11057
KQL Query from file: Detecting Abuse of Wevtutil.exe in LOLBAS Attacks
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
40103
Detects the invocation of MS SQL transactions that are destructive towards table or database data, such as "DROP TABLE" or "DROP DATABASE".
avatar
Daniel Degasperi@d4ns4n
avatar
Detections.ai Community
1 year ago
2330
This analytic detects modifications to the default Group Policy Objects (GPOs) in an Active Directory environment. It leverages Splunk's Admon to monitor updates to the "Default Domain Policy" and "Default Domain Controllers Policy." This activity is significant because changes to these default GPOs can indicate an adversary with privileged access attempting to gain further control, establish persistence, or deploy malware across multiple hosts. If confirmed malicious, such modifications could lead to widespread policy enforcement changes, unauthorized access, and potential compromise of the entire domain environment.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
1038
The analytic detects the use of PowerShell's Invoke-RestMethod cmdlet to collect geolocation data from ipinfo.io or IP address information from api.ipify.org. This behavior leverages PowerShell Script Block Logging to identify scripts that gather external IP information and potential geolocation data. This activity is significant as it may indicate reconnaissance efforts, where threat actors are attempting to determine the geographical location or network details of a compromised system. While some legitimate software may use these services, this pattern is commonly observed in malware and post-exploitation toolkits like those used by Water Gamayun threat actors.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0031
Detects when the a stored procedure is set or cleared for automatic execution in MSSQL. A stored procedure that is set to automatic execution runs every time an instance of SQL Server is started
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0025
Detects command execution via ScreenConnect RMM
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0016
Detects events generated by user-mode applications when they call the CveEventWrite API when a known vulnerability is trying to be exploited.
MS started using this log in Jan. 2020 with CVE-2020-0601 (a Windows CryptoAPI vulnerability.
Unfortunately, that is about the only instance of CVEs being written to this log.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
1012
Detects the exploitation of Microsoft Exchange vulnerability as described in CVE-2020-0688
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0010
Detects exploitation attempt of CVE-2024-49113 known as LDAP Nightmare, based on "Application Error" log where the faulting application is "lsass.exe" and the faulting module is "WLDAP32.dll".
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0010
Detects backup catalog deletions
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0010
An application has been removed. Check if it is critical.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
1010
Detects successful installation of Atera Remote Monitoring & Management (RMM) agent as recently found to be used by Conti operators
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0010
Detects potentially highly relevant antivirus events in the application log based on known virus signature names and malware keywords.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0010
Page 11 of 18