LockCrypt Ransomware
This content has been archived
This article no longer conforms to NHS Digital's standards for cyber alerts, and may contain outdated or inaccurate information. Use of this information contained in this page is at your own risk
Summary
Threat details
The creators of the malware are manually infecting devices using an RDP brute-force attack performed on compromised servers. Once they have access to a system they terminate all non-core processes before deploying LockCrypt to ensure maximum damage.
LockCrypt encrypts files with .lock extension before installing itself and deleting backups or shadow volumes to prevent easy recovery. Once a system is encrypted the malware sends base64 encoded information to a command & control server in Iran.
Threat updates
| Date | Update |
|---|---|
| 23 Nov 2017 |
Further details concerning the techniques used to deliver the malware have come to light. The RDP brute-force uses a tool called NLBrute to automate the attack. Low-level administration software, such as the Process Hacker tool, are then used to disable AV and database services before removing Volume Shadow Copies. The ransomware is then loaded and run on the unprotected system. |
Remediation steps
| Type | Step |
|---|---|
|
If a computer on your network becomes infected with ransomware it will begin encrypting local machine files and files on any network the logged-in user has permission to access. For system administration accounts this may include backup storage locations. To avoid becoming infected with ransomware, ensure that:
Identifying the source of infection: Identifying the infected machine and unplugging / disconnecting or quarantining it from the network is essential to damage limitation.
To limit the damage of ransomware and enable recovery: All critical data must be backed up, and these backups must be sufficiently protected/kept out of reach of ransomware.
The only guaranteed way to recover from a ransomware infection is to restore all affected files from their most recent backup. Additionally, if Remote Desktop Protocol (RDP) is not used then ensure port 3389 (TCP/UDP) is blocked at your internet firewall. If RDP is used, then:
|
Last edited: 17 February 2020 11:33 am