Jps

Overview

JPS (cataloged across security software as Trojan:Win32/JPS, Virus:Win32/JPS, and Trojan.Win32.JPS) is the compiled runtime client component generated by the JPS Virus Maker framework during the early 2000s underground virus authoring era. When executed, JPS drops secondary trojan components into the Windows system directory, establishes registry Run key persistence, modifies executable file associations, and attempts to spread locally across connected drives and shared folders. The trojan executes pre-configured disruptive subroutines designed by the toolkit operator, including terminating antivirus processes, disabling system management tools, and establishing reverse backdoor connections.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan:Win32/JPS
• Virus:Win32/JPS
• Trojan.Win32.JPS
• Win32/JPS.Trojan
• JPS.Client

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Jps_Virus_Maker

Known Derivatives & Downstream Variants: Jps Client V1.0 · Jps Client V2.0 · Win32/Jps.Gen

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.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):

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

• CVE-2010-2568 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
• CVE-2012-0158 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

• 9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d
• 4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d4e5f

Delivery vectors

• Peer-to-peer file sharing networks disguised as software cracks and game cheat tools
• Compromised software freeware download portals and bundled installers

Persistence mechanisms

• HKLM\Software\Microsoft\Windows\CurrentVersion\Run\JPSClient
• Startup folder shortcut placed under %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup

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_JPS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Jps"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "jps" ascii wide nocase
        $s2 = "trojan:win32/jps" ascii wide nocase
        $s3 = "virus:win32/jps" ascii wide nocase
        $s4 = "trojan.win32.jps" ascii wide nocase
        $s5 = "win32/jps.trojan" ascii wide nocase
        $s6 = "jps.client" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Jps (Trojan) Execution & Triage
id: db8144b1-b780-5dea-be28-c1e1212f21f8
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Jps 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/jps
- 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.t1547_001
- attack.t1112
- attack.t1562_001
- attack.t1059_003
- 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

rule MALWARE_WIN_JPS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Jps 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 = "jps" 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. Isolate the affected machine to block active command sessions and prevent local network share propagation.
2. Kill active JPS binaries and spawned shell processes running out of %SYSTEMROOT%\System32.
3. Restore disabled administrative tooling (Task Manager, Regedit) by purging malicious registry policy keys.
4. Scan all attached storage volumes to detect and remove residual JPS dropper binaries.

What to Avoid

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

1. Do not execute software utilities downloaded from unverified peer-to-peer file-sharing networks.
2. Avoid bypassing operating system warnings when launching unsigned executable binaries.

References & External Analysis

• Kaspersky Threat Intelligence - Trojan.Win32.JPS
• Trend Micro Threat Encyclopedia - Trojan.Win32.JPS
• NIST National Vulnerability Database - CVE-2010-2568
• Search "jps" on VirusTotal (External Analysis)
• Search "jps" on Any.Run (Sandbox Sandbox)
• Search "jps" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Injeber
• Trojna
• Perflogger
• Mosucker
• Vbclone
• Mepaow
• Pcmega
• Trjgen

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/jps.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.