Nivdort

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Network Traffic Interception: Its signature capability was deep network interception. It installed malicious proxies or modified system routing to perform Man-in-the-Middle (MitM) attacks. This allowed it to modify web pages in real-time (e.g., changing the price of an item on eBay or stealing credit card data during checkout), even on HTTPS sites.
• Polymorphism and Evasion: The botnet operators utilized advanced server-side polymorphism. Every single victim downloaded a unique, cryptographically distinct version of the malware executable, rendering traditional signature-based AV almost entirely useless at the time.
• Modular Architecture: The botnet could be updated on the fly. The C2 server could push new modules to the infected host to turn it into a spam relay, a cryptocurrency miner, or a generic proxy node.

Threat Assessment

Incident Response and Remediation

• Network Isolation and Triage: Isolate the endpoint immediately. Ensure that the C2 domains associated with the Nivdort variant are sinkholed at the corporate DNS level to prevent the bot from receiving new instructions.
• Forensic Imaging: Because Nivdort heavily modifies network routing and installs custom proxies, a deep forensic analysis may be necessary to understand the full scope of the intercepted data.
• Total Re-imaging: Attempting to manually remove Nivdort is strongly discouraged due to its deep hooks into the OS network stack. A complete bare-metal wipe and re-image is the only secure remediation method.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan.Nivdort
• Botnet.Bayrob
• Win32/Nivdort

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:

• T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
• T1185: Enforce strong MFA and use browser isolation or hardened browsers for sensitive financial or administrative portals to defeat session hijacking.

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

title: SystemHelpDesk Detection - Nivdort (Trojan) Execution & Triage
id: 3cbd8cb7-d2d7-5517-9ec9-5bc5b1b6418c
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Nivdort 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/nivdort
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1562
- attack.t1185
- attack.t1056_001
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_NIVDORT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Nivdort 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 = "nivdort" 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. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Nivdort from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Nivdort into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Nivdort persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Nivdort execution timeframe.

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 incident is resolved simply because an antivirus tool removed the initial Nivdort dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Nivdort until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• Search "nivdort" on VirusTotal (External Analysis)
• Search "nivdort" on Any.Run (Sandbox Sandbox)
• Search "nivdort" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Doser
• Krepper
• Hkautoit
• Esfury
• Cookiesstealer
• Extenbro
• Polip
• Driverdevelop

Machine-readable

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