Code

Overview

Trojan:Win32/Code (or Exploit:JS/Code, Script:VBS/Code) is a generic classification denoting the detection of malicious scripting or raw exploit code, rather than a compiled executable binary. This signifies the presence of 'fileless' malware techniques, where attackers leverage built-in operating system interpreters (like PowerShell, VBScript, or JavaScript) (`T1059`) to execute malicious logic directly in memory, bypassing many traditional file-scanning antivirus engines.

Understanding Script-Based Threats ('Code')
To an end-user, an infection utilizing script-based code is often completely invisible, as there is no traditional `.exe` file to double-click. For a SOC analyst, a 'Code' detection usually points to the *delivery mechanism* or *initial access* phase of an attack. The script's job is typically to establish a foothold, disable defenses, and download the actual compiled payload (like ransomware or a RAT).

Execution and Fileless Mechanics
Malicious 'Code' is frequently delivered via weaponized Office documents (Macros), malicious HTML files, or shortcut (`.lnk`) files. Upon execution, the script (e.g., PowerShell) is often heavily obfuscated using Base64 encoding or string manipulation (`T1027`). It runs entirely within the memory space of the interpreter process (e.g., `powershell.exe`, `wscript.exe`, `mshta.exe`), meaning no malicious file is written to the hard drive during the execution phase. The script typically utilizes 'Living off the Land' techniques, employing legitimate administrative commands to download a payload (`T1105`) or create a reverse shell.

Indicators of Compromise & Impact
The impact depends on the payload the script is designed to download. Host-based IoCs require robust behavioral monitoring (EDR): look for anomalous command-line arguments passed to script interpreters (e.g., `powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -EncodedCommand...`), Office applications (`winword.exe`) spawning script interpreters, or `wscript.exe` making outbound network connections. Network IoCs involve the script interpreters making HTTP/HTTPS GET requests to unknown or compromised domains to fetch the secondary payload.

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: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• 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):

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_CODE_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Code"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "code" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Code (Ransomware) Execution & Triage
id: d0d1b3fb-c320-5ed2-ba85-746d83edc321
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Code 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/code
- 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.t1105
- attack.t1059
- attack.t1027
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_CODE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Code 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 = "code" 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 endpoint and determine what the malicious script downloaded and executed; the script is usually just the first stage.
2. Analyze the obfuscated command-line arguments captured by EDR (or PowerShell Script Block Logging) to extract the C2 domains and payload URLs.
3. Implement strict Application Control (like AppLocker or WDAC) to restrict the execution of PowerShell and WScript to authorized administrators only.
4. Disable Office Macros via Group Policy for all documents originating from the internet.

What to Avoid

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

1. Do not assume the threat is neutralized simply because the AV blocked the initial script; always verify if any child processes were spawned.
2. Avoid leaving PowerShell Script Block Logging (Event ID 4104) disabled; it is essential for investigating fileless attacks.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Injectorlib
• Enosch
• Verecno
• Vz2Au4Dpceii
• Cryptinject
• Xxyheo
• Mytonel
• Swotter

Machine-readable

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