Bladabindi

Category: rat · Aliases: njRAT, Bladabindi, Njw0rm, Jenxcus · Sample count (EMBER 2018): 3,930 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: RatSeverity: CRITICALStatus: Automated SignaturePlatform: WINDOWS_PEStage: Persistence, Command And Control, Remote AccessFirst seen: 2012Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Bladabindi (universally recognized in the cybersecurity community as njRAT) is an infamous, widely proliferated remote access trojan originally authored by an individual operating under the moniker 'spar-key' (Naser Al Mutairi) in Kuwait.

Table of Contents

Overview

Bladabindi (universally recognized in the cybersecurity community as njRAT) is an infamous, widely proliferated remote access trojan originally authored by an individual operating under the moniker 'spar-key' (Naser Al Mutairi) in Kuwait. First appearing around 2012 and disseminated openly through Arabic underground hacking forums and YouTube tutorials, Bladabindi quickly became one of the most ubiquitous threat vectors in global cybercrime and targeted espionage. Authored in Microsoft .NET, Bladabindi features a full-featured graphical command console providing complete endpoint compromise: real-time keystroke logging, desktop and webcam video surveillance, microphone eavesdropping, password extraction from web browsers and messaging clients, dynamic process manipulation, registry manipulation, and interactive command execution. The malware became notorious for its aggressive propagation across enterprise USB drives using malicious .lnk shortcuts, dynamic DNS infrastructure for command-and-control, and widespread weaponization by advanced persistent threat (APT) groups across the Middle East, North Africa, and Eastern Europe. In June 2014, Microsoft's Digital Crimes Unit and the Federal Bureau of Investigation (FBI) executed 'Operation Flash'—a high-profile federal civil and criminal action seizing 22 dynamic DNS domains hosted by No-IP that were utilized by Bladabindi and Jenxcus operators to control millions of compromised endpoints.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

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

Known Derivatives & Downstream Variants: Njrat V0.6.4 · Njrat V0.7D · Njw0Rm · Limerat

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

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

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-HACHardware Device Access ControlIsolateT1125Enforce Group Policy hardware access restrictions on integrated webcams and microphones.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsTCP, HTTP, Reverse Shell
Observed ports1177, 5552, 5555, 80, 443
Infrastructure modelDynamic DNS providers (historically No-IP, DynDNS, DuckDNS) resolving to attacker-managed virtual private servers running the njRAT builder and listener consoles.
Encryption / encodingProprietary plaintext or Base64-delimited string protocol utilizing specific delimiter tokens such as '|' and '[kl]' to serialize victim system telemetry and harvested credentials.
Traffic fingerprintOutbound persistent TCP sessions on non-standard ports (e.g. 1177, 5552) exchanging pipe-delimited identification strings containing operating system version, active window title, and webcam status.
Identifiable from traffic aloneHigh

Network detection ideas

Sources: MITRE ATT&CK S0038: njRAT / Bladabindi, CISA / US-CERT Alert TA14-182A (Microsoft Operation Flash)

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.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_BLADABINDI_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Bladabindi"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "bladabindi" ascii wide nocase
        $s2 = "njrat" ascii wide nocase
        $s3 = "bladabindi" ascii wide nocase
        $s4 = "njw0rm" ascii wide nocase
        $s5 = "jenxcus" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Bladabindi (Rat) Execution & Triage
id: b11014f9-d0b8-502c-a361-d0d2147fee48
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Bladabindi malware family. Detects unauthorized persistence creation via
  Windows Registry Run keys, scheduled tasks, and privilege escalation indicative
  of RAT installations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/bladabindi
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.rat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1125
- attack.t1123
- attack.t1059_003
- attack.t1547_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \reg.exe
    - \schtasks.exe
    - \cmd.exe
    - \powershell.exe
    CommandLine|contains:
    - \CurrentVersion\Run
    - /create /tn
    - bypass -enc
    - net user /add
    - net localgroup administrators
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_BLADABINDI_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Bladabindi 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 = "bladabindi" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Isolate the host immediately from all corporate and guest networks.
  2. Identify and terminate malicious .NET host processes residing in %APPDATA% or %TEMP%.
  3. Remove persistent registry keys in HKCU and HKLM Run folders.
  4. Inspect and sanitize all connected USB drives to remove hidden payloads and malicious .lnk shortcuts.
  5. Reset all browser, email, and network credentials accessed from the infected endpoint.

What to Avoid

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

  1. Do not allow infected USB drives to be connected to clean workstations for forensic examination without write-blocking.
  2. Do not rely solely on antivirus signatures, as njRAT builders offer easy obfuscation and crypter integration.

References & External Analysis

North American Authority Advisory (CISA / NIST)

The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: CISA Alert TA14-182A (Operation Flash / Bladabindi & Jenxcus Takedown) ↗

Frequently Asked Questions

What is Bladabindi (njRAT)?

Bladabindi is the security industry detection name for njRAT, a popular .NET remote access trojan first developed in Kuwait in 2012 that grants attackers full surveillance and administrative control over infected systems.

What was Operation Flash?

Operation Flash was a coordinated federal civil and criminal law enforcement action executed in June 2014 by Microsoft Digital Crimes Unit and the FBI, seizing 22 dynamic DNS domains that were controlling millions of Bladabindi/njRAT botnet victims.

How does njRAT spread across local networks?

In addition to phishing emails, njRAT features an aggressive USB spreading module that hides legitimate files on removable drives and replaces them with executable .lnk shortcuts carrying the malware.

What capabilities does Bladabindi possess?

Bladabindi can log keystrokes, capture webcam footage, record microphone audio, steal saved browser credentials, download secondary payloads, and execute reverse command shells.

How should an enterprise respond to an njRAT infection?

Quarantine the machine from the network immediately, terminate rogue .NET processes in AppData, revoke all domain and cloud credentials associated with the user, and scan all removable media across the environment.

How do I remove Bladabindi from Windows?

Manual removal of Bladabindi is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

What are the main symptoms of a Bladabindi infection?

Symptoms of Bladabindi can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Rats

Want to prevent Bladabindi and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

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