Mbrlock

Overview

Ransom:Win32/Mbrlock represents a highly destructive class of ransomware known as **Bootlockers**. Unlike traditional file-encrypting ransomware that targets individual documents (like Word or PDF files), Mbrlock targets the foundational architecture of the hard drive itself. It specifically overwrites the Master Boot Record (MBR) of the infected system, preventing the Windows operating system from loading entirely and holding the entire computer hostage.

Understanding Bootlocker Ransomware
To an infected user, the impact is immediate and terrifying. Instead of the familiar Windows logo upon turning on the computer, they are greeted by a stark, text-only (DOS-like) screen demanding a ransom payment to unlock the system. For a security analyst, Mbrlock indicates a severe breach that requires low-level disk recovery techniques to remediate, as the operating system's boot process has been hijacked (`T1542.003`). Notable examples of Mbrlock-style malware include the early versions of Petya and various 'lock-screen' extortion variants.

Execution and Boot Hijacking Mechanics
Mbrlock is often distributed via spear-phishing or dropped as a secondary payload by other trojans. Upon execution (`T1204.002`), it requires administrative privileges. Once obtained, it uses low-level disk writing APIs (like `DeviceIoControl`) to access `PhysicalDrive0` directly. It backs up the legitimate Master Boot Record (MBR), encrypts or obfuscates it, and then overwrites the active MBR with its own malicious, custom bootloader (`T1542.003`). Finally, it forces a system reboot (`T1529`). When the BIOS/UEFI attempts to boot the computer, it loads the malicious Mbrlock code instead of the Windows bootloader, displaying the ransom note and preventing OS initialization.

Indicators of Compromise & Impact
The impact is total denial of service for the endpoint. The primary IoC is the inability to boot into Windows, replaced by a text-mode ransom note. EDR systems monitoring for low-level disk access (`T1006`) will often flag the attempt to overwrite the MBR if they are active before the reboot. Because the OS never loads, traditional antivirus cannot run to remove the threat once the system has rebooted.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

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_MBRLOCK {
    meta:
        description = "Detects Mbrlock (ransomware)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "mbrlock" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

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

Containment & Response Steps

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

1. Do not pay the ransom. Mbrlock variants are often poorly coded, and paying does not guarantee a working unlock code.
2. Boot the infected system using a legitimate Windows Recovery Environment (WinRE) USB drive or a Linux Live CD.
3. Use the `bootrec.exe /fixmbr` command (or equivalent Linux utilities like `testdisk`) to overwrite the malicious bootloader with a standard Windows MBR, restoring the ability to boot.
4. Once booted back into Windows, immediately perform a full offline antivirus scan to remove the initial dropper executable that caused the infection.

What to Avoid

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

1. Do not format the hard drive immediately; the actual user files are often untouched (unless it's a destructive wiper variant like NotPetya), and restoring the MBR usually recovers the entire system intact.
2. Avoid turning the computer on and off repeatedly; if the malware also encrypted the Master File Table (MFT), this could cause further corruption.

References & External Analysis

• Search "mbrlock" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: ransomware)

Explore other malware families in the same category:

• Agile
• Eb149B
• Xmgfa0Ysjgki
• Floder
• Tilken

Machine-readable

Get this profile as JSON: https://jordan123234-malware-families-explorer.static.hf.space/api/mbrlock.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.