Jscriptwrap

Overview

Executive Summary

Technical Architecture and Exploitation

• Delivery: The user receives a `.js`, `.jse`, `.wsf`, or `.hta` file, often zipped or embedded within a weaponized Office document.
• Obfuscation: The script content is heavily obfuscated, often appearing as an unreadable block of encoded characters (e.g., Base64 or custom XOR encoding) combined with legitimate-looking "junk" code to throw off heuristic analysis.
• In-Memory Execution: When executed by the native `wscript.exe` or `cscript.exe` engines, the JScriptWrap code decodes the primary payload (often a PowerShell script or an embedded PE file). It then utilizes techniques like `Eval()` or COM object instantiation (e.g., `WScript.Shell`) to execute the decoded payload directly in memory, leaving no executable file on the hard drive for the AV to scan.

Threat Impact

Defense and Resilience Strategies

• Script Host Restriction: The most effective defense against JScriptWrap is to disable or strictly control the Windows Script Host (WSH). Use Group Policy to change the default file association for `.js` and `.vbs` files to open in Notepad rather than `wscript.exe`.
• AMSI and EDR: Ensure that the Anti-Malware Scan Interface (AMSI) is fully functional and integrated with your EDR solution. AMSI can intercept and scan the script content *after* it has been de-obfuscated by the script engine, just before execution.
• Behavioral Monitoring: Monitor for suspicious parent-child process relationships, such as `wscript.exe` spawning `powershell.exe` or initiating unexpected outbound network connections.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan.JScriptWrap
• Dropper.JScript
• Script.Obfuscated

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

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_JSCRIPTWRAP_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Jscriptwrap"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "jscriptwrap" ascii wide nocase
        $s2 = "trojan.jscriptwrap" ascii wide nocase
        $s3 = "dropper.jscript" ascii wide nocase
        $s4 = "script.obfuscated" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Jscriptwrap (Ransomware) Execution & Triage
id: 727dc719-74c5-5f17-85e8-38c0ee01f254
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Jscriptwrap malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/jscriptwrap
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_007
- attack.t1027
- attack.t1218_011
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

rule MALWARE_WIN_JSCRIPTWRAP_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Jscriptwrap 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 = "jscriptwrap" 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. Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Jscriptwrap from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Jscriptwrap symmetric encryption keys or uncompiled payload components may still reside in memory.
3. Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Jscriptwrap to inhibit recovery.
4. Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Jscriptwrap binary and related persistence hooks are eradicated.

What to Avoid

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

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Jscriptwrap.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Jscriptwrap eradication is completely verified.

References & External Analysis

• Search "jscriptwrap" on VirusTotal (External Analysis)
• Search "jscriptwrap" on Any.Run (Sandbox Sandbox)
• Search "jscriptwrap" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Vopak
• Umgfxgkazyg
• Satana
• Ridapi
• Listicka
• Stercogs
• Writos
• Mosu

Machine-readable

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