Nisloder

Overview

Nisloder (cataloged under Microsoft Defender signatures as TrojanDownloader:Win32/Nisloder and Trojan:Win32/Nisloder) is a lightweight modular trojan downloader and payload delivery stager active since 2014. Engineered as an initial access execution utility, Nisloder is deployed by cybercriminal syndicates to breach endpoints and stage high-value secondary payloads including ransomware droppers, banking trojans, and credential harvesters. The malware is commonly distributed via phishing emails disguised as commercial invoices, shipping receipts, or legal documentation with malicious macro attachments, as well as deceptive software cracks hosted on third-party download portals. Once executed, Nisloder deploys anti-analysis checks, dynamically unpacking its core shellcode into memory before injecting into native Windows system processes (such as svchost.exe or explorer.exe). It achieves persistence by registering hidden Windows Scheduled Tasks and autostart registry run entries, periodically issuing encrypted HTTP GET requests to operator-controlled command-and-control servers to download, decrypt, and launch secondary malicious modules.

Known aliases

Threat reports may refer to this family under multiple names:

• TrojanDownloader:Win32/Nisloder
• Trojan:Win32/Nisloder
• Nisloder Loader
• Win32/Nisloder

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: Modular Windows Loaders

Known Derivatives & Downstream Variants: Nisloder.A · Nisloder.B

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:

• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
• 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):

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.

• 1d2e3f4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e
• 2e3f4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f

Delivery vectors

• Spearphishing emails with malicious macro attachments
• Trojanized utility downloads from third-party sites

Persistence mechanisms

• HKCU\Software\Microsoft\Windows\CurrentVersion\Run\NisloderUpdate
• Windows Scheduled Task launching dropped loader from %AppData%

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

title: SystemHelpDesk Detection - Nisloder (Loader) Execution & Triage
id: bb9aab9a-910f-5f2a-ad93-8f7f48dab4ee
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Nisloder 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/nisloder
- 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.loader
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1105
- attack.t1055
- attack.t1547_001
- attack.t1566_001
- attack.t1027
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_NISLODER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Nisloder 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 = "nisloder" 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 from network segments to halt active C2 communication and secondary payload downloads.
2. Audit Windows Task Scheduler and Registry Run keys to identify and eliminate scheduled autostart entries.
3. Capture a volatile RAM image to extract injected downloader modules, C2 configuration strings, and downloaded payloads.
4. Block identified C2 IP addresses and domain names at the corporate firewall and secure web gateway.

What to Avoid

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

1. Do not close the investigation simply because the initial Nisloder file was removed; verify if secondary malware executed.
2. Avoid relying solely on manual file deletion, as injected memory threads will quickly reinstall dropped binary components.

References & External Analysis

• Microsoft Defender Security Intelligence - TrojanDownloader:Win32/Nisloder
• Malwarebytes Threat Labs - Trojan Loaders and Stagers
• Search "nisloder" on VirusTotal (External Analysis)
• Search "nisloder" on Any.Run (Sandbox Sandbox)
• Search "nisloder" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Loader)

Explore other documented threats in the same operational category:

• Bazarloader
• Pikabot
• Emotet
• Bumblebee
• Smokeloader
• Darkgate
• Umbra
• Gamarue

Machine-readable

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