Kaspersky Endpoint Security Service Stopped via Command Line on Linux

Flags Linux commands using systemctl/bash/sh to stop Kaspersky (kesl) services, suggesting defense impairment or manual service shutdown.

FreeReviewedSigma · High · v3
Product
linux
Category
process_creation
Author
Milad Cheraghi (SigmaHQ), DRL 1.1
Published
2025-10-18
Updated
2026-07-31

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies process creation events where a Kaspersky init.d stop action is executed on Linux, either directly through a shell or via systemctl. Attackers may stop or disable security tooling to evade defenses or interfere with incident response. The detection relies on Linux process execution telemetry, matching on process image ending with common shells/systemctl and a command line containing both 'stop' and 'kesl'.

Related detections9 linkedT1685 — drag to rearrange
Malicious Unsigned VIB Installation on ESXi Host via esxcli (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)
Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)
Suspicious EDRKillShifter Vulnerable Driver Load from User Temp Directory (via image_load)
Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)
Malicious FIN7 AvNeutralizer EDR Killer Execution via Masqueraded Binary (via process_creation)
Suspicious Process Explorer Kernel Driver Dropped as PED.sys via File Creation (via file_event)
Malicious Windows Defender Tampering via Set-MpPreference and Add-MpPreference (via ps_script)
Kaspersky Endpoint Security Service Stopped via Command Line on Linux
Pivot detection · T1685 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.