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

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

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

title: SystemHelpDesk Detection - Microjoin (Ransomware) Execution & Triage
id: 916a8e67-62bd-573d-b3a3-b7f25ddbcc56
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Microjoin 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/microjoin
- 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.t1566_001
- attack.t1204_002
- attack.t1027
- attack.t1036
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_MICROJOIN_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Microjoin 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 = "microjoin" 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 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)
• Search "microjoin" on Any.Run (Sandbox Sandbox)
• Search "microjoin" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Perez
• Thanatos
• Ransomkd
• Necne
• Crypt0L0Cker
• Prex
• Pccleaners
• Gosys

Machine-readable

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