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 the 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.

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_CODE {
    meta:
        description = "Detects Code (ransomware)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "code" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Code Activity
id: c13367945d5d4c91047b3b50234aa7ab
status: experimental
description: Detects generic indicators of the code malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*code*"
    condition: selection
level: medium

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)

Frequently Asked Questions

Related Families (Category: ransomware)

Explore other malware families in the same category:

• Cryptpack
• Gatak
• Meikehuayi
• Za0Au42Rofm
• Cycbot

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/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.