Hive Ransomware

By Ashwin Venugopal -

 







Introduction

Firstly discovered in June, 2021, Hive is affiliate-based ransomware, that targets healthcare facilities, nonprofits, retailers, energy providers, and other sectors worldwide. It has a Ransomware-as-a-service model enabling its affiliates to use Hive as they want. 

They generally uses common ransomware techniques, tactics, and procedures to intrude into their victims' devices, exfiltrate sensitive data, and encrypt business files. Also, phishing emails having malicious attachments, leaking VPN credentials, and exploiting external vulnerabilities, are used by the affiliates to compromise a network. Hive sends a plain-text ransom note threatening to leak the data of their victims on their TOR website 'HiveLeaks' if they do not meet their demands. 

It is believed that Hive is an Russian organization. According to their website, they have targeted institutes from more than 20 countries since its emergence from far west, the USA, to the far east, Japan.

How does it works? 

FBI discovered that these gangs use a variety of TTPs for their attacks. 82% of breaches occurred via phishing tricks, that allowed them to use their malicious attachments to infiltrate critical systems and Remote Desktop Control to move horizontally across the network. 

This ransomware can encrypt critical files, and then distribute two malicious scripts (hive.bat and shadow.bat) for cleanup. After that, they threatens their victims with the leakage of their files on the dark web on HiveLeaks. They always leave a ransom note on each affected directory with the instructions of gaining decryption software. 

They communicate the ransom amount and payment deadline to the victim on live chat. They also negotiate the ransom demands in U.S. dollars, with the initial amount ranging from several thousand dollars to millions. They demand bitcoin payment. 

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