Jenxcus
Table of Contents
Overview
Worm:VBS/Jenxcus (often referred to as Houdini or Dinihu) is a prolific, script-based worm and Remote Access Trojan (RAT) written entirely in Visual Basic Script (VBScript). It is notorious for its ability to rapidly propagate across networks via removable media (USB drives) and for providing attackers with a highly persistent, fileless-style backdoor that relies almost entirely on built-in Windows administrative tools (Living off the Land).
Understanding Jenxcus (VBScript Worms)
To an end-user, a Jenxcus infection often starts when they plug in a USB drive and click what appears to be a folder, but is actually a malicious shortcut (`.lnk` file). For a SOC analyst, Jenxcus is a frustrating threat because it is highly evasive; the entire malware payload is often just a few lines of obfuscated text running inside the legitimate `wscript.exe` process, making it difficult for traditional, file-based AV to detect.
Execution and Spreading Mechanics
Jenxcus typically arrives via spear-phishing or infected USB drives (`T1091`). When executed (`T1059.005`), the VBScript heavily obfuscates its core logic to evade static analysis (`T1027`). It establishes persistence by dropping a copy of the VBS script into the `%AppData%` or `Startup` folder and creating a Registry Run key pointing to it (`T1547.001`). For propagation, it constantly monitors the system for new removable drives. When a USB is inserted, it copies its VBScript to the drive, hides all legitimate folders on the drive (`T1564.001`), and creates malicious Windows Shortcut (`.lnk`) files (`T1102.001`) with the same names and icons as the hidden folders. When the next victim clicks the 'folder', the shortcut executes the VBScript and then opens the hidden folder, maintaining the deception. Once active, the script beacons out to a C2 server (often using dynamic DNS services) allowing the attacker to download and execute arbitrary files, run shell commands, or update the worm itself (`T1105`).
Indicators of Compromise & Impact
The impact is a persistent backdoor and the rapid spread of infection across air-gapped or segmented networks via USBs. Host-based IoCs include EDR alerts for `wscript.exe` or `cscript.exe` executing scripts from the `%AppData%` or `%Temp%` directories, or `wscript.exe` making outbound network connections. The presence of hidden folders and corresponding `.lnk` files on USB drives is a definitive indicator.
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.005 | Command and Scripting Interpreter: Visual Basic | Execution | ATT&CK ↗ |
T1091 | Replication Through Removable Media (USB Spreading) | Lateral Movement | ATT&CK ↗ |
T1564.001 | Hide Artifacts: Hidden Files and Directories (Hiding USB folders) | Defense Evasion | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution | Persistence | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1059.005: 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):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-SEA | Script Execution Analysis | Detect | T1059.005 | Analyze script block syntax and command arguments at runtime to detect malicious automation. |
D3-RMC | Removable Media Access Control | Harden | T1091 | Enforce Group Policy settings disabling Windows autorun and block execution permissions on removable USB storage media. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
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_JENXCUS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Jenxcus"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "jenxcus" 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 - Jenxcus (Trojan) Execution & Triage
id: 44547656-e1e9-5241-a756-62d2d97f5f62
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Jenxcus 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/jenxcus
- 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.t1091
- attack.t1547_001
- attack.t1059_005
- attack.t1564_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: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_JENXCUS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Jenxcus 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 = "jenxcus" 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.
- Enforce strict Group Policies to disable Windows AutoRun/AutoPlay and restrict the execution of `.vbs` and `.vbe` files (via Windows Script Host) by standard users.
- Use the command line (`attrib -h -s /s /d driveletter:\*.*`) to unhide the legitimate files on infected USB drives, and then delete the malicious `.lnk` and `.vbs` files.
- Identify the Dynamic DNS domains the script is contacting in the VBS code and block them at the corporate proxy/firewall.
- Audit the Registry Run keys and Startup folders across the network to identify and remove the persistence mechanisms.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not allow the use of unencrypted, unmanaged USB drives, as they are the primary vector for Jenxcus.
- Avoid relying solely on file-based antivirus; heavily obfuscated VBScript requires behavioral monitoring (EDR) of the `wscript.exe` process.
References & External Analysis
- Search "jenxcus" on VirusTotal (External Analysis)
- Search "jenxcus" on Any.Run (Sandbox Sandbox)
- Search "jenxcus" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Jenxcus and what threat category does it belong to?
Jenxcus 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 Jenxcus establish persistence and evade defensive controls?
Jenxcus 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 Jenxcus compromise?
Security teams responding to Jenxcus 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 Jenxcus?
Jenxcus 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 Jenxcus across enterprise endpoints?
Defenders should hunt for Jenxcus 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 Jenxcus Trojan from Windows?
Manual removal of Jenxcus 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 Jenxcus a virus or a Trojan?
Jenxcus is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Jenxcus typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Jenxcus infection?
Symptoms of Jenxcus 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 Jenxcus 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/jenxcus.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.