Winlock
Table of Contents
Overview
Winlock (historically documented across threat intelligence platforms under designations including Ransom:Win32/Winlock, Trojan-Ransom.Win32.Winlock, and Win32/Winlock) represents a pioneering and destructive screen-locking ransomware family active since 2010. Distributed through compromised adult websites, malicious codec downloads, and drive-by download vectors, Winlock replaces or hooks the Windows graphical shell (explorer.exe), setting itself as the default shell under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon. Upon execution, Winlock renders a non-dismissible, full-screen lockdown banner that covers the desktop, disables Task Manager, registry editing tools, and task switching keystrokes (Alt+Tab, Ctrl+Alt+Del). The locker displays fake legal notices or pornographic scareware messages demanding SMS premium rate messages or cryptocurrency payment to receive a dynamic unlock code.
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 |
|---|---|---|---|
T1491.001 | Defacement: Internal Defacement | Impact | ATT&CK ↗ |
T1547.004 | Boot or Logon Autostart Execution: Winlogon Helper DLL | Persistence | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools | Defense Evasion | ATT&CK ↗ |
T1112 | Modify Registry | Defense Evasion | ATT&CK ↗ |
T1189 | Drive-by Compromise | Initial Access | ATT&CK ↗ |
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-RVM | Registry Value Modification Analysis | Detect | T1112 | Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings. |
D3-RBI | Remote Browser Isolation | Isolate | T1189 | Execute untrusted web browsing sessions in disposable cloud containers to isolate drive-by exploits from local endpoints. |
D3-WIM | Web Interface Monitoring | Detect | T1491.001 | Deploy automated file integrity monitoring (FIM) and continuous HTTP checksum verification across public web roots. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.004 | Monitor changes to standard autostart run keys (HKLM\Software\Microsoft\Windows\CurrentVersion\Run) and Startup folders. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
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_WINLOCK_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Winlock"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "winlock" ascii wide nocase
$s2 = "ransom:win32/winlock" ascii wide nocase
$s3 = "trojan-ransom.win32.winlock" ascii wide nocase
$s4 = "win32/winlock" ascii wide nocase
$s5 = "ransom.winlock" ascii wide nocase
$s6 = "ransom:win32/winlock.a" 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 - Winlock (Ransomware) Execution & Triage
id: eb0f0076-0c17-5a63-96dc-daaf2e2454ee
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Winlock 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/winlock
- 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.t1491_001
- attack.t1547_004
- attack.t1562_001
- attack.t1112
- attack.t1189
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_WINLOCK_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Winlock 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 = "winlock" 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.
- Reboot the affected system into Windows Recovery Environment (WinRE) or bootable offline media.
- Load the offline SYSTEM and SOFTWARE registry hives using regedit.
- Verify and restore HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon 'Shell' to 'explorer.exe'.
- Delete the locker binary located in %APPDATA%, %TEMP%, or %WINDIR%.
- Remove DisableTaskMgr and DisableRegistryTools policies under HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not pay the SMS or cryptocurrency ransom demand, as codes provided are rarely functional.
- Do not reformat the hard drive before attempting Winlogon shell restoration, as user files remain unencrypted.
References & External Analysis
- Microsoft Defender Threat Encyclopedia - Ransom:Win32/Winlock
- Kaspersky Lab - Winlock Ransomware Historical Analysis
- Trend Micro Threat Encyclopedia - Ransom_Winlock
- Search "winlock" on VirusTotal (External Analysis)
- Search "winlock" on Any.Run (Sandbox Sandbox)
- Search "winlock" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Ransom:Win32/Winlock?
Winlock is a landmark screen-locking ransomware family that locks the Windows desktop and demands extortion payment.
How does Winlock hijack the Windows user shell?
It modifies the Winlogon Shell registry entry to execute the locker executable instead of explorer.exe.
How does Winlock prevent users from closing the extortion screen?
It hooks keyboard combinations like Alt+Tab and Ctrl+Alt+Del while disabling Task Manager via registry policies.
How is Winlock delivered to user computers?
It is delivered through malicious media codecs, compromised streaming websites, and exploit kit drive-by downloads.
How can a Winlock ransomware infection be removed?
Boot into Windows Recovery Environment (WinRE) or Safe Mode with Command Prompt, restore the Winlogon Shell value to explorer.exe, and delete the locker binary.
How do I remove the Winlock Ransomware from Windows?
Manual removal of Winlock 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 Winlock a virus or a Ransomware?
Winlock is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Winlock typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Winlock infection?
Symptoms of Winlock 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 Winlock 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/winlock.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.