Necurs

Category: spam_bot · Aliases: Necurs, Win32/Necurs, Rootkit.Necurs, Trojan.Necurs · Sample count (EMBER 2018): 2 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: Spam_BotStatus: Automated SignaturePlatform: WINDOWS, X86, X64Stage: Initial-Access, Execution, Defense-Evasion, Persistence, Command-And-ControlFirst seen: 2012Actor: Evil Corp Affiliates ↗Actor: TA505 ↗Industry: banking, healthcare, education, retail, consumersMotivation: Financial Extortion & Fraud🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Botnet:Win32/Necurs was one of the largest, most pervasive botnet infrastructures in cybercrime history, comprising over 9 million compromised computers across 35 countries at its peak operational strength.

Table of Contents

Overview

Botnet:Win32/Necurs was one of the largest, most pervasive botnet infrastructures in cybercrime history, comprising over 9 million compromised computers across 35 countries at its peak operational strength. Discovered in 2012, Necurs functioned as a premier crimeware distribution-as-a-service engine, historically responsible for disseminating world-threatening ransomware and banking malware campaigns including Locky, Dridex, TrickBot, and massive pump-and-dump financial spam runs. Necurs executed via a deeply embedded, digitally signed 32-bit and 64-bit kernel-mode rootkit driver that actively neutralized host security software, subverting Windows Filtering Platform (WFP) hooks, intercepting antivirus syscalls, and disabling security telemetry agents. Its command-and-control network was architected with supreme resilience, employing peer-to-peer (P2P) mesh protocols combined with a high-entropy Domain Generation Algorithm (DGA) that generated up to 2,048 pseudo-random domains every four days across dozens of top-level domains. In March 2020, Microsoft's Digital Crimes Unit (DCU), partnered with international law enforcement and ISPs across 35 nations, executed a landmark coordinated civil takedown (Operation Necurs), legally seizing control of over 6 million anticipated algorithmically generated domains and severing the botnet's command infrastructure.

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: Necurs Rootkit V1 · Necurs Modular Dga Edition · Necurs P2P Fallback Engine

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-KMCKernel Memory Integrity CheckingHardenT1014Enable Hypervisor-Protected Code Integrity (HVCI) and UEFI Secure Boot to prevent unsigned kernel driver execution.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-STASecurity Tool Anti-Tamper EnforcementHardenT1562.001Block unauthorized modification of antivirus registry flags and prevent stopping security agent services.
D3-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.
D3-DNSRDNS Reputation AnalysisDetectT1568.002Deploy recursive DNS security resolvers with algorithmic domain scoring (entropy and n-gram models) to automatically sinkhole DGA queries.

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.

ProtocolsP2P, HTTP, DNS
Observed ports80, 443, 53
Identifiable from traffic aloneHigh

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_NECURS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Necurs"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "necurs" ascii wide nocase
        $s2 = "necurs" ascii wide nocase
        $s3 = "win32/necurs" ascii wide nocase
        $s4 = "rootkit.necurs" ascii wide nocase
        $s5 = "trojan.necurs" 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 - Necurs (Spam Bot) Execution & Triage
id: cb2f1f5a-017d-5879-a99f-2b2cae960f78
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Necurs 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/necurs
- 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.spam-bot
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1014
- attack.t1566_001
- attack.t1568_002
- attack.t1071_001
- attack.t1562_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

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_NECURS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Necurs 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 = "necurs" 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. Deploy boot-time kernel verification tools to detect unlinked rootkit driver objects.
  2. Sinkhole domain queries matching documented Necurs DGA seeds and top-level domain patterns.
  3. Filter inbound gateway SMTP traffic for archive attachments containing macro-enabled Office payloads.
  4. Revoke local administrator rights to prevent kernel-mode driver registration by unprivileged accounts.

What to Avoid

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

  1. Do not attempt manual file deletion of Necurs user-mode components without first unloading the kernel rootkit driver.
  2. Avoid opening unverified email attachments purporting to be automated invoices or shipping receipts.
  3. Never disable Windows Driver Signature Enforcement on production endpoints.

References & External Analysis

Frequently Asked Questions

What was the Necurs botnet?

Necurs was a massive modular botnet comprising over 9 million infected computers used as a global distributor for Locky ransomware, Dridex banking trojans, and penny-stock spam.

How did Necurs maintain persistence and evade detection?

Necurs utilized a signed kernel-mode rootkit driver that hooked Windows system calls, disabled endpoint antivirus products, and blocked firewall inspection tools.

How was the Necurs botnet taken down?

In March 2020, Microsoft Digital Crimes Unit and international law enforcement executed Operation Necurs, algorithmically predicting and legally seizing 6 million DGA domains to sever command and control.

What malware families were distributed by Necurs?

Necurs was the primary delivery vehicle for Locky ransomware, Dridex financial trojans, TrickBot, Jaff ransomware, and pharmaceutical/stock pump-and-dump spam.

What vulnerabilities were used in Necurs email distribution campaigns?

Necurs spam distributed weaponized Office documents exploiting CVE-2016-0189, CVE-2017-0199, and CVE-2017-11882 to execute dropper payloads.

How do I remove the Necurs Spam_Bot from Windows?

Manual removal of Necurs 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.

Is Necurs a virus or a Spam_Bot?

Necurs is classified as a Spam_Bot. Unlike traditional viruses that infect files, modern malware like Necurs typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Necurs infection?

Symptoms of Necurs 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 Spam_Bots

Want to prevent Necurs and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.

📣 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/necurs.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.