Jacksbot
Table of Contents
Overview
Backdoor:Java/Jacksbot is a sophisticated, cross-platform Remote Access Trojan (RAT) written entirely in Java. Because it relies on the Java Virtual Machine (JVM), a single Jacksbot payload can successfully infect and control Windows, macOS, and Linux systems (`T1059.007`). It is primarily designed for full remote administration, credential theft, and enlisting the compromised machine into a botnet for DDoS attacks.
Understanding Jacksbot (Cross-Platform RAT)
To an end-user, the infection is invisible, though system performance may degrade during a DDoS attack. For a SOC analyst, Jacksbot is highly concerning because its cross-platform nature allows attackers to pivot seamlessly across mixed-OS environments (e.g., moving from a compromised Windows workstation to a Linux server).
Execution and RAT Mechanics
Jacksbot is typically distributed via malicious links (Drive-by Downloads) exploiting outdated Java browser plugins, or bundled within pirated software (`.jar` files). Upon execution via the `java.exe` or `javaw.exe` process (`T1059.007`), it establishes persistence specific to the host OS (e.g., Registry Run keys on Windows, `cron` jobs or `init` scripts on Linux). It establishes an encrypted C2 connection, often over IRC or custom TCP protocols. It possesses a vast array of capabilities: remote desktop viewing (VNC), file system manipulation, executing arbitrary shell commands (`T1059.004`), keylogging, and launching UDP/TCP flood attacks against specific targets (`T1498.001`).
Indicators of Compromise & Impact
The impact is total loss of confidentiality and control, plus the liability of the host being used in cyberattacks. Host-based IoCs include EDR alerts for `java.exe` or `javaw.exe` spawning unexpected child processes (like `cmd.exe` or `/bin/sh`), high CPU utilization by the Java process, and the presence of hidden `.jar` files in user directories. Network IoCs include outbound IRC traffic or persistent, encrypted connections to unknown IP addresses on non-standard ports.
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:
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
- T1059.004: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
- T1059.007: 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-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-SEA | Script Execution Analysis | Detect | T1059.004 | Analyze script block syntax and command arguments at runtime to detect malicious automation. |
D3-TR | Traffic Rate Limiting | Isolate | T1498.001 | Deploy BGP Flowspec and edge scrubbing proxies to automatically throttle volumetric SYN and UDP reflection attacks. |
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_JACKSBOT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Jacksbot"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "jacksbot" 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 - Jacksbot (Trojan) Execution & Triage
id: ad964372-75a9-5bbd-a3a2-605ff4a2ca6c
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Jacksbot 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/jacksbot
- 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_007
- attack.t1498_001
- attack.t1059_004
- attack.t1056_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_JACKSBOT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Jacksbot 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 = "jacksbot" 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.
- Isolate the machine immediately to sever the attacker's interactive control and stop any ongoing DDoS participation.
- Determine the vector of execution; if a vulnerable Java browser plugin was exploited, mandate updates across the enterprise.
- Hunt across the network for the specific C2 IP addresses, as Jacksbot frequently spreads to other OS platforms within the environment.
- Assume all credentials present on the machine (stored in browsers, SSH keys on Linux) are compromised and initiate resets.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume Linux or macOS hosts are immune; Jacksbot is specifically designed to run on any OS with a JVM.
- Avoid leaving outdated versions of the Java Runtime Environment (JRE) installed on endpoints.
References & External Analysis
- Search "jacksbot" on VirusTotal (External Analysis)
- Search "jacksbot" on Any.Run (Sandbox Sandbox)
- Search "jacksbot" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Jacksbot and what threat category does it belong to?
Jacksbot 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 Jacksbot establish persistence and evade defensive controls?
Jacksbot 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 Jacksbot compromise?
Security teams responding to Jacksbot 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 Jacksbot?
Jacksbot 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 Jacksbot across enterprise endpoints?
Defenders should hunt for Jacksbot 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 Jacksbot Trojan from Windows?
Manual removal of Jacksbot 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 Jacksbot a virus or a Trojan?
Jacksbot is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Jacksbot typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Jacksbot infection?
Symptoms of Jacksbot 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 Jacksbot 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/jacksbot.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.