Stop

Category: ransomware · Aliases: STOP/Djvu, Djvu Ransomware, Ransomware:Win32/Stop, Trojan-Ransom.Win32.Stop, Djvu · Sample count (EMBER 2018): 8,900 · Enrichment: curated_sourced · Updated: 2026-10-16
Category: RansomwareStatus: Automated SignaturePlatform: WINDOWSStage: Initial-Access, Execution, Persistence, Credential-Access, Discovery, ImpactFirst seen: 2018Actor: STOP SyndicateIndustry: consumers, remote_workers, education, small_businessMotivation: Financial Extortion & Secondary Credential Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
STOP (universally recognized across consumer cybersecurity forums and threat feeds as STOP/Djvu) is the single most prevalent consumer ransomware family in cyber history by raw victim count.

Table of Contents

Overview

STOP (universally recognized across consumer cybersecurity forums and threat feeds as STOP/Djvu) is the single most prevalent consumer ransomware family in cyber history by raw victim count. Active since late 2018, STOP specifically targets home consumers, remote workers, and small business operators by distributing its payloads through trojanized software cracks, warez torrents, key generators (such as fake KMSPico activators), and pirated media bundles. Once executed on a Windows system, the ransomware attempts to reach its centralized command-and-control servers to obtain an 'Online Key' (a unique public RSA key generated per victim). If the host is disconnected or firewalled from the C2 server, STOP falls back to an embedded hardcoded 'Offline Key' that is shared across thousands of victims. The malware traverses all mounted fixed and removable drives, encrypting victim personal files (documents, images, videos, databases) using high-speed AES-256 encryption and appending unique extension tags (with hundreds of observed variants including .djvu, .stop, .gero, .coot, .tisc, and .peet). In over 60% of modern infections, STOP simultaneously deploys secondary infostealers (such as Vidar or RedLine) to harvest stored browser credentials and cryptocurrency wallets before the ransom note (_readme.txt) is displayed.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Stop Early Variant

Known Derivatives & Downstream Variants: Djvu · Gero · Peet · Coot · Tisc · Derp

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-FDAFile Directory Access AuditingDetectT1083Audit and alert on high-frequency recursive directory queries executed by non-system and unclassified binaries.
D3-FAEDFile Alteration Early DetectionDetectT1486Deploy canary files and monitor mass rename/encryption I/O spikes to terminate ransomware threads immediately.
D3-VSSVolume Shadow & Snapshot HardeningHardenT1490Block execution of vssadmin.exe and wmic shadowcopy delete; maintain air-gapped immutable backup repositories.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsHTTP, HTTPS
Observed ports80, 443
Identifiable from traffic aloneMedium

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_STOP_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Stop"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "stop" ascii wide nocase
        $s2 = "stop/djvu" ascii wide nocase
        $s3 = "djvu ransomware" ascii wide nocase
        $s4 = "ransomware:win32/stop" ascii wide nocase
        $s5 = "trojan-ransom.win32.stop" ascii wide nocase
        $s6 = "djvu" 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 - Stop (Ransomware) Execution & Triage
id: b0a24041-ccd2-59e5-9786-39c5649943e2
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Stop malware family. Detects volume shadow copy deletion, boot status tampering,
  and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/stop
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1486
- attack.t1490
- attack.t1059_003
- attack.t1547_001
- attack.t1083
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_STOP_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Stop 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 = "stop" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

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

  1. Disconnect the infected computer from local Wi-Fi and Ethernet networks immediately.
  2. Examine C:\SystemID\PersonalID.txt to inspect the assigned victim identifier; strings ending in 't1' indicate an Offline Key that is fully decryptable.
  3. Run an offline antivirus scan to eradicate co-installed infostealer payloads (Vidar, RedLine) before entering credentials.
  4. Change all banking, email, and social media passwords from a clean, separate device.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Never pay the ransom demand via cryptocurrency; STOP operators rarely deliver working keys to consumers.
  2. Do not download third-party paid 'decryption tools' from untrusted YouTube channels or forums; they are frequently secondary malware.
  3. Avoid downloading cracked software or keygens, which remain the near-exclusive initial access vector for STOP.

References & External Analysis

Frequently Asked Questions

What is STOP/Djvu ransomware?

STOP/Djvu is a prolific consumer-targeting ransomware family that encrypts personal documents and multimedia files using AES-256, distributed primarily through trojanized software cracks and key generators.

Can files encrypted by STOP/Djvu be decrypted for free?

Files encrypted with an 'Offline Key' (indicated by a victim ID ending in 't1') can be decrypted for free using the Emsisoft STOP/Djvu Decryption Tool developed by Michael Gillespie. Files encrypted with unique 'Online Keys' cannot currently be decrypted without private keys.

How does STOP/Djvu infect computers?

STOP/Djvu infects endpoints when users download and execute pirated software, cracked games, video editing software patches, or fake activator tools from torrent sites and deceptive YouTube tutorials.

Why are passwords stolen during a STOP ransomware infection?

STOP ransomware payloads are frequently bundled with secondary information stealers like Vidar or RedLine, which silently extract saved browser passwords, session cookies, and cryptocurrency wallets prior to encrypting files.

What should victims do immediately after a STOP/Djvu infection?

Immediately disconnect the machine from the internet, preserve the C:\SystemID\PersonalID.txt file to identify the key type, scan with reputable antivirus to remove stealer trojans, and change all account passwords from an uninfected device.

What is the architectural difference between STOP/Djvu online keys and offline hardcoded fallback encryption keys?

When STOP/Djvu executes, it attempts to contact its C2 server to retrieve a unique RSA-2048 public key (the 'online key'). If the C2 server is unreachable or offline, the ransomware falls back to a hardcoded static public key embedded in the binary (the 'offline key'). For victims encrypted with an offline key, security researchers at Emsisoft were able to recover the corresponding private key, allowing victims to decrypt their files for free using the Emsisoft Decryptor for STOP/Djvu.

How does STOP/Djvu distribute through cracked software, keygens, and YouTube description links to target consumer systems?

STOP/Djvu dominates consumer malware telemetry because it is distributed through high-volume warez networks, cracked software download portals, torrent trackers, and deceptive YouTube video descriptions promising free activation keys for games and video editors. Bundled with secondary infostealers (such as Vidar or RedLine), the malicious bundle steals passwords before encrypting personal files and appending extensions like .djvu, .gero, or .vve.

How do I remove the Stop Ransomware from Windows?

Manual removal of Stop 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 Stop a virus or a Ransomware?

Stop is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Stop typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Stop infection?

Symptoms of Stop 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 Ransomwares

Want to prevent Stop and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.

📣 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.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/stop.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.