Nyxem
Table of Contents
Overview
Executive Summary
Nyxem (widely known as Kama Sutra, Blackmal, or MyWife) is a highly destructive mass-mailing computer worm that gained global infamy in early 2006. It combines aggressive social engineering (often using sexually explicit lures) with a devastating time-bomb payload designed to systematically overwrite and destroy critical user documents on the third day of every month.Infection Vector and Technical Capabilities
Nyxem propagates almost exclusively via email. It arrives with enticing subject lines (e.g., "Miss Lebanon 2006," "Kama Sutra pic," "Fw: true romance") and an attached executable, often disguised with a double extension (e.g., `.doc.exe` or `.pdf.zip`) or a provocative icon. Upon execution, Nyxem performs the following actions:- Mass Mailing and Harvesting: The worm harvests email addresses from the local system (address books, cached web pages) and uses its own SMTP engine to aggressively mail copies of itself to all found contacts.
- Security Software Neutralization: Nyxem actively hunts for and terminates processes related to antivirus software, firewalls, and security monitoring tools, effectively blinding the host.
- The "Time Bomb" Payload (Destructive Data Wiping): The most critical feature of Nyxem is its destructive payload. It checks the system clock. On the 3rd day of every month, it activates a wiper routine that searches for and overwrites files with specific extensions (`.doc`, `.xls`, `.mdb`, `.mde`, `.ppt`, `.pps`, `.zip`, `.rar`, `.pdf`, `.psd`, `.dmp`) with the text "DATA ERROR [47 0F 94 93 F4 K5]."
Threat Assessment
Nyxem is classified as a critical, destructive threat. The "time bomb" payload ensures that if the infection is not caught within a specific window, the organization will suffer catastrophic, unrecoverable data loss across all infected endpoints. The mass-mailing capability also causes severe network congestion.Incident Response and Remediation
- Immediate Isolation and Clock Modification: If an active infection is suspected and it is nearing the 3rd of the month, immediately isolate the endpoint and, if necessary, alter the system clock to prevent the trigger condition from executing while remediation occurs.
- Outbound SMTP Blocking: Block unauthorized outbound Port 25 (SMTP) traffic at the firewall to halt the worm's propagation.
- Targeted Malware Removal: Run comprehensive anti-malware scans (often from a safe, bootable environment since the worm disables local AV). Because Nyxem *overwrites* files rather than encrypting them, recovery of the targeted documents requires restoring from offline, air-gapped backups.
Known aliases
Threat reports may refer to this family under multiple names:
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1566.001 | Phishing: Spearphishing Attachment | Initial Access | ATT&CK ↗ |
T1485 | Data Destruction | Impact | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools | Defense Evasion | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- 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):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-WORM | Immutable Backup Storage | Harden | T1485 | Store primary backups in Write-Once-Read-Many (WORM) cloud repositories protected by multi-party out-of-band credentials. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
D3-FS | File Sandboxing (Attachment Detonation) | Isolate | T1566.001 | Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor. |
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_NYXEM_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Nyxem"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "nyxem" ascii wide nocase
$s2 = "w32.nyxem" ascii wide nocase
$s3 = "worm.kamasutra" ascii wide nocase
$s4 = "w32/blackmal" ascii wide nocase
$s5 = "worm:win32/mywife" 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 - Nyxem (Advanced Threat) Execution & Triage
id: 689da5a9-9208-5511-8679-4c23ce508a3e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Nyxem malware family. Detects proxy execution, reflective DLL loading,
and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/nyxem
- 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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_001
- attack.t1485
- attack.t1562_001
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \powershell.exe
- \cmd.exe
- \rundll32.exe
- \regsvr32.exe
CommandLine|contains:
- DownloadString
- IEX(
- '/s /n /u /i:'
- sc create
- start-process
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: highTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_NYXEM_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Nyxem 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 = "nyxem" 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.
- Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Nyxem adversary activity.
- Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Nyxem C2 infrastructure IP/domain lists.
- Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Nyxem.
- Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.
- Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Nyxem operators.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Nyxem dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Nyxem until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "nyxem" on VirusTotal (External Analysis)
- Search "nyxem" on Any.Run (Sandbox Sandbox)
- Search "nyxem" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Nyxem and what threat category does it belong to?
Nyxem is classified as a Advanced Threat. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Nyxem establish persistence and evade defensive controls?
Nyxem typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Nyxem compromise?
Security teams responding to Nyxem should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What lateral movement and credential access tactics does W32.Nyxem leverage in enterprise intrusions?
W32.Nyxem frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.
How does W32.Nyxem maintain covert communications and evade perimeter network monitoring?
W32.Nyxem often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.
How do I remove the Nyxem Advanced_Threat from Windows?
Manual removal of Nyxem 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 Nyxem a virus or a Advanced_Threat?
Nyxem is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Nyxem typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Nyxem infection?
Symptoms of Nyxem 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 Advanced_Threats
Want to prevent Nyxem 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/nyxem.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.