Detections

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

27 detections

Detects a single process creating several named pipes, which is indicative of the Kazuar malware's communication mechanism between its Kernel, Bridge, and Worker modules. The rule specifically looks for a process creating 3 or more unique named pipes within a 10-minute window.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
001
Detects a worker DLL or executable loaded from the Kazuar working directory shortly after a bridge process creates IPC channels. This behavior is indicative of the Kazuar malware's operational methodology, where a main 'bridge' component loads various 'worker' modules to perform malicious tasks.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
001
Detects several related module processes on one host while a single process accounts for all external network connections. This behavior is indicative of the Kazuar malware, which uses a botnet-like structure where one 'leader' process handles C2 communications.
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
4 months ago
001
Detects the DLL sideloading of the Kazuar v3 loader (hpbprndiLOC.dll) by a legitimate Hewlett-Packard printer driver installer (hpbprndi.exe). This technique is used by Turla to initiate its infection chain.
avatar
Tim Peck@timpeck
avatar
SecOps Signals
10 months ago
5065
Detects a script process (wscript.exe/cscript.exe) creating files in a specific HP-themed path and then creating a Run key for persistence, indicative of the Turla Kazuar VBScript dropper.
avatar
Ethan Andrews@eandrews
avatar
Federal Signal Detections
10 months ago
4133
Detects potential DLL side-loading of the Turla Kazuar backdoor using legitimate executables launched from unusual, actor-specific file paths.
avatar
Tim Peck@timpeck
avatar
Detections.ai Community
1 year ago
00118
Page 2 of 2