Binder

Overview

Binder (cataloged across cybersecurity vendors under detections including HackTool:Win32/Binder, Trojan:Win32/Binder, and Win32/Binder) is a broad classification for malicious file joiner and binder utility frameworks active since 2005. Engineered to merge two or more independent files into a single compiled executable wrapper stub, Binder utilities are widely abused by threat actors to disguise malicious payloads inside seemingly harmless carrier programs (such as games, software installers, screen savers, or multimedia documents). When a victim launches the bound binary, the wrapper silently extracts the decoy application to %Temp% and executes it in the foreground to eliminate suspicion, while simultaneously unpacking, executing, and persisting the concealed secondary payload—such as a remote access trojan (RAT), infostealer, keylogger, or cryptominer—in the background without user interaction.

Known aliases

Threat reports may refer to this family under multiple names:

• HackTool:Win32/Binder
• Trojan:Win32/Binder
• Win32/Binder
• FileBinder

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Classic Windows Pe File Binders

Known Derivatives & Downstream Variants: Binder.Stub · Joiner.Win32

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.002: Monitor for executable files running from unusual paths or with deceptive names. Use EDR to detect process masquerading.
• T1036.004: Monitor for executable files running from unusual paths or with deceptive names. Use EDR to detect process masquerading.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

• 2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c
• 8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a

Delivery vectors

• installer_bundle.exe
• game_trainer_crack.exe

Persistence mechanisms

• %Temp%\decoy_app.exe
• %AppData%\payload_svc.exe

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_BINDER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Binder"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "binder" ascii wide nocase
        $s2 = "hacktool:win32/binder" ascii wide nocase
        $s3 = "trojan:win32/binder" ascii wide nocase
        $s4 = "win32/binder" ascii wide nocase
        $s5 = "filebinder" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Binder (Hacktool) Execution & Triage
id: 6107ac86-db7b-5e1a-9099-b58611a9e046
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Binder malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/binder
- 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.hacktool
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1027_002
- attack.t1036_002
- attack.t1204_002
- attack.t1059_003
- attack.t1105
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

rule MALWARE_WIN_BINDER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Binder 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 = "binder" 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. Quarantine the initial executable to prevent it from dropping and launching the hidden malicious payloads.
2. Clear the Windows `%Temp%` directory, as file binders overwhelmingly use this location to extract and stage their hidden components.
3. Utilize EDR to identify and terminate any child processes spawned by the initial executed file (excluding the legitimate decoy application).
4. Perform a full system sweep to identify the specific malware family that was dropped by the binder.

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 endpoint is safe simply because the user saw the expected document; the malware executed silently in the background.
2. Avoid ignoring the delivery vector; if a bound file arrived via email, a spearphishing campaign is actively targeting the organization.

References & External Analysis

• Huntress Threat Research - Understanding File Binders and Joiners
• Microsoft Defender Security Intelligence - HackTool:Win32/Binder
• Search "binder" on VirusTotal (External Analysis)
• Search "binder" on Any.Run (Sandbox Sandbox)
• Search "binder" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Hacktool)

Explore other documented threats in the same operational category:

• Remoteadmin
• Screenconnect
• Cobaltstrike
• Meterpreter
• Bruteforce
• Dllinject
• Bypassuac
• Pswtool

Machine-readable

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