{ "family": "nyxem", "sample_count": 1, "category": "advanced_threat", "description": "

Executive Summary

\nNyxem (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.\n\n

Infection Vector and Technical Capabilities

\nNyxem 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.\n\nUpon execution, Nyxem performs the following actions:\n\n\n

Threat Assessment

\nNyxem 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.\n\n

Incident Response and Remediation

\n", "cta": "Published by the SystemHelpdesk team.", "aliases": [ "W32.Nyxem", "Worm.KamaSutra", "W32/Blackmal", "Worm:Win32/MyWife" ], "enrichment_level": "expert-seo", "faq": [ { "@type": "Question", "name": "What is Nyxem and what threat category does it belong to?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "How does Nyxem establish persistence and evade defensive controls?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "What are the essential incident response steps for mitigating a Nyxem compromise?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "What lateral movement and credential access tactics does W32.Nyxem leverage in enterprise intrusions?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "How does W32.Nyxem maintain covert communications and evade perimeter network monitoring?", "acceptedAnswer": { "@type": "Answer", "text": "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." } } ], "faq_count": 5, "mitre_attack": [ "T1566.001", "T1485", "T1562.001" ], "cisa_advisory": null, "last_updated": "2026-10-15", "type": "Worm / Data Wiper", "target_industries": [ "Global / Opportunistic" ], "motivation": "Opportunistic", "threat_actors": [ "Unknown / Cybercriminal" ], "target_geographies": [ "Global" ], "attack_stage": [ "execution", "persistence" ], "ecosystem": [ "windows_pe" ], "is_emerging": false, "mitre_attack_detail": [ { "id": "T1566.001", "name": "Phishing: Spearphishing Attachment", "tactic": "Initial Access" }, { "id": "T1485", "name": "Data Destruction", "tactic": "Impact" }, { "id": "T1562.001", "name": "Impair Defenses: Disable or Modify Tools", "tactic": "Defense Evasion" } ], "containment_steps": [ "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": [ "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." ], "target_platforms": [ "Windows 11", "Windows 10", "Windows Server 2022", "Windows Server 2019" ] }