Detection rules for Kaspersky data sources. Each rule includes its MITRE ATT&CK mapping, impact rating, and a description of what it detects.

This category contains 19 detection rules.

RuleCategoryTechniqueImpact (C/I/A)
Code Injection Attempt DetectionDefense Evasion, Privilege EscalationT1055 - Process InjectionC:3 / I:3 / A:2
Kaspersky Agent Disabled or TamperedDefense EvasionT1562.001 - Impair Defenses: Disable or Modify ToolsC:3 / I:3 / A:3
Kaspersky Application Privilege Escalation DetectionDefense Evasion, Privilege EscalationT1055/T1134 - Process Injection and Access Token ManipulationC:3 / I:3 / A:2
Kaspersky Command and Control Communication DetectionCommand and ControlT1071 - Application Layer ProtocolC:3 / I:3 / A:2
Kaspersky Critical Object DetectionExecutionT1204 - User Execution: Malicious FileC:3 / I:3 / A:2
Kaspersky Data Exfiltration Attempts DetectionExfiltrationT1048 - Exfiltration Over Alternative ProtocolC:3 / I:2 / A:1
Kaspersky Ransomware Behavior DetectionImpactT1486 - Data Encrypted for ImpactC:3 / I:3 / A:3
Kaspersky Rootkit DetectionDefense EvasionT1014 - RootkitC:3 / I:3 / A:3
Kaspersky Sandbox Evasion Attempts DetectionDefense Evasion, DiscoveryT1497 - Virtualization/Sandbox EvasionC:3 / I:3 / A:2
Kaspersky Suspicious Network Activity DetectionCommand and ControlT1071 - Application Layer ProtocolC:3 / I:2 / A:2
Kaspersky Suspicious Scheduled Tasks DetectionExecution, Persistence, Privilege EscalationT1053 - Scheduled Task/JobC:3 / I:3 / A:2
Kaspersky Suspicious Service Installation DetectionPersistence, Privilege EscalationT1543.003 - Create or Modify System Process: Windows ServiceC:2 / I:2 / A:2
Kaspersky System File Tampering DetectionDefense EvasionT1562.001 - Impair Defenses: Disable or Modify ToolsC:2 / I:3 / A:1
Kaspersky Trusted Application Compromise DetectionDefense EvasionT1218 - Signed Binary Proxy ExecutionC:3 / I:3 / A:2
Kaspersky WMI Abuse DetectionExecutionT1047 - Windows Management InstrumentationC:3 / I:3 / A:2
Lateral Movement Indicators DetectionLateral MovementT1021 - Remote ServicesC:3 / I:3 / A:2
Living Off the Land Binaries (LOLBins) Abuse DetectionDefense EvasionT1218 - System Binary Proxy ExecutionC:3 / I:3 / A:2
Process Hollowing DetectionDefense Evasion, Privilege EscalationT1055.012 - Process Injection: Process HollowingC:3 / I:3 / A:2
Suspicious Packed Executable DetectionDefense EvasionT1027.002 - Obfuscated Files or Information: Software PackingC:3 / I:3 / A:2

Rule Example

Below is an example of a rule definition for Code Injection Attempt Detection (view in repository):

# Rule version v1.0.0

dataTypes:
  - antivirus-kaspersky
name: Code Injection Attempt Detection
impact:
  confidentiality: 3
  integrity: 3
  availability: 2
category: Defense Evasion, Privilege Escalation
technique: "T1055 - Process Injection"
adversary: origin
references:
  - https://attack.mitre.org/techniques/T1055/
  - https://support.kaspersky.com/KESWin/11/en-us/151065.htm
description: |
  Detects attempts to inject malicious code into legitimate processes. This technique is commonly used by malware to evade detection and gain elevated privileges by running within trusted processes.
  
  Next Steps:
  1. Immediately isolate the affected system to prevent lateral movement
  2. Identify the source process that attempted the injection
  3. Check if the malware was successfully quarantined or if manual removal is needed
  4. Review system logs for any suspicious activities around the same timeframe
  5. Scan the system with updated antivirus definitions
  6. Check for persistence mechanisms (scheduled tasks, registry keys, services)
  7. Review network connections from the affected host for C2 communications
  8. Consider reimaging the system if critical processes were compromised
where: |
  (regexMatch("log.msg", "(?i).*(inject|injection|CreateRemoteThread|SetWindowsHookEx|WriteProcessMemory).*") ||
   (contains("log.cs4", ["inject", "hooking", "trojan", "backdoor"]) && 
    contains("action", ["terminate", "delete", "quarantine"]))) &&
  contains("log.msg", ["lsass", "csrss", "winlogon", "services", "svchost", "explorer"])
deduplicateBy:
  - origin.host
  - log.cs4

Rule Details

Code Injection Attempt Detection

