Ransomware Cuba

By Ashwin Venugopal -

 



About Cuba Ransomware

Russia-based Cuba ransomware is one of the world's most profitable ransomware outfits. It mainly targets USA and its organizations.  It was discovered in 2019. According to data, this threat group have compromised 101 entities (65 in the US and 36 elsewhere) till now. They have already demanded a total of $145 million in ransom payments and received around $60 million. It is affiliated with the small but disproportionately high-impact threat actors RomCom and Industrial Spy. 

Cuba uses less sophisticated standard commercial software packing techniques confirming it to be a product of a small but talented group of profit-seeking individuals. It is deployed selectively via a big game hunting strategy. It generally targets some high-profile financial services organizations, government sector, healthcare sector, critical infrastructure and IT sector. 

Reportedly, Cuba operators delivers decryption packages to decrypt the files of a victims when the said ransom is paid. However, for those who refuse to pay the ransom, they use double-extortion tactic and can also publish the stolen data and documents after the refusal.

How does Cuba attacks?

When Cuba was first discovered, there was no evidence of any prior failed login attempts or any kind of brute-forcing or exploitation of vulnerabilities. However, researchers from BlackBerry found out that these threat actors had previously used initial access brokers to obtain credentials. 

After intruding the network, Cuba deploys its own custom-made downloader, BUGHATCH. This downloader then connects to a command-and-control (C2) server and starts downloading the attacker's payload. 

Cuba also uses another interesting malware named BURNTCIGAR, which can carry out Bring Your Own Vulnerable Driver (BYVOD) attacks. This one can easily exploit the input-output control codes to terminate kernel-level processes en masse. BURNTCIGAR has eliminated more than 200 processes associated with anti-malware endpoint products. 

Cuba is also known for stealthily covering its tracks inside a network for more than two months before taking out anti-malware and endpoint protections. 

Prevention

General methods to combat a ransomware attack are as follows-
  • Mandatory strong password policies and multi-factor authentication for all critical services.
  • Use updated or modern Identity and Access Management (IAM) tools.
  • Employ advanced endpoint security products on all endpoints.
  • Regularly update all the software and operating systems. 
  • Have the least privilege approach to security, including the removal of all the unnecessary access to administrative shares and other services.
  • Administer a solid backup strategy including offline, encrypted, and immutable backup of data.


























































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more