Infector_Ng_2004

Category: trojan · Aliases: Trojan:Win32/InfectorNG2004, Virus:Win32/InfectorNG, Trojan.Win32.Infector, Win32/InfectorNG.Trojan, InfectorNG.2004 · Sample count (EMBER 2018): 1,500 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: TrojanSeverity: MEDIUMStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, ExecutionFirst seen: 2004Motivation: Espionage🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Infector NG 2004 (Infector Next Generation, cataloged across security telemetry as Trojan:Win32/InfectorNG2004, Virus:Win32/InfectorNG, and Trojan.Win32.Infector) is a legacy dual-action file infector generator and backdoor trojan developed in 2004.

Table of Contents

Overview

Infector NG 2004 (Infector Next Generation, cataloged across security telemetry as Trojan:Win32/InfectorNG2004, Virus:Win32/InfectorNG, and Trojan.Win32.Infector) is a legacy dual-action file infector generator and backdoor trojan developed in 2004. Distributed as an underground builder toolkit, Infector NG 2004 enabled malware authors to generate customized trojan droppers that appended parasitic loader subroutines to local Windows portable executable (PE) files (.exe and .scr). When an infected host binary is executed, the trojan executes its malicious payload prior to transferring control back to the legitimate host application. Its capabilities include keystroke interception, registry policy tampering, downloading secondary malware packages, and establishing reverse command-and-control backdoors.

Known aliases

Threat reports may refer to this family under multiple names:

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: Win32 Pe Infector Generators

Known Derivatives & Downstream Variants: Infector Ng Build 102 · Infector Ng 2004 Pro · Win32/Infectorng.Gen

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-PIADProcess Injection Analysis & DetectionDetectT1055.002Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
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-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
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:

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_INFECTOR_NG_2004_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Infector_Ng_2004"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "infector_ng_2004" ascii wide nocase
        $s2 = "trojan:win32/infectorng2004" ascii wide nocase
        $s3 = "virus:win32/infectorng" ascii wide nocase
        $s4 = "trojan.win32.infector" ascii wide nocase
        $s5 = "win32/infectorng.trojan" ascii wide nocase
        $s6 = "infectorng.2004" 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 - Infector_ng_2004 (Trojan) Execution & Triage
id: 5c580e3f-2c7e-5fde-94b9-c666841d10d0
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Infector_ng_2004 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/infector_ng_2004
- 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.t1055_002
- attack.t1056_001
- attack.t1059_003
- attack.t1547_001
- 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

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_INFECTOR_NG_2004_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Infector_Ng_2004 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 = "infector_ng_2004" 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 affected endpoints from corporate network shares to halt lateral PE file infection.
  2. Quarantine and disinfect all executables exhibiting appended parasitic sections or altered entry points.
  3. Delete persistence registry entries located under HKCU\Software\Microsoft\Windows\CurrentVersion\Run.
  4. Verify the integrity of system host executables by running sfc /scannow or restoring from known-good golden images.

What to Avoid

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

  1. Do not execute clean binaries from mapped drives while connected to an infected workstation.
  2. Avoid relying solely on file cleaning tools for mission-critical systems; golden image restoration is recommended.

References & External Analysis

Frequently Asked Questions

What is Infector NG 2004?

Infector NG 2004 is a legacy dual-function file infector generator and backdoor trojan developed in 2004.

How does Infector NG 2004 infect executable binaries?

It appends parasitic loader routines to local PE executables and modifies binary entry points to execute the trojan first.

What remote access capabilities does Infector NG 2004 provide?

It provides keystroke logging, secondary payload downloading, registry modification, and reverse command shells.

Which CVE vulnerabilities have been linked to Infector NG 2004 delivery?

Droppers delivering Infector NG 2004 have exploited common shortcut and document flaws including CVE-2010-2568 and CVE-2012-0158.

How should administrators clean an Infector NG 2004 infection?

Scan and disinfect or restore all infected PE files, remove Run registry entries, and reboot from a clean recovery image.

How do I remove the Infector_Ng_2004 Trojan from Windows?

Manual removal of Infector_Ng_2004 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 Infector_Ng_2004 a virus or a Trojan?

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

What are the main symptoms of a Infector_Ng_2004 infection?

Symptoms of Infector_Ng_2004 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 Trojans

Want to prevent Infector_Ng_2004 and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan 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 Threat Intelligence Team.

Machine-readable

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