Termite
Table of Contents
Overview
Executive Summary
Termite (often associated with the NetWeaver framework) is a highly capable Remote Access Trojan (RAT) and post-exploitation toolset. While sometimes marketed or discussed in "grey hat" contexts as an administrative tool, its deep capabilities for covert surveillance, process manipulation, and lateral movement make it a severe threat when deployed by malicious actors or utilized during a network breach.Infection Vector and Technical Capabilities
Termite is rarely the initial infection vector. It is typically deployed as a secondary, post-exploitation payload *after* an attacker has already gained initial access to a network (e.g., via spear-phishing, exploiting a vulnerable web server, or purchasing access from an Initial Access Broker). Once deployed, Termite provides the attacker with a comprehensive suite of control capabilities:- Reverse Shell and Command Execution: The core functionality provides a stable, often encrypted, reverse shell connecting back to the attacker's C2 infrastructure, allowing for arbitrary command execution with the privileges of the compromised user.
- Advanced Process Manipulation: Termite excels at evasion. It can inject its code into legitimate running processes (Process Hollowing), manipulate process tokens to escalate privileges (e.g., from a standard user to SYSTEM), and actively hide its network connections from standard monitoring tools.
- Data Exfiltration and Surveillance: The toolset includes modules for capturing screenshots, logging keystrokes, dumping credentials from LSASS memory, and silently archiving and exfiltrating sensitive files.
Threat Assessment
The detection of Termite on a network is a critical security incident. It indicates that an adversary has moved beyond initial access and has established a highly reliable, interactive foothold within the environment. The presence of a RAT like Termite is the immediate precursor to lateral movement and massive data exfiltration.Incident Response and Remediation
- Immediate Containment and Triage: Isolate the infected endpoint immediately. Incident Response teams must perform forensic analysis on the machine (capturing RAM and disk images) to identify the initial entry vector that allowed the attacker to deploy Termite.
- Hunt for Lateral Movement: Because Termite is a post-exploitation tool, incident responders must assume the attacker has stolen credentials and attempted to pivot. An enterprise-wide sweep is required to locate other compromised hosts.
- Global Credential Reset and Rebuild: All credentials stored on or accessible from the compromised endpoint must be reset. The endpoint itself must undergo a complete bare-metal wipe and re-image from a trusted baseline.
Known aliases
Threat reports may refer to this family under multiple names:
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 |
|---|---|---|---|
T1059.003 | Command and Scripting Interpreter: Windows Command Shell | Execution | ATT&CK ↗ |
T1055 | Process Injection | Defense Evasion | ATT&CK ↗ |
T1003.001 | OS Credential Dumping: LSASS Memory (Behaviorally blocking access to credential stores) | Credential Access | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | Command and Control | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1003.001: Monitor for LSASS memory dumping or registry SAM extraction. Enable Credential Guard on Windows systems.
- T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
- 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-LSA | LSA Protection & Credential Guard | Harden | T1003.001 | Enable Windows LSA RunAsPPL (Protected Process Light) and Credential Guard to prevent memory dumping of lsass.exe. |
D3-PIAD | Process Injection Analysis & Detection | Detect | T1055 | Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC). |
D3-PBA | Process Spawn Analysis | Detect | T1059.003 | Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
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_TERMITE_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Termite"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "termite" ascii wide nocase
$s2 = "rat.termite" ascii wide nocase
$s3 = "backdoor.netweaver" ascii wide nocase
$s4 = "hacktool.termite" 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 - Termite (Trojan) Execution & Triage
id: 2f17ecbf-c69c-551f-9de0-3c7729b31f7e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Termite 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/termite
- 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.t1059_003
- attack.t1055
- attack.t1003_001
- attack.t1105
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_TERMITE_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Termite 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 = "termite" 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.
- Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Termite from retrieving secondary stage payloads.
- Capture process memory triage to detect and terminate malicious threads injected by Termite into legitimate system processes such as explorer.exe or svchost.exe.
- Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Termite persistence hooks.
- Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
- Rotate all credentials, domain user passwords, and session cookies active on the system during the Termite execution timeframe.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Termite dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Termite until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "termite" on VirusTotal (External Analysis)
- Search "termite" on Any.Run (Sandbox Sandbox)
- Search "termite" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Termite and what threat category does it belong to?
Termite 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 Termite establish persistence and evade defensive controls?
Termite 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 Termite compromise?
Security teams responding to Termite 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 RAT.Termite?
RAT.Termite 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 RAT.Termite across enterprise endpoints?
Defenders should hunt for RAT.Termite 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 Termite Trojan from Windows?
Manual removal of Termite 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 Termite a virus or a Trojan?
Termite is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Termite typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Termite infection?
Symptoms of Termite 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 Termite 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/termite.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.