Kwampirs
Table of Contents
Overview
Backdoor:Win32/Kwampirs is a sophisticated, highly targeted remote access trojan (RAT) primarily associated with the Advanced Persistent Threat (APT) group known as **Orangeworm**. Kwampirs gained notoriety for its laser-focused, long-term espionage campaigns against the **Healthcare sector**, specifically targeting international hospital networks, medical equipment manufacturers, and providers of healthcare logistics and IT services.
Understanding Kwampirs (Targeted Espionage)
To an end-user, a Kwampirs infection is completely silent. For an incident response team, detecting Kwampirs indicates a severe, state-sponsored or highly organized corporate espionage breach. The attackers specifically aim to compromise systems that control high-value medical imaging devices (like X-Ray and MRI machines) to steal intellectual property, patient data, and maintain deep, long-term persistence within critical healthcare infrastructure.
Execution and Backdoor Mechanics
Kwampirs is often delivered via targeted spearphishing (`T1566.001`) or supply chain compromises. Upon execution, it achieves persistence by installing itself as a hidden Windows Service (`T1543.003`), aggressively attempting to blend in with legitimate system processes. Kwampirs is a modular backdoor; it opens a covert channel to its C2 server (`T1071.001`) and can receive commands to download further payloads (`T1105`). It contains a highly aggressive, built-in network propagation module that aggressively copies itself across open network shares (`T1021.002`), attempting to infect every reachable machine on the hospital network to ensure persistence even if the initial beachhead is discovered.
Indicators of Compromise & Impact
The impact is extreme: the compromise of critical healthcare systems and the theft of highly sensitive IP and PHI. Host-based IoCs include the presence of a hidden Windows service (often disguised with names mimicking legitimate medical software or system drivers), and the presence of the Kwampirs payload (often an obfuscated DLL) in the `System32` directory. Network IoCs include massive spikes in SMB (Port 445) traffic as the malware attempts aggressively to copy itself to all accessible network shares, and periodic beaconing to known Orangeworm C2 infrastructure.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1543.003 | Create or Modify System Process: Windows Service | Persistence | ATT&CK ↗ |
T1021.002 | Remote Services: SMB/Windows Admin Shares (Aggressive lateral movement) | Lateral Movement | ATT&CK ↗ |
T1071.001 | Application Layer Protocol: Web Protocols (C2 Beaconing) | Command and Control | ATT&CK ↗ |
T1105 | Ingress Tool Transfer (Downloading further espionage tools) | Command and Control | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-NBA | Network Behavioral Analysis | Detect | T1021.002 | Enforce SMB message signing, disable legacy SMBv1, and restrict administrative share access (C$, ADMIN$) to dedicated PAM bastion hosts. |
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
D3-SCM | Windows Service Creation Monitoring | Detect | T1543.003 | Verify service binary image signatures and restrict standard users from creating or modifying service definitions. |
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:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_KWAMPIRS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Kwampirs"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "kwampirs" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Kwampirs (Trojan) Execution & Triage
id: 11cfae60-b26a-5fd8-b9bc-7196e0107d3b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Kwampirs malware family. Detects suspicious execution from temporary user
directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/kwampirs
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1543_003
- attack.t1105
- attack.t1021_002
- attack.t1071_001
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_KWAMPIRS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Kwampirs 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 = "kwampirs" 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.
- Due to its aggressive SMB propagation, immediately isolate infected subnets to halt the worm-like lateral movement across the hospital network.
- Audit all Windows Services on suspected endpoints for anomalous entries, specifically focusing on systems controlling medical imaging hardware.
- Analyze firewall logs for beaconing activity and block all identified C2 infrastructure enterprise-wide.
- Assume a massive data breach of Intellectual Property and Patient Health Information (PHI) and engage incident response and legal counsel.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not attempt a simple 'whack-a-mole' remediation by deleting the malware on a single host; Kwampirs' aggressive lateral movement means it is likely on dozens of other machines.
- Avoid rebooting critical medical infrastructure without a coordinated incident response plan, as the malware may have hooked critical system processes.
References & External Analysis
- Search "kwampirs" on VirusTotal (External Analysis)
- Search "kwampirs" on Any.Run (Sandbox Sandbox)
- Search "kwampirs" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Kwampirs and what threat category does it belong to?
Kwampirs is classified as a Trojan. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Kwampirs establish persistence and evade defensive controls?
Kwampirs typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Kwampirs compromise?
Security teams responding to Kwampirs should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What secondary payloads and staging behaviors are commonly associated with Kwampirs?
Kwampirs frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Kwampirs across enterprise endpoints?
Defenders should hunt for Kwampirs by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove the Kwampirs Trojan from Windows?
Manual removal of Kwampirs is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
Is Kwampirs a virus or a Trojan?
Kwampirs is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Kwampirs typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Kwampirs infection?
Symptoms of Kwampirs can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Trojans
Want to prevent Kwampirs and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/kwampirs.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.