Threat Signal Report

Alert (AA22-321A): #StopRansomware: Hive Ransomware

description-logo Description

FortiGuard Labs is aware of that the Federal Bureau of Investigation (FBI), the Cybersecurity and Infrastructure Security Agency (CISA), and the Department of Health and Human Services (HHS) released a joint advisory for Hive ransomware as part of their #StopRansomware effort. Hive ransomware is a Ransomware-as-a-Service (RaaS) consisting of developers and affiliates. It attempts to steal data, encrypt files on victims' machines, and demand ransom recover affected files and prevent stolen data from being published to their data leak site, called "HiveLeaks," on the DarkWeb.

Why is this Significant?

This is significant because Hive is a Ransomware-as-a-Service (RaaS) that, according to the advisory, has victimized more than 1,300 enterprises globally and extorted 100 million US dollars. The group has been active since June 2021 and did not only target private enterprises but also essential industries such as government organizations and healthcare services.

What is Hive Ransomware?

Hive is a Ransomware-as-a-Service (RaaS) consisting of two groups: developers and affiliates. Hive developers create, maintain, and update Hive ransomware and infrastructures such date leak site named "HiveLeaks" and negotiant site. Hive affiliates are responsible for finding and infecting victims, exfiltrating files, and deploying Hive ransomware to the victims' network.

The latest Hive ransomware iterations are written in the Rust programing language. Older variants are written in Go.

Reported initial infection vectors include emails, exploiting vulnerabilities such as CVE-2020-12812, CVE-2021-31207, CVE-2021-34473 and CVE-2021-34523.

Hive ransomware encrypts files on victims' machines and typically appends a ".hive" file extension to the affected files. It also drops a ransom note named "HOW_TO_DECRYPT.txt", which instructs victims to visit a negotiation site on TOR.

The advisory states that Hive ransomware is known to victimize organizations that were previously infected with Hive ransomware and recovered without paying ransom.

What is the Status of Protection?

FortiGuard Labs provides the following AV signatures for recent Hive ransomware samples that we collected:

  • W32/Filecoder_Hive.A!tr.ransom
  • W32/Filecoder_Hive.B!tr.ransom
  • W32/Hive.4a4e!tr.ransom
  • W32/Hive.B0FF!tr.ransom
  • W32/Hive.d10e!tr.ransom
  • W32/Hive.FD38!tr.ransom
  • W64/Filecoder.AW!tr.ransom
  • W64/Filecoder_Hive.A!tr.ransom
  • W64/Filecoder_Hive.B!tr.ransom
  • W64/Hive.31ec!tr.ransom
  • W64/Hive.6bcb!tr.ransom
  • W64/Hive.71de!tr.ransom
  • W64/Hive.7cec!tr.ransom
  • W64/Hive.933c!tr.ransom
  • W64/Hive.A!tr
  • W64/Hive.B0FF!tr.ransom
  • W64/Hive.c2e4!tr.ransom
  • W64/Hive.e550!tr.ransom
  • W64/Hive.ea51!tr.ransom
  • W32/Filecoder.507F!tr.ransom
  • W32/Agent.0b0f!tr.ransom
  • W32/Agent.32a5!tr.ransom
  • W32/Agent.65e3!tr.ransom
  • W32/Agent.69ce!tr.ransom
  • W32/Agent.6d49!tr.ransom
  • W32/Agent.7c49!tr.ransom
  • W64/Agent.U!tr

All network IOCs on the advisory are blocked by Webfiltering.

FortiGuard Labs provides the following IPS signatures for the vulnerabilities reportedly exploited as initial infection vector by Hive threat actors:

  • MS.Exchange.MailboxExportRequest.Arbitrary.File.Write (CVE-2021-31207)
  • MS.Exchange.Server.Autodiscover.Remote.Code.Execution (CVE-2021-34473)
  • MS.Exchange.Server.Common.Access.Token.Privilege.Elevation (CVE-2021-34523)


Traffic Light Protocol

Color When Should it Be used? How may it be shared?


Not for disclosure, restricted to participants only.
Sources may use TLP:RED when information cannot be effectively acted upon by additional parties, and could lead to impacts on a party's privacy, reputation, or operations if misused. Recipients may not share TLP:RED information with any parties outside of the specific exchange, meeting, or conversation in which it was originally disclosed. In the context of a meeting, for example, TLP:RED information is limited to those present at the meeting. In most circumstances, TLP:RED should be exchanged verbally or in person.


Limited disclosure, restricted to participants’ organizations.
Sources may use TLP:AMBER when information requires support to be effectively acted upon, yet carries risks to privacy, reputation, or operations if shared outside of the organizations involved. Recipients may only share TLP:AMBER information with members of their own organization, and with clients or customers who need to know the information to protect themselves or prevent further harm. Sources are at liberty to specify additional intended limits of the sharing: these must be adhered to.


Limited disclosure, restricted to the community.
Sources may use TLP:GREEN when information is useful for the awareness of all participating organizations as well as with peers within the broader community or sector. Recipients may share TLP:GREEN information with peers and partner organizations within their sector or community, but not via publicly accessible channels. Information in this category can be circulated widely within a particular community. TLP:GREEN information may not be released outside of the community.


Disclosure is not limited.
Sources may use TLP:WHITE when information carries minimal or no foreseeable risk of misuse, in accordance with applicable rules and procedures for public release. Subject to standard copyright rules, TLP:WHITE information may be distributed without restriction.