That is why the Federal Bureau of Investigation (FBI), the Cybersecurity and Infrastructure Security Agency (CISA), and the Multi-State Information Sharing & Analysis Center (MS-ISAC) released a joint cybersecurity advisory (CSA) on LockBit 3.0 ransomware indicators of compromise (IoCs) and tactics, techniques, and procedures (TTPs).
LockBit 3.0 ransomware operations function as a Ransomware-as-a-Service (RaaS) model and is a continuation of previous versions of the ransomware, LockBit 2.0, and LockBit.
Since January 2020, LockBit has functioned as an affiliate-based ransomware variant; affiliates deploying the LockBit RaaS use many varying TTPs and attack a wide range of businesses and critical infrastructure organizations, which can make effective computer network defense and mitigation challenging.
Reduce Ransomware Incidents
The FBI, CISA, and the MS-ISAC encourage organizations to work out a plan to reduce the likelihood and impact of ransomware attacks.
LockBit 3.0, also known as “LockBit Black,” is more modular and evasive than its previous versions and shares similarities with Blackmatter and Blackcat ransomware.
LockBit 3.0 is configured upon compilation with many different options that determine the behavior of the ransomware.
Upon the actual execution of the ransomware within a victim environment, various arguments can be supplied to further modify the behavior of the ransomware, according to the advisory.
One case in point is LockBit 3.0 accepts additional arguments for specific operations in lateral movement and rebooting into Safe Mode. If a LockBit affiliate does not have access to passwordless LockBit 3.0 ransomware, then a password argument is mandatory during the execution of the ransomware, according to the advisory.
LockBit 3.0 affiliates failing to enter the correct password will be unable to execute the ransomware. The password is a cryptographic key which decodes the LockBit 3.0 executable.
LockBit 3.0 Details
By protecting the code in such a manner, LockBit 3.0 hinders malware detection and analysis with the code being unexecutable and unreadable in its encrypted form, according to the advisory. Signature-based detections may fail to detect the LockBit 3.0 executable as the executable’s encrypted potion will vary based on the cryptographic key used for encryption while also generating a unique hash.
When provided the correct password, LockBit 3.0 will decrypt the main component, continue to decrypt or decompress its code, and execute the ransomware, according to the advisory.
LockBit 3.0 will only infect machines that do not have language settings matching a defined exclusion list, according to the advisory. However, whether a system language is checked at runtime is determined by a configuration flag originally set at compilation time. Languages on the exclusion list include, but are not limited to, Romanian (Moldova), Arabic (Syria), and Tatar (Russia). If a language from the exclusion list is detected, LockBit 3.0 will stop execution without infecting the system.
Affiliates deploying LockBit 3.0 ransomware gain initial access to victim networks via remote desktop protocol (RDP) exploitation, drive-by compromise, phishing campaigns, abuse of valid accounts, and exploitation of public-facing applications, according to the advisory.
Affiliates deploying LockBit 3.0 ransomware gain initial access to victim networks via remote desktop protocol (RDP) exploitation, drive-by compromise, phishing campaigns, abuse of valid accounts, and exploitation of public-facing applications.
During the malware routine, if privileges are not sufficient, LockBit 3.0 attempts to escalate to the required privileges, according to the advisory. LockBit 3.0 performs functions such as:
- Enumerating system information such as hostname, host configuration, domain information, local drive configuration, remote shares, and mounted external storage devices
- Terminating processes and services
- Launching commands
- Enabling automatic logon for persistence and privilege escalation
- Deleting log files, files in the recycle bin folder, and shadow copies residing on disk
Spread Across Network
LockBit 3.0 attempts to spread across a victim network by using a preconfigured list of credentials hardcoded at compilation time or a compromised local account with elevated privileges, according to the advisory. When compiled, LockBit 3.0 may also enable options for spreading via Group Policy Objects and PsExec using the Server Message Block (SMB) protocol. LockBit 3.0 attempts to encrypt data saved to any local or remote device, but skips files associated with core system functions.
After files are encrypted, LockBit 3.0 drops a ransom note with the new filename .README.txt and changes the host’s wallpaper and icons to LockBit 3.0 branding, according to the advisory. If needed, LockBit 3.0 will send encrypted host and bot information to a command and control (C2) server.
Once completed, LockBit 3.0 may delete itself from the disk as well as any Group Policy updates that were made, depending on which options were set at compilation time.
LockBit 3.0 affiliates use Stealbit, a custom exfiltration tool used previously with LockBit 2.0; rclone, an open-source command line cloud storage manager; and publicly available file sharing services, such as MEGA, to exfiltrate sensitive company data files prior to encryption, according to the advisory. While rclone and many publicly available file sharing services are primarily used for legitimate purposes, they can also end up used by threat actors to aid in system compromise, network exploration, or data exfiltration. LockBit 3.0 affiliates often use other publicly available file sharing services to exfiltrate data as well.
Actions to take to mitigate cyber threats from ransomware:
- Prioritize remediating known exploited vulnerabilities
- Train users to recognize and report phishing attempts
- Enable and enforce phishing- resistant multifactor authentication
Click here for more information on the LockBit 3.0 ransomware CSA.

