Wlock

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Screen Locking Mechanism: If operating as a locker, Wlock modifies the Windows Registry (often hijacking the `Winlogon\Shell` key) to load its own full-screen application instead of the standard `explorer.exe` desktop. This completely prevents the user from accessing the Start menu, taskbar, or any files.
• File Encryption (Crypto-variant): If operating as a standard crypto-ransomware, it rapidly enumerates the hard drive and network shares, encrypting documents, photos, and databases utilizing strong encryption algorithms (like AES or RSA). The original files are deleted, leaving only the encrypted versions.
• Extortion Demand: The malware displays a persistent, intimidating ransom note (often claiming to be from law enforcement or utilizing aggressive countdown timers) instructing the victim on how to purchase cryptocurrency and transfer the funds to the attacker.

Threat Assessment

Incident Response and Remediation

• Network Isolation: Disconnect the infected machine immediately to prevent the ransomware from spreading to mapped network drives or other devices on the LAN.
• Safe Mode Bypass (For Lockers): If Wlock is acting purely as a Screen Locker, booting the machine into "Safe Mode with Command Prompt" or using an offline bootable rescue disk can often bypass the locker application, allowing an administrator to remove the malicious registry keys and delete the executable.
• Data Restoration (For Crypto): If files have been encrypted, paying the ransom is strongly discouraged, as it funds criminal enterprises and does not guarantee a decryption key. The only reliable remediation is a complete wipe and re-image of the system, followed by data restoration from secure, offline backups.

Known aliases

Threat reports may refer to this family under multiple names:

• Ransomware.Wlock
• Trojan.Ransom.Wlock
• WinLock

MITRE ATT&CK Techniques

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

MITRE D3FEND™ Defensive Countermeasures

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

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:

rule MALWARE_WIN_WLOCK_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Wlock"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "wlock" ascii wide nocase
        $s2 = "ransomware.wlock" ascii wide nocase
        $s3 = "trojan.ransom.wlock" ascii wide nocase
        $s4 = "winlock" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Wlock (Ransomware) Execution & Triage
id: 796593b4-2e93-5073-8617-92c1e275a46a
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Wlock 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/wlock
- 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.t1489
- attack.t1547_004
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

rule MALWARE_WIN_WLOCK_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Wlock 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 = "wlock" 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.

1. Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Wlock from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Wlock symmetric encryption keys or uncompiled payload components may still reside in memory.
3. Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Wlock to inhibit recovery.
4. Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Wlock binary and related persistence hooks are eradicated.

What to Avoid

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

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Wlock.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Wlock eradication is completely verified.

References & External Analysis

• Search "wlock" on VirusTotal (External Analysis)
• Search "wlock" on Any.Run (Sandbox Sandbox)
• Search "wlock" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Busky
• Higuniel
• Tibsystems
• Lightmoon
• Msilbot
• Loyeetro
• Psyokym
• Sysdrop

Machine-readable

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