Pikachu
Table of Contents
Overview
Executive Summary
The 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.Infection Vector and Technical Capabilities
Pikachu 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`. Upon execution, the worm operated in two distinct phases:- Propagation (Mass Mailing): Like many worms of its era (e.g., ILOVEYOU), Pikachu immediately accessed the victim's Microsoft Outlook Address Book. It then utilized Outlook's COM interface to automatically email a copy of itself to every contact in the address book, ensuring rapid, exponential spread across networks.
- Destructive Payload: The worm's secondary function was system vandalism. It modified the `autoexec.bat` file (a critical startup script in older Windows versions like 95, 98, and ME). It added the commands `del C:\WINDOWS\*.* /y` and `del C:\WINDOWS\SYSTEM\*.* /y`, which would attempt to delete the entire Windows directory upon the next system reboot.
Threat Assessment
While 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.Historical Remediation
- Payload Interception: Interestingly, the worm contained a flaw. It often prompted the user with a standard Windows confirmation dialog box ("Are you sure you want to delete these files?") before executing the destructive `del` commands, allowing alert users to cancel the payload.
- Registry and File Cleanup: Remediation involved booting into Safe Mode, deleting the malicious `pikachuPokemon.exe` file, and manually editing the `autoexec.bat` file to remove the destructive commands before rebooting normally.
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 ↗ |
T1114.003 | Email Forwarding Rule | Collection | 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-EAM | Email Access Monitoring | Detect | T1114.003 | Monitor Graph API and MAPI email harvesting routines and alert on bulk email downloads originating from unusual IP addresses. |
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-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_PIKACHU_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Pikachu"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "pikachu" ascii wide nocase
$s2 = "w32/pikachu.worm" ascii wide nocase
$s3 = "worm.pikachu" ascii wide nocase
$s4 = "pikachu.exe" 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 - Pikachu (Advanced Threat) Execution & Triage
id: 346609b0-43da-5499-a88f-d4aab19b0848
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Pikachu 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/pikachu
- 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.t1114_003
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: high
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_PIKACHU_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Pikachu 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 = "pikachu" 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 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
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 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.
References & External Analysis
- Search "pikachu" on VirusTotal (External Analysis)
- Search "pikachu" on Any.Run (Sandbox Sandbox)
- Search "pikachu" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Pikachu and what threat category does it belong to?
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.
How does Pikachu establish persistence and evade defensive controls?
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.
What are the essential incident response steps for mitigating a Pikachu compromise?
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.
What lateral movement and credential access tactics does W32/Pikachu.worm leverage in enterprise intrusions?
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.
How does W32/Pikachu.worm maintain covert communications and evade perimeter network monitoring?
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.
How do I remove the Pikachu Advanced_Threat from Windows?
Manual removal of Pikachu 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 Pikachu a virus or a Advanced_Threat?
Pikachu is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Pikachu typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Pikachu infection?
Symptoms of Pikachu 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 Pikachu 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/pikachu.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.