Schoolgirl

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 the MITRE ATT&CK framework:

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.

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_SCHOOLGIRL {
    meta:
        description = "Detects Schoolgirl (trojan)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "schoolgirl" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Schoolgirl Activity
id: b6f5000fbc2e1057538e988b0ac9b168
status: experimental
description: Detects generic indicators of the schoolgirl malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*schoolgirl*"
    condition: selection
level: medium

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. 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.
2. Use an enterprise antivirus solution to scan the Windows System directory and the P2P shared folders to remove all copies of the Schoolgirl executable.
3. Block legacy P2P protocols (eDonkey, Kazaa, Gnutella) at the enterprise firewall to prevent re-infection.
4. 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.

1. 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.
2. 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)

Frequently Asked Questions

Related Families (Category: trojan)

Explore other malware families in the same category:

• Goldun
• Xxybvi
• Ceeinject
• Bototer
• Memery

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/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.