Cmb RDP Ransomware

First observed in 2018, Cmb is a new variant of the Dharma ransomware family.

Threat ID:: CC-2597
Category:: Ransomware
Threat Severity:: Medium
Threat Vector:: Insecure network
Published:: 14 August 2018 12:00 AM

Report a cyber attack: call 0300 303 5222 or email [email protected]

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

First observed in 2018, Cmb is a new variant of the Dharma ransomware family.

Affected platforms

The following platforms are known to be affected:

Microsoft Windows

Microsoft Windows - All versions

Threat details

As with most Dharma variants, Cmb is delivered manually over Remote Desktop Protocol services (RDP). The attackers operating Cmb will scan for exposed RDP ports, typically TCP 3389, and attempt brute-force attacks to gain access to the affected device.

Once installed, Cmb will enumerate all local, network and virtual machine host drives before encrypting all non-system files on theses drives and appending them with a new extension.

Remediation steps

Type	Step
	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: Only allow access for authorised RDP users. Enforce strong password policies. Enforce multi-factor authentication. Don't allow RDP access for privileged user accounts. Don’t use generic accounts. Set user accounts with an expiry date. Audit user accounts periodically. Only allow point-to-point connections from specific IP addresses where feasible. Ensure Transport Layer Security (TLS) is up-to-date. Log and monitor all RDP activity and investigate unusual behaviour. Consider only allowing RDP for authorised virtual private network (VPN) connections. Additionally, if a device 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: A robust program of education and awareness training is delivered to users to ensure they don’t open attachments or follow links within unsolicited emails. All operating systems, anti-virus and other security products are kept up to date. All day to day computer activities such as email and internet are performed using non-administrative accounts and that permissions are always assigned based on the principle of least privilege. Your organisation adopts a holistic all-round approach to Cyber Security as advocated by the 10 Steps to Cyber Security. Identifying the source of infection: Identifying the affected device and disconnecting or quarantining it from the network is essential to damage limitation. Users should immediately report infections to their IT support provider, disconnect their network cable and power the computer down. File auditing should be enabled, and file server logs should be monitored to detect signs of unauthorised encryption and allow the source of encryption to be identified (i.e. the infected device). 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. Multiple backups should be created including at least one off-network backup (e.g. to tape). The only guaranteed way to recover from a ransomware infection is to restore all affected files from their most recent backup.

Type

Step

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:

Only allow access for authorised RDP users.
Enforce strong password policies.
Enforce multi-factor authentication.
Don't allow RDP access for privileged user accounts.
Don’t use generic accounts.
Set user accounts with an expiry date.
Audit user accounts periodically.
Only allow point-to-point connections from specific IP addresses where feasible.
Ensure Transport Layer Security (TLS) is up-to-date.
Log and monitor all RDP activity and investigate unusual behaviour.
Consider only allowing RDP for authorised virtual private network (VPN) connections.

Additionally, if a device 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:

A robust program of education and awareness training is delivered to users to ensure they don’t open attachments or follow links within unsolicited emails.
All operating systems, anti-virus and other security products are kept up to date.
All day to day computer activities such as email and internet are performed using non-administrative accounts and that permissions are always assigned based on the principle of least privilege.
Your organisation adopts a holistic all-round approach to Cyber Security as advocated by the 10 Steps to Cyber Security.

Identifying the source of infection:
Identifying the affected device and disconnecting or quarantining it from the network is essential to damage limitation.

Users should immediately report infections to their IT support provider, disconnect their network cable and power the computer down.
File auditing should be enabled, and file server logs should be monitored to detect signs of unauthorised encryption and allow the source of encryption to be identified (i.e. the infected device).

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.

Multiple backups should be created including at least one off-network backup (e.g. to tape).
The only guaranteed way to recover from a ransomware infection is to restore all affected files from their most recent backup.

Last edited: 17 February 2020 12:41 pm