Microjoin

Overview

HackTool:Win32/Microjoin (or generic **File Joiner** / **Binder** heuristics) refers to a class of utilities used to secretly combine two or more distinct files into a single, functional executable. While they can be used legitimately, threat actors heavily abuse 'joiners' to bundle a highly destructive malware payload (like a RAT or ransomware) with a benign decoy file (like an image, PDF, or a legitimate software installer) to execute a sophisticated social engineering attack.

Understanding File Joiners
To a victim, executing the joined file appears completely normal; they double-click a 'PDF' (which is actually an `.exe` with a spoofed icon), Adobe Reader opens, and they view the document. For a security analyst, a Microjoin alert means the user has been tricked. While the user was reading the decoy document, the joined malware payload was silently extracted and executed in the background, establishing a backdoor.

Execution and Bundling Mechanics
File joiners operate by taking the raw byte streams of the decoy file and the malicious payload and appending them together, along with a small 'stub' executable (`T1027`). The attacker distributes this joined file via spearphishing (`T1566.001`), often using Right-to-Left Override (RLO) characters or spoofed icons (`T1036`) to make the `.exe` look like a safe document. When executed (`T1204.002`), the stub runs first. It extracts the decoy file to the `%Temp%` directory and opens it with the default application (e.g., Adobe Reader). Simultaneously, it extracts the malware payload, executes it silently in the background, and establishes persistence.

Indicators of Compromise & Impact
The impact depends entirely on the hidden secondary payload (often a RAT). Incident responders should closely monitor EDR logs for 'Anomalous Child Process Spawning'. A major IoC is an executable file dropping a document (PDF/DOCX) into the Temp folder and immediately launching it, while simultaneously launching a secondary, hidden process. Static analysis of the dropped file will reveal the distinct MZ headers of the bundled executables within the larger file structure.

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:

• T1036: Monitor for executable files running from unusual paths or with deceptive names. Use EDR to detect process masquerading.
• T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.

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_MICROJOIN {
    meta:
        description = "Detects Microjoin (ransomware)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "microjoin" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Microjoin Activity
id: 65dcf318ff1fa90a22046f49087bf263
status: experimental
description: Detects generic indicators of the microjoin malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*microjoin*"
    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 immediately to prevent the hidden payload (often a backdoor) from exfiltrating data or moving laterally.
2. Examine EDR telemetry to identify the secondary, hidden process that was spawned when the user opened the 'decoy' file, and terminate it.
3. Perform a deep forensic scan of the system to identify any persistence mechanisms (Registry Run keys, Scheduled Tasks) established by the unpacked malware.
4. Educate the user on identifying executable files (e.g., enabling 'View File Extensions' in Windows) even when they possess document icons.

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 file is safe just because a legitimate document opened; the execution of the decoy is explicitly designed to distract from the malware installation.
2. Avoid relying solely on file deletion, as the hidden payload is already running in memory and may have established its own persistence.

References & External Analysis

• Search "microjoin" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: ransomware)

Explore other malware families in the same category:

• Crifi
• Sfuzuan
• Secucharge
• Orcusrat
• Syscon

Machine-readable

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