LockBit ransomware takes as little as five minutes to deploy the encryption routine on target systems once it lands on the victim network. LockBit attacks leave few traces for forensic analysis as the malware loads into the system memory, with logs and supporting files removed upon execution. In one case, they found that the attack began from a compromised Internet Information Server that launched a remote PowerShell script calling another script embedded in a remote Google Sheets document. This script connects to a command and control server to retrieve and install a PowerShell module for adding a backdoor and establish persistence. To evade monitoring and go unnoticed in the logs, the attacker renamed copies of PowerShell and the binary for running Microsoft HTML Applications (mshta.exe); this prompted Sophos to call this a “PS Rename“ attack. The backdoor is responsible for installing attack modules and executes a VBScript that downloads and executes a second backdoor on systems restart.
LockBit strives to target different sectors throughout the world and has just rebranded for the second time. Operators and affiliates behind the LockBit ransomware started transitioning to LockBit 3.0 around June 2022. LockBit 3.0, also known as LockBit Black, is active and out there, and the BFSI Sector makes up 1/3rd of its victims. This latest LockBit version has a new extortion model that allows them to purchase stolen data during attacks. Rapid affiliate adoption of LockBit 3.0 has resulted in a large number of victims being identified on the new “Version 3.0” leak sites, a collection of public blogs that identify non-compliant victims and release extracted data.
Image source: (Sentinelone)