Detects attempts to inject malicious code into legitimate processes. This technique is commonly used by malware to evade detection and gain elevated privileges by running within trusted processes.

Kaspersky Agent Disabled or Tampered

Detects when the Kaspersky security agent is disabled, stopped, or tampered with. This is a critical indicator of defense evasion as attackers disable endpoint protection to execute malware undetected.

Kaspersky Application Privilege Escalation Detection

Detects attempts to escalate privileges through application manipulation, process injection, or unauthorized elevation of permissions monitored by Kaspersky endpoint protection. These techniques are commonly used by attackers to gain higher-level permissions on compromised systems.

Kaspersky Command and Control Communication Detection

Detects potential command and control (C2) communication attempts identified by Kaspersky, including suspicious outbound connections, malware callbacks, and botnet communication patterns. This rule triggers when Kaspersky identifies network threats related to botnet activity, C2 communications, or malware beaconing that was not successfully blocked.

Kaspersky Critical Object Detection

Detects when Kaspersky identifies critical threats including malware, trojans, or other dangerous objects that require immediate attention. High severity detections often indicate active threats.

Kaspersky Data Exfiltration Attempts Detection

Detects potential data exfiltration attempts identified by Kaspersky through suspicious network traffic patterns, large data transfers, or connections to suspicious external destinations. This rule monitors for network threats, trojan/backdoor detections, and suspicious data transfer patterns that may indicate data exfiltration.

Kaspersky Ransomware Behavior Detection

Detects ransomware behavior patterns identified by Kaspersky including mass file encryption, ransom note creation, and ransomware-specific malware classifications.

Kaspersky Rootkit Detection

Detects rootkit activity identified by Kaspersky security, including hidden processes, kernel-level modifications, and rootkit-specific malware classifications that indicate a deeply compromised system.

Kaspersky Sandbox Evasion Attempts Detection

Identifies malware attempting to detect and evade sandbox environments. This includes time-based evasion, environment checks, anti-VM techniques, and other behaviors designed to avoid analysis in controlled environments.

Kaspersky Suspicious Network Activity Detection

Detects suspicious network activities including unusual connections, potential C2 communications, or network-based attacks identified by Kaspersky security monitoring. This rule triggers when Kaspersky blocks network connections that match suspicious patterns and multiple similar events occur from the same host.

Kaspersky Suspicious Scheduled Tasks Detection

Detects suspicious scheduled task creation or modification identified by Kaspersky, which could indicate persistence mechanisms used by malware or attackers. Scheduled tasks are commonly abused by attackers to maintain persistence, execute malicious code at specific times, or escalate privileges.

Kaspersky Suspicious Service Installation Detection

Detects suspicious Windows service installation or modification attempts identified by Kaspersky, which could indicate malware persistence mechanisms or privilege escalation attempts. Service manipulation is a common technique used by malware to maintain persistence on compromised systems.

Kaspersky System File Tampering Detection

Detects attempts to tamper with critical system files, Windows services, or protected system components. This includes unauthorized modifications to system binaries, service configurations, or attempts to manipulate security-critical files.

Kaspersky Trusted Application Compromise Detection

Identifies when legitimate or trusted applications exhibit malicious behavior, potentially indicating compromise or exploitation. This includes detecting when signed binaries are used for malicious purposes or when trusted processes perform suspicious activities. This is a critical security event that indicates an attacker may be using living-off-the-land techniques to evade detection.

Kaspersky WMI Abuse Detection

Detects potential Windows Management Instrumentation (WMI) abuse identified by Kaspersky, including suspicious WMI queries, event subscriptions, or process creation via WMI. WMI is a legitimate Windows component often abused by attackers for lateral movement, persistence, and code execution.

Lateral Movement Indicators Detection

Detects indicators of lateral movement attempts within the network through Kaspersky antivirus logs.
Attackers use various techniques including PSExec, WMI, RDP, SMB shares, and exploitation tools to move
from one compromised system to others, expanding their access and control across the network. This rule
identifies blocked or detected activities that may indicate lateral movement attempts.

Living Off the Land Binaries (LOLBins) Abuse Detection

Detects the malicious use of legitimate Windows system binaries (LOLBins) to execute malicious code. Attackers abuse these trusted tools to bypass security controls and maintain persistence. LOLBins are particularly dangerous because they are signed Microsoft binaries that are trusted by most security products.

Process Hollowing Detection

Detects process hollowing attempts where malware creates a new process in suspended state, unmaps its memory, and replaces it with malicious code. This advanced technique is used to evade detection by hiding malicious code within legitimate processes.

Suspicious Packed Executable Detection

Detects when Kaspersky identifies suspicious packed executables, which are often used by malware to evade detection and analysis. Packed executables use compression or encryption to hide their true content and make reverse engineering more difficult.