Detections

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

38 detections

This rule detects when critical Windows services or processes associated with Active Directory (NTDS, Netlogon, LSASS, LDAP) or the Print Spooler (Spooler, spoolsv.exe) crash multiple times (3 or more) on a machine within a 7-day period. This could indicate instability, a denial-of-service attempt, or a system compromise affecting core services.
avatar
Ankit Mehta@Secvyn
Bharat Cyber Guardians
4 months ago
003
Detects potential PrintNightmare or Print Spooler exploitation by monitoring for the spoolsv.exe service spawning suspicious child processes (e.g., cmd, powershell, rundll32) and unauthorized files being dropped into the printer driver directory.
avatar
Ankit Mehta@Secvyn
Bharat Cyber Guardians
4 months ago
302
This rule detects when critical Windows services or processes associated with Active Directory (NTDS, Netlogon, LSASS, LDAP) or the Print Spooler (Spooler, spoolsv.exe) crash multiple times (3 or more) on a machine within a 7-day period. This could indicate instability, a denial-of-service attempt, or a system compromise affecting core services.
avatar
Ankit Mehta@Secvyn
Bharat Cyber Guardians
4 months ago
002
Detects suspicious activity related to the Print Spooler service (spoolsv.exe), specifically focusing on the spawning of known command-line interpreters (cmd.exe, powershell.exe, rundll32.exe) by spoolsv.exe, as well as the creation or modification of DLL files within the system print spool drivers directory by processes other than spoolsv.exe. This activity is often associated with privilege escalation and persistence techniques involving print spooler service abuse.
avatar
Ankit Mehta@Secvyn
Bharat Cyber Guardians
4 months ago
002
Detects PrintNightmare print spooler exploitation attempts
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
4 months ago
004
Detects potential PrintNightmare or Print Spooler exploitation by monitoring for the spoolsv.exe service spawning suspicious child processes (e.g., cmd, powershell, rundll32) and unauthorized files being dropped into the printer driver directory.
avatar
Ankit Mehta@Secvyn
avatar
Detections.ai Community
4 months ago
001
Detects suspicious activity related to the Print Spooler service (spoolsv.exe), specifically focusing on the spawning of known command-line interpreters (cmd.exe, powershell.exe, rundll32.exe) by spoolsv.exe, as well as the creation or modification of DLL files within the system print spool drivers directory by processes other than spoolsv.exe. This activity is often associated with privilege escalation and persistence techniques involving print spooler service abuse.
avatar
Ankit Mehta@Secvyn
avatar
Detections.ai Community
4 months ago
000
This rule detects the creation of a file named 'config.dat' within the Windows printer color profile directory (typically 'C:\Windows\System32\spool\drivers\color'). This activity is suspicious because 'config.dat' in this specific location is often targeted by malware, such as the SprySocks backdoor, to maintain persistence or store malicious configurations. Legitimate modifications to this file are rare and usually associated with printer driver installations or manual color profile adjustments, which should be investigated as potential false positives.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
007
This rule detects the creation or modification of a file named 'config.dat' within the Windows print spooler's color driver directory (system32\spool\drivers\color). This activity is considered suspicious when it occurs outside of normal print workflows, as it could indicate malicious manipulation of printer configurations, potentially for persistence or privilege escalation. The rule focuses on capturing causality information to aid in investigation.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
005
Detects the VSPMsg print processor path and DLL name, which is associated with the SprySocks malware for persistence on Windows systems. The rule looks for specific strings related to the DLL name, print processor path, and common installation directories used by this malware.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
004
This rule detects the creation of a file named 'config.dat' within the Windows printer color profile directory (typically 'C:\Windows\System32\spool\drivers\color'). This activity is suspicious because 'config.dat' in this specific location is often targeted by malware, such as the SprySocks backdoor, to maintain persistence or store malicious configurations. Legitimate modifications to this file are rare and usually associated with printer driver installations or manual color profile adjustments, which should be investigated as potential false positives.
avatar
Daniel Jeremiah@daniyyell
Google SecOps
4 months ago
204
This rule targets registry or file artifacts that install 'VSPMsg' as an x64 print processor. It specifically looks for registry modifications where the value name contains 'print processors\vspmsg' and the event subtype or actor process command line contains 'vspmsg.dll'. The XQL view retains actor and causality fields for investigation.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
004
Detects the Print Spooler service (spoolsv.exe) spawning svchost.exe. This behavior is leveraged by the WIN_PLUS variant of SprySOCKS to execute a first-stage print processor loader, which then injects the backdoor into a newly created svchost.exe process.
avatar
Ethan Andrews@eandrews
avatar
Federal Signal Detections
4 months ago
108
Detects registration of malicious port monitor DLLs via print spooler
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
4 months ago
004
This rule detects Portable Executable (PE) files that contain a cluster of API calls commonly associated with process doppelganging techniques, specifically targeting the 'spoolsv.exe' process. The presence of 'NtCreateTransaction', 'CreateFileTransacted', 'NtCreateSection', 'NtCreateProcessEx', and 'NtCreateThreadEx' in conjunction with 'spoolsv.exe' suggests an attempt to inject malicious code into a legitimate process using advanced evasion techniques.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
001
Targets registry or file artefacts that install VSPMsg as an x64 print processor. The UDM rule retains principal and target context for correlation.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
001
Targets registry or file artefacts that install VSPMsg as an x64 print processor. The UDM rule retains principal and target context for correlation.
avatar
Daniel Jeremiah@daniyyell
Google SecOps
4 months ago
301
Detects registration of malicious port monitor DLLs via print spooler
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
4 months ago
002
This rule detects network traffic on TCP port 445 (SMB) containing the case-insensitive string "Print Processors". This pattern is indicative of an attempt to register a malicious Print Processor DLL for persistence, a technique used by adversaries to maintain access to a system. The rule specifically looks for traffic flowing to the home network, suggesting an inbound attempt to establish persistence.
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
5 months ago
005
Detects registration of print processor DLLs for SYSTEM-level persistent code execution
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
5 months ago
002
Detects potential exploitation of CVE-2021-1675 / CVE-2021-34527 (PrintNightmare) via anomalous SMB access to the IPC$ share targeting the "spoolss" named pipe (AccessMask: 0x3).

This pattern is associated with RPC-based abuse of the Windows Print Spooler service, which may allow remote code execution or privilege escalation with SYSTEM privileges.
avatar
karim gi@kappanello
avatar
Detections.ai Community
8 months ago
7084
Page 1 of 2