Detections

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

14 detections

This rule detects attempts to establish persistence by modifying specific registry keys known to be used for auto-starting applications or malicious code. It specifically monitors for changes to 'AppInit_DLLs', 'LSAProviders', 'SecurityProviders', and 'WinlogonNotifyPackages' within Security Event ID 4657 (A registry value was modified).
avatar
Ankit Mehta@Secvyn
avatar
Detections.ai Community
4 months ago
006
This rule detects attempts to establish persistence by modifying specific registry keys known to be used for auto-starting applications or malicious code. It specifically monitors for changes to 'AppInit_DLLs', 'LSAProviders', 'SecurityProviders', and 'WinlogonNotifyPackages' within Security Event ID 4657 (A registry value was modified).
avatar
Ankit Mehta@Secvyn
Bharat Cyber Guardians
4 months ago
005
Detects registration of malicious SSP DLLs for credential interception
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
5 months ago
002
This rule detects network traffic on TCP port 445 (SMB) containing the string "Security Packages" in a case-insensitive manner. This pattern is often associated with the registration or use of Security Support Provider DLLs, which can be a persistence mechanism (T1547.005) used by adversaries to maintain access to a system.
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
5 months ago
001
Detects the addition of a SSP to the registry. Upon a reboot or API call, SSP DLLs gain access to encrypted and plaintext passwords stored in Windows.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
7 months ago
000
Detects the addition of a Security Support Provider (SSP) to the Windows registry. When an SSP DLL is loaded into the Local Security Authority (LSA) process, typically upon system reboot or via an API call, it gains access to encrypted and plaintext passwords stored in Windows. This technique is often used for persistence and credential access.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
1 year ago
1144
KQL Query from file: Azure AI Security Finding Report
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
4079
KQL Query from file: Critical Monitor for Critical Assets
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
4072
KQL Query from file: Tracking The Most Dangerous Entra Admin Role
avatar
Steven Lim@KQLWizard
avatar
SlimKQL
1 year ago
3066
Detects the addition of a SSP to the registry. Upon a reboot or API call, SSP DLLs gain access to encrypted and plaintext passwords stored in Windows.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0035
Detects the addition of a SSP to the registry. Upon a reboot or API call, SSP DLLs gain access to encrypted and plaintext passwords stored in Windows.
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0016
The following query surface network activity associated with exploitation of CVE-2022-22965.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0018
The following analytic identifies command-line activity querying the registry for Security Support Providers (SSPs) related to Local Security Authority (LSA) protection and configuration. This detection leverages Endpoint Detection and Response (EDR) telemetry, focusing on processes accessing specific LSA registry paths. Monitoring this activity is crucial as adversaries and post-exploitation tools like winpeas may use it to gather information on LSA protections, potentially leading to credential theft. If confirmed malicious, attackers could exploit this to scrape password hashes or plaintext passwords from memory, significantly compromising system security.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0036
Detects when an attacker modifies the "REG_MULTI_SZ" value named "Extensions" to include a custom DLL to achieve persistence via lsass. The "Extensions" list contains filenames of DLLs being automatically loaded by lsass.exe. Each DLL has its InitializeLsaExtension() method called after loading.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0014