Schoolgirl
Table of Contents
Overview
Worm:Win32/Schoolgirl is a historic, self-propagating worm from the early-to-mid 2000s that gained prevalence through primitive social engineering and the abuse of peer-to-peer (P2P) file-sharing networks (like Kazaa and eDonkey) and early Instant Messaging protocols. Its primary objective was rapid, viral propagation to drop secondary payloads (often adware or generic trojans) onto victim machines.
Understanding the Schoolgirl Worm
To an infected user, the computer might seem fine initially, but they would soon notice an overwhelming amount of pop-up ads, or their friends would report receiving strange files from them. For security analysts, Schoolgirl represents the era of mass-mailing and P2P worms, where malware relied entirely on tricking users into executing files with enticing, often sexually explicit names (hence the name 'Schoolgirl').
Propagation and P2P Mechanics
The infection cycle begins when a victim downloads what they believe to be a video or image file from a P2P network (`T1204.002`). The file is actually the Schoolgirl executable, often disguised with a double extension (e.g., `video.avi.exe`) (`T1036.004`). Upon execution, it establishes persistence via Registry Run keys (`T1547.001`). The worm's core propagation mechanism involves copying itself into the shared upload directories of installed P2P software (like the `My Shared Folder` in Kazaa) and giving itself hundreds of highly searched, enticing filenames (`T1083`). When other users search the P2P network, they download the worm from the infected machine. It also attempts to mail copies of itself to addresses found in the Windows Address Book (`T1534`).
Indicators of Compromise & Impact
The primary impact was severe network congestion on P2P protocols and the deployment of secondary adware. The most glaring IoC is the presence of hundreds of executable files with random, enticing names appearing in the user's P2P shared folders. Host-based IoCs include EDR alerts for the creation of randomly named executables in the Windows System directory and unauthorized SMTP traffic originating from the endpoint (as it attempts to mass-mail itself).
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 |
|---|---|---|---|
T1204.002 | User Execution: Malicious File (Double extensions) | Execution | ATT&CK ↗ |
T1534 | Internal Spearphishing (Propagating via Mass-Mailing) | Lateral Movement | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys | Persistence | ATT&CK ↗ |
T1036.004 | Masquerading: Masquerade Task or Service (Fake filenames in P2P folders) | Defense Evasion | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1036.004: Monitor for executable files running from unusual paths or with deceptive names. Use EDR to detect process masquerading.
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-PMA | Process Lineage & Masquerade Analysis | Detect | T1036.004 | Verify digital code-signing signatures and compare executable paths against known Windows binaries. |
D3-FEA | File Execution Analysis | Harden | T1204.002 | Enforce AppLocker and Windows Defender Application Control (WDAC) to block executable launches from temporary and user-writable directories. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
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_SCHOOLGIRL_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Schoolgirl"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "schoolgirl" 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 - Schoolgirl (Trojan) Execution & Triage
id: 5850febb-8120-5ec6-83e9-292c57fa2536
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Schoolgirl 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/schoolgirl
- 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.t1036_004
- attack.t1547_001
- attack.t1534
- attack.t1204_002
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: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_SCHOOLGIRL_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Schoolgirl 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 = "schoolgirl" 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.
- Isolate the endpoint from the network to halt the mass-mailing engine and stop other P2P users from downloading the worm from the infected host.
- Use an enterprise antivirus solution to scan the Windows System directory and the P2P shared folders to remove all copies of the Schoolgirl executable.
- Block legacy P2P protocols (eDonkey, Kazaa, Gnutella) at the enterprise firewall to prevent re-infection.
- Instruct the user to notify their contacts to ignore any recent unexpected email attachments sent from their profile.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the threat is modern; Schoolgirl heavily targets obsolete P2P protocols, meaning an infection on a modern system is rare unless the user is running legacy software.
- Avoid ignoring the incident; while the worm itself is old, the vector (executing unknown files) indicates a severe lack of security awareness.
References & External Analysis
- Search "schoolgirl" on VirusTotal (External Analysis)
- Search "schoolgirl" on Any.Run (Sandbox Sandbox)
- Search "schoolgirl" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Schoolgirl and what threat category does it belong to?
Schoolgirl is classified as a Trojan. 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 Schoolgirl establish persistence and evade defensive controls?
Schoolgirl 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 Schoolgirl compromise?
Security teams responding to Schoolgirl 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 secondary payloads and staging behaviors are commonly associated with Schoolgirl?
Schoolgirl frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Schoolgirl across enterprise endpoints?
Defenders should hunt for Schoolgirl by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove the Schoolgirl Trojan from Windows?
Manual removal of Schoolgirl 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 Schoolgirl a virus or a Trojan?
Schoolgirl is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Schoolgirl typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Schoolgirl infection?
Symptoms of Schoolgirl 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 Schoolgirl 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/schoolgirl.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.