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

Executive Summary

\nThe Pikachu Worm (often detected as W32/Pikachu.worm) is a classic, early-2000s mass-mailing computer worm designed to appeal to children. Masquerading as a harmless, animated greeting card featuring the popular Pokémon character, its actual payload was highly destructive, attempting to completely delete core Windows operating system directories upon execution.\n\n

Infection Vector and Technical Capabilities

\nPikachu spread almost exclusively via email. It arrived in the victim's inbox with the subject line \"Pikachu Pokemon\" and a body text claiming \"Pikachu is your friend.\" The attached malicious executable was typically named `pikachuPokemon.exe`.\n\nUpon execution, the worm operated in two distinct phases:\n\n\n

Threat Assessment

\nWhile the Pikachu worm is entirely obsolete and unable to function on modern Windows operating systems (due to changes in architecture and the deprecation of `autoexec.bat`), it is historically significant. At the time of its release, it caused widespread panic, particularly in educational institutions, due to its child-friendly disguise and destructive payload.\n\n

Historical Remediation

\n", "cta": "Published by the SystemHelpdesk team.", "aliases": [ "W32/Pikachu.worm", "Worm.Pikachu", "Pikachu.exe" ], "enrichment_level": "expert-seo", "faq": [ { "@type": "Question", "name": "What is Pikachu and what threat category does it belong to?", "acceptedAnswer": { "@type": "Answer", "text": "Pikachu 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 Pikachu establish persistence and evade defensive controls?", "acceptedAnswer": { "@type": "Answer", "text": "Pikachu 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 Pikachu compromise?", "acceptedAnswer": { "@type": "Answer", "text": "Security teams responding to Pikachu 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/Pikachu.worm leverage in enterprise intrusions?", "acceptedAnswer": { "@type": "Answer", "text": "W32/Pikachu.worm 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/Pikachu.worm maintain covert communications and evade perimeter network monitoring?", "acceptedAnswer": { "@type": "Answer", "text": "W32/Pikachu.worm 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", "T1114.003" ], "cisa_advisory": null, "last_updated": "2026-10-15", "type": "Worm / Vandalism", "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": "T1114.003", "name": "Email Forwarding Rule", "tactic": "Collection" } ], "containment_steps": [ "Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Pikachu adversary activity.", "Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Pikachu 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 Pikachu.", "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 Pikachu operators." ], "what_to_avoid": [ "Do not assume the incident is resolved simply because an antivirus tool removed the initial Pikachu 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 Pikachu 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" ] }