More than a year after its leak in September 2022, the builder for the notorious LockBit 3.0 ransomware continues to be a persistent and widespread threat. Security researchers report that a diverse array of threat actors, from low-skilled opportunists to more organized groups, are using the leaked tool to create and launch their own ransomware campaigns. This has led to a decentralization and proliferation of LockBit-based attacks, making attribution nearly impossible and increasing the overall volume of ransomware incidents. The leak has had a lasting impact on the cybercrime landscape, effectively turning a sophisticated RaaS product into a freely available weapon.
The leaked LockBit 3.0 builder is a command-line application that allows a user to generate a fully customized ransomware payload. An attacker can configure various options, including the ransom note text, encryption settings, and services to terminate, before compiling a unique executable. This ease of use has lowered the barrier to entry for ransomware deployment, enabling criminals without the technical skill to develop their own malware to conduct damaging attacks.
Security firms are observing a steady stream of incidents involving these custom LockBit variants. In many cases, the attackers attempt to rebrand the malware, but forensic analysis reveals its origins from the leaked builder. This phenomenon complicates threat intelligence, as an attack using a LockBit-based binary can no longer be definitively attributed to the core LockBit group (which itself was recently disrupted by law enforcement).
The builder, often referred to as builder.exe, allows for the generation of three key components:
Attackers use this tool to create variants that are then deployed using common ransomware TTPs. The resulting attacks are characteristic of modern ransomware operations.
T1566 - Phishing, T1133 - External Remote Services, or exploiting vulnerabilities in public-facing applications.T1059.001 - Command and Scripting Interpreter: PowerShell to run reconnaissance and deployment scripts.T1562.001 - Impair Defenses: Disable or Modify Tools to disable security software.T1486 - Data Encrypted for Impact is the primary objective, encrypting files for financial gain.T1490 - Inhibit System Recovery by deleting volume shadow copies.The 'democratization' of LockBit has several negative consequences for defenders:
vssadmin delete shadows), disabling of security tools, and rapid, widespread file modification.D3-FCR: File Content Rules and D3-FH: File Hashing to detect known LockBit components. More importantly, use D3-BMA: Behavior-based Malware Analysis to identify ransomware-like actions.Defending against these attacks requires a standard, robust anti-ransomware strategy:
D3-SPP: Strong Password Policy and D3-MFA: Multi-factor Authentication to prevent initial access, with D3-BMA: Behavior-based Malware Analysis for detection.Train users to identify and report phishing, a common initial access vector for ransomware attacks.
Enforce MFA on all remote access points and privileged accounts to prevent unauthorized access.
Mapped D3FEND Techniques:
Since the leaked LockBit builder allows attackers to create countless variants with unique file hashes, signature-based detection is unreliable. The most effective defense is behavior-based analysis. Configure EDR and security tools to detect and block core ransomware behaviors. Key rules to implement include: alerting on any process that attempts to delete Volume Shadow Copies (e.g., via vssadmin.exe or WMI calls), blocking processes that try to terminate or disable known security agents, and triggering a high-severity incident when a process rapidly modifies and renames a large number of files. These behavioral tripwires can detect a LockBit-based attack regardless of how the binary was compiled.
Given the high probability of encountering a LockBit variant, having a robust and tested incident response plan is critical. This plan must include having offline, immutable backups of critical data (the 3-2-1 rule). Regularly test your ability to restore from these backups to ensure they are viable. The plan should also contain playbooks for isolating infected hosts, identifying the initial access vector, and communicating with stakeholders. The proliferation of LockBit variants means that recovery, not just prevention, must be a core tenet of an organization's security strategy. A successful recovery from backups is the only way to guarantee business continuity without paying a ransom.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats