Killapp

Overview

Executive Summary

Technical Architecture and Exploitation

• Process Enumeration: Upon execution, KillApp rapidly enumerates all running processes on the system, cross-referencing them against a hardcoded list of known security vendors (e.g., `MsMpEng.exe`, `ekrn.exe`, `avp.exe`).
• Forceful Termination: It utilizes Windows APIs (such as `TerminateProcess`) to forcefully kill the identified security software.
• Service Disablement: To ensure the AV does not restart, advanced variants of KillApp will attempt to stop the associated Windows Services and alter their startup type in the Registry (e.g., `HKLM\SYSTEM\CurrentControlSet\Services`) to "Disabled."

Threat Impact

Incident Response and Mitigation

• EDR Tamper Protection: The most effective defense against KillApp is robust Tamper Protection within the EDR/AV solution. This prevents unauthorized processes (even those running as Administrator) from terminating the EDR agent or modifying its core files and registry keys.
• Immediate Network Isolation: If an alert fires indicating that security services have been stopped or terminated unexpectedly, the endpoint must be isolated from the network immediately, as a secondary payload is likely imminent.
• Forensic Investigation: Because KillApp is a precursor tool, incident responders must immediately investigate *how* KillApp was executed (e.g., tracing it back to a weaponized document or a compromised remote access tool).

Known aliases

Threat reports may refer to this family under multiple names:

• Riskware.KillApp
• Tool.KillApp
• Trojan:Win32/KillApp

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

rule MALWARE_WIN_KILLAPP_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Killapp"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "killapp" ascii wide nocase
        $s2 = "riskware.killapp" ascii wide nocase
        $s3 = "tool.killapp" ascii wide nocase
        $s4 = "trojan:win32/killapp" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Killapp (Ransomware) Execution & Triage
id: 3a866414-1d5b-59b2-8fb8-624832bcf9db
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Killapp malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/killapp
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1562_001
- attack.t1489
- attack.t1059
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

rule MALWARE_WIN_KILLAPP_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Killapp tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "killapp" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Killapp from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Killapp symmetric encryption keys or uncompiled payload components may still reside in memory.
3. Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Killapp to inhibit recovery.
4. Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Killapp binary and related persistence hooks are eradicated.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Killapp.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Killapp eradication is completely verified.

References & External Analysis

• Search "killapp" on VirusTotal (External Analysis)
• Search "killapp" on Any.Run (Sandbox Sandbox)
• Search "killapp" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Nabasa
• Rzwaagpbkfii
• Safebreas
• Jbomi
• Donloz
• Azero
• Noupack
• Ransim

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/killapp.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.