Blog
/
Network
/
May 23, 2023

Darktrace’s Detection of a Hive Ransomware-as-Service

This blog investigates a new strain of ransomware, Hive, a ransomware-as-a-service. Darktrace was able to provide full visibility over the attacks.
Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
Written by
Emily Megan Lim
Cyber Analyst
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
23
May 2023

Update: On January 26, 2023, the Hive ransomware group was dismantled and servers associated with the sale of the ransomware were taken offline following an investigation by the FBI, German law enforcement and the National Crime Agency (NCA). The activity detailed in this blog took place in 2022, whilst the group was still active.

RaaS in Cyber Security

The threat of ransomware continues to be a constant concern for security teams across the cyber threat landscape. With the growing popularity of Ransomware-as-a-Service (RaaS), it is becoming more and more accessible for even inexperienced would-be attackers. As a result of this low barrier to entry, the volume of ransomware attacks is expected to increase significantly.

What’s more, RaaS is a highly tailorable market in which buyers can choose from varied kits and features to use in their ransomware deployments meaning attacks will rarely behave the same. To effectively detect and safeguard against these differentiations, it is crucial to implement security measures that put the emphasis on detecting anomalies and focusing on deviations in expected behavior, rather than relying on depreciated indicators of compromise (IoC) lists or playbooks that focus on attack chains unable to keep pace with the increasing speed of ransomware evolution.

In early 2022, Darktrace DETECT/Network™ identified several instances of Hive ransomware on the networks of multiple customers. Using its anomaly-based detection, Darktrace was able to successfully detect the attacks and multiple stages of the kill chain, including command and control (C2) activity, lateral movement, data exfiltration, and ultimately data encryption and the writing of ransom notes.

Hive Ransomware 

Hive ransomware is a relatively new strain that was first observed in the wild in June 2021. It is known to target a variety of industries including healthcare, energy providers, and retailers, and has reportedly attacked over 1,500 organizations, collecting more than USD 100m in ransom payments [1].

Hive is distributed via a RaaS model where its developers update and maintain the code, in return for a percentage of the eventual ransom payment, while users (or affiliates) are given the tools to carry out attacks using a highly sophisticated and complex malware they would otherwise be unable to use. Hive uses typical tactics, techniques and procedures (TTPs) associated with ransomware, though they do vary depending on the Hive affiliate carrying out the attack.

In most cases a double extortion attack is carried out, whereby data is first exfiltrated and then encrypted before a ransom demand is made. This gives attackers extra leverage as victims are at risk of having their sensitive data leaked to the public on websites such as the ‘HiveLeaks’ TOR website.

Attack Timeline

Owing to the highly customizable nature of RaaS, the tactics and methods employed by Hive actors are expected to differ on a case-by-case basis. Nonetheless in the majority of Hive ransomware incidents identified on Darktrace customer environments, Darktrace DETECT observed the following general attack stages and features. This is possibly indicative of the attacks originating from the same threat actor(s) or from a widely sold batch with a particular configuration to a variety of actors.

Figure 1: A typical timeline of a Hive attack observed by Darktrace.

Initial Access 

Although Hive actors are known to gain initial access to networks through multiple different vectors, the two primary methods reported by security researchers are the exploitation of Microsoft Exchange vulnerabilities, or the distribution of phishing emails with malicious attachments [2][3].

In the early stages of one Hive ransomware attack observed on the network of a Darktrace customer, for example, Darktrace detected a device connecting to the rare external location 23.81.246[.]84, with a PowerShell user agent via HTTP. During this connection, the device attempted to download an executable file named “file.exe”. It is possible that the file was initially accessed and delivered via a phishing email; however, as Darktrace/Email was not enabled at the time of the attack, this was outside of Darktrace’s purview. Fortunately, the connection failed the proxy authentication was thus blocked as seen in the packet capture (PCAP) in Figure 2. 

Shortly after this attempted download, the same device started to receive a high volume of incoming SSL connections from a rare external endpoint, namely 146.70.87[.]132. Darktrace logged that this endpoint was using an SSL certificate signed by Go Daddy CA, an easily obtainable and accessible SSL certificate, and that the increase in incoming SSL connections from this endpoint was unusual behavior for this device. 

It is likely that this highly anomalous activity detected by Darktrace indicates when the ransomware attack began, likely initial payload download.  

Darktrace DETECT models:

  • Anomalous Connection / Powershell to Rare External
  • Anomalous Server Activity / New Internet Facing System
Figure 2: PCAP of the HTTP connection to the rare endpoint 23.81.246[.]84 showing the failed proxy authentication.

C2 Beaconing 

Following the successful initial access, Hive actors begin to establish their C2 infrastructure on infected networks through numerous connections to C2 servers, and the download of additional stagers. 

On customer networks infected by Hive ransomware, Darktrace identified devices initiating a high volume of connections to multiple rare endpoints. This very likely represented C2 beaconing to the attacker’s infrastructure. In one particular example, further open-source intelligence (OSINT) investigation revealed that these endpoints were associated with Cobalt Strike.

Darktrace DETECT models:

  • Anomalous Connection / Multiple Connections to New External TCP
  • Anomalous Server Activity / Anomalous External Activity from Critical Network Device
  • Compromise / High Volume of Connections with Beacon Score
  • Compromise / Sustained SSL or HTTP Increase
  • Compromise / Suspicious HTTP Beacons to Dotted Quad 
  • Compromise / SSL or HTTP Beacon
  • Device / Lateral Movement and C2 Activity

Internal Reconnaissance, Lateral Movement and Privilege Escalation

After C2 infrastructure has been established, Hive actors typically begin to uninstall antivirus products in an attempt to remain undetected on the network [3]. They also perform internal reconnaissance to look for vulnerabilities and open channels and attempt to move laterally throughout the network.

Amid the C2 connections, Darktrace was able to detect network scanning activity associated with the attack when a device on one customer network was observed initiating an unusually high volume of connections to other internal devices. A critical network device was also seen writing an executable file “mimikatz.exe” via SMB which appears to be the Mimikatz attack tool commonly used for credential harvesting. 

There were also several detections of lateral movement attempts via RDP and DCE-RPC where the attackers successfully authenticated using an “Administrator” credential. In one instance, a device was also observed performing ITaskScheduler activity. This service is used to remotely control tasks running on machines and is commonly observed as part of malicious lateral movement activity. Darktrace DETECT understood that the above activity represented a deviation from the devices’ normal pattern of behavior and the following models were breached:

Darktrace DETECT models:

  • Anomalous Connection / Anomalous DRSGetNCChanges Operation
  • Anomalous Connection / New or Uncommon Service Control
  • Anomalous Connection / Unusual Admin RDP Session
  • Anomalous Connection / Unusual SMB Version 1 Connectivity
  • Compliance / SMB Drive Write
  • Device / Anomalous ITaskScheduler Activity
  • Device / Attack and Recon Tools
  • Device / Attack and Recon Tools In SMB
  • Device / EXE Files Distributed to Multiple Devices
  • Device / Suspicious Network Scan Activity
  • Device / Increase in New RPC Services
  • User / New Admin Credentials on Server

Data Exfiltration

At this stage of the attack, Hive actors have been known to carry out data exfiltration activity on infected networks using a variety of different methods. The Cybersecurity & Infrastructure Security Agency (CISA) reported that “Hive actors exfiltrate data likely using a combination of Rclone and the cloud storage service Mega[.]nz” [4]. Darktrace DETECT identified an example of this when a device on one customer network was observed making HTTP connections to endpoints related to Mega, including “w.apa.mega.co[.]nz”, with the user agent “rclone/v1.57.0” with at least 3 GiB of data being transferred externally (Figure 3). The same device was also observed transferring at least 3.6 GiB of data via SSL to the rare external IP, 158.51.85[.]157.

Figure 3: A summary of a device’s external connections to multiple endpoints and the respective amounts of data exfiltrated to Mega storage endpoints.

In another case, a device was observed uploading over 16 GiB of data to a rare external endpoint 93.115.27[.]71 over SSH. The endpoint in question was seen in earlier beaconing activity suggesting that this was likely an exfiltration event. 

However, Hive ransomware, like any other RaaS kit, can differ greatly in its techniques and features, and it is important to note that data exfiltration may not always be present in a Hive ransomware attack. In one incident detected by Darktrace, there were no signs of any data leaving the customer environment, indicating data exfiltration was not part of the Hive actor’s objectives.

Darktrace DETECT models:

  • Anomalous Connection / Data Sent to Rare Domain
  • Anomalous Connection / Lots of New Connections
  • Anomalous Connection / Multiple HTTP POSTs to Rare Hostname
  • Anomalous Connection / Suspicious Self-Signed SSL
  • Anomalous Connection / Uncommon 1 GiB Outbound
  • Device / New User Agent and New IP
  • Unusual Activity / Unusual External Data to New Endpoints
  • Unusual Activity / Unusual External Data Transfer
  • Unusual Activity / Enhanced Unusual External Data Transfer

Ransomware Deployment

In the final stage of a typical Hive ransomware attack, the ransomware payload is deployed and begins to encrypt files on infected devices. On one customer network, Darktrace detected several devices connecting to domain controllers (DC) to read a file named “xxx.exe”. Several sources have linked this file name with the Hive ransomware payload [5].

In another example, Darktrace DETECT observed multiple devices downloading the executable files “nua64.exe” and “nua64.dll” from a rare external location, 194.156.90[.]25. OSINT investigation revealed that the files are associated with Hive ransomware.

Figure 4: Security vendor analysis of the malicious file hash [6] associated with Hive ransomware. 

Shortly after the download of this executable, multiple devices were observed performing an unusual amount of file encryption, appending randomly generated strings of characters to file extensions. 

Although it has been reported that earlier versions of Hive ransomware encrypted files with a “.hive” extension [7], Darktrace observed across multiple customers that encrypted files had extensions that were partially-randomized, but consistently 20 characters long, matching the regular expression “[a-zA-Z0-9\-\_]{8}[\-\_]{1}[A-Za-z0-9\-\_]{11}”.

Figure 5: Device Event Log showing SMB reads and writes of encrypted files with a randomly generated extension of 20 characters. 

Following the successful encryption of files, Hive proceeds to drop a ransom note, named “HOW_TO_DECRYPT.txt”, into each affected directory. Typically, the ransom note will contain a link to Hive’s “sales department” and, in the event that exfiltration took place, a link to the “HiveLeaks” site, where attackers threaten to publish exfiltrated data if their demands are not met (Figure 6).  In cases of Hive ransomware detected by Darktrace, multiple devices were observed attempting to contact “HiveLeaks” TOR domains, suggesting that endpoint users had followed links provided to them in ransom notes.

Figure 6: Sample of a Hive ransom note [4].

Examples of file extensions:

  • 36C-AT9-_wm82GvBoCPC
  • 36C-AT9--y6Z1G-RFHDT
  • 36C-AT9-_x2x7FctFJ_q
  • 36C-AT9-_zK16HRC3QiL
  • 8KAIgoDP-wkQ5gnYGhrd
  • kPemi_iF_11GRoa9vb29
  • kPemi_iF_0RERIS1m7x8
  • kPemi_iF_7u7e5zp6enp
  • kPemi_iF_y4u7pB3d3f3
  • U-9Xb0-k__T0U9NJPz-_
  • U-9Xb0-k_6SkA8Njo5pa
  • zm4RoSR1_5HMd_r4a5a9 

Darktrace DETECT models:

  • Anomalous Connection / SMB Enumeration
  • Anomalous Connection / Sustained MIME Type Conversion
  • Anomalous Connection / Unusual Admin SMB Session
  • Anomalous File / Internal / Additional Extension Appended to SMB File
  • Compliance / SMB Drive Write
  • Compromise / Ransomware / Suspicious SMB Activity
  • Compromise / Ransomware / Ransom or Offensive Words Written to SMB
  • Compromise / Ransomware / Possible Ransom Note Write
  • Compromise / High Priority Tor2Web
  • Compromise / Tor2Web
  • Device / EXE Files Distributed to Multiple Devices

Conclusion

As Hive ransomware attacks are carried out by different affiliates using varying deployment kits, the tactics employed tend to vary and new IoCs are regularly identified. Furthermore, in 2022 a new variant of Hive was written using the Rust programming language. This represented a major upgrade to Hive, improving its defense evasion techniques and making it even harder to detect [8]. 

Hive is just one of many RaaS offerings currently on the market, and this market is only expected to grow in usage and diversity of presentations.  As ransomware becomes more accessible and easier to deploy it is essential for organizations to adopt efficient security measures to identify ransomware at the earliest possible stage. 

Darktrace DETECT’s Self-Learning AI understands customer networks and learns the expected patterns of behavior across an organization’s digital estate. Using its anomaly-based detection Darktrace is able to identify emerging threats through the detection of unusual or unexpected behavior, without relying on rules and signatures, or known IoCs. 

Credit to: Emily Megan Lim, Cyber Analyst, Hyeongyung Yeom, Senior Cyber Analyst & Analyst Team Lead.

Appendices

MITRE AT&CK Mapping

Reconnaissance

T1595.001 – Scanning IP Blocks

T1595.002 – Vulnerability Scanning

Resource Development

T1583.006 – Web Services

Initial Access

T1078 – Valid Accounts

T1190 – Exploit Public-Facing Application

T1200 – Hardware Additions

Execution

T1053.005 – Scheduled Task

T1059.001 – PowerShell

Persistence/Privilege Escalation

T1053.005 – Scheduled Task

T1078 – Valid Accounts

Defense Evasion

T1078 – Valid Accounts

T1207 – Rogue Domain Controller

T1550.002 – Pass the Hash

Discovery

T1018 – Remote System Discovery

T1046 – Network Service Discovery

T1083 – File and Directory Discovery

T1135 – Network Share Discovery

Lateral Movement

T1021.001 – Remote Desktop Protocol

T1021.002 – SMB/Windows Admin Shares

T1021.003 – Distributed Component Object Model

T1080 – Taint Shared Content

T1210 – Exploitation of Remote Services

T1550.002 – Pass the Hash

T1570 – Lateral Tool Transfer

Collection

T1185 – Man in the Browser

Command and Control

T1001 – Data Obfuscation

T1071 – Application Layer Protocol

T1071.001 – Web Protocols

T1090.003 – Multi-hop proxy

T1095 – Non-Application Layer Protocol

T1102.003 – One-Way Communication

T1571 – Non-Standard Port

Exfiltration

T1041 – Exfiltration Over C2 Channel

T1567.002 – Exfiltration to Cloud Storage

Impact

T1486 – Data Encrypted for Impact

T1489 – Service Stop

List of IoCs 

23.81.246[.]84 - IP Address - Likely Malicious File Download Endpoint

146.70.87[.]132 - IP Address - Possible Ransomware Endpoint

5.199.162[.]220 - IP Address - C2 Endpoint

23.227.178[.]65 - IP Address - C2 Endpoint

46.166.161[.]68 - IP Address - C2 Endpoint

46.166.161[.]93 - IP Address - C2 Endpoint

93.115.25[.]139 - IP Address - C2 Endpoint

185.150.1117[.]189 - IP Address - C2 Endpoint

192.53.123[.]202 - IP Address - C2 Endpoint

209.133.223[.]164 - IP Address - Likely C2 Endpoint

cltrixworkspace1[.]com - Domain - C2 Endpoint

vpnupdaters[.]com - Domain - C2 Endpoint

93.115.27[.]71 - IP Address - Possible Exfiltration Endpoint

158.51.85[.]157 - IP Address - Possible Exfiltration Endpoint

w.api.mega.co[.]nz - Domain - Possible Exfiltration Endpoint

*.userstorage.mega.co[.]nz - Domain - Possible Exfiltration Endpoint

741cc67d2e75b6048e96db9d9e2e78bb9a327e87 - SHA1 Hash - Hive Ransomware File

2f9da37641b204ef2645661df9f075005e2295a5 - SHA1 Hash - Likely Hive Ransomware File

hiveleakdbtnp76ulyhi52eag6c6tyc3xw7ez7iqy6wc34gd2nekazyd[.]onion - TOR Domain - Likely Hive Endpoint

References

[1] https://www.justice.gov/opa/pr/us-department-justice-disrupts-hive-ransomware-variant

[2] https://www.varonis.com/blog/hive-ransomware-analysis

[3] https://www.trendmicro.com/vinfo/us/security/news/ransomware-spotlight/ransomware-spotlight-hive 

[4]https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-321a

[5] https://www.trendmicro.com/en_us/research/22/c/nokoyawa-ransomware-possibly-related-to-hive-.html

[6] https://www.virustotal.com/gui/file/60f6a63e366e6729e97949622abd9de6d7988bba66f85a4ac8a52f99d3cb4764/detection

[7] https://heimdalsecurity.com/blog/what-is-hive-ransomware/

[8] https://www.microsoft.com/en-us/security/blog/2022/07/05/hive-ransomware-gets-upgrades-in-rust/ 

Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
Written by
Emily Megan Lim
Cyber Analyst

More in this series

No items found.

Blog

/

/

May 19, 2026

State of AI Cybersecurity 2026: 77% of security stacks include AI, but trust is lagging

Default blog imageDefault blog image

Findings in this blog are taken from Darktrace’s annual State of AI Cybersecurity Report 2026.

AI is a contributing member of nearly every modern cybersecurity team. As we discussed earlier in this blog series, rapid AI adoption is expanding the attack surface in ways that security professionals have never before experienced while also empowering attackers to operate at unprecedented speed and scale. It’s only logical that defenders are harnessing the power of AI to fight back.

After all, AI can help cybersecurity teams spot the subtle signs of novel threats before humans can, investigate events more quickly and thoroughly, and automate response. But although AI has been widely adopted, this technology is also frequently misunderstood, and occasionally viewed with suspicion.

For CISOs, the cybersecurity marketplace can be noisy. Making sense of competing vendors’ claims to distinguish the solutions that truly deliver on AI’s full potential from those that do not isn’t always easy. Without a nuanced understanding of the different types of AI used across the cybersecurity stack, it is difficult to make informed decisions about which vendors to work with or how to gain the most value from their solutions. Many security leaders are turning to Managed Security Service Providers (MSSPs) for guidance and support.

The right kinds of AI in the right places?

Back in 2024, when we first conducted this annual survey, more than a quarter of respondents were only vaguely familiar with generative AI or hadn’t heard of it at all. Today, GenAI plays a role in 77% of security stacks. This percentage marks a rapid increase in both awareness and adoption over a relatively short period of time.

According to security professionals, different types of AI are widely integrated into cybersecurity tooling:

  • 67% report that their organization’s security stack uses supervised machine learning
  • 67% report that theirs uses agentic AI
  • 58% report that theirs uses natural language processing (NLP)
  • 35% report that theirs uses unsupervised machine learning

But their responses suggest that organizations aren’t always using the most valuable types of AI for the most relevant use cases.

Despite all the recent attention AI has gotten, supervised machine learning isn’t new. Cybersecurity vendors have been experimenting with models trained on hand-labeled datasets for over a decade. These systems are fed large numbers of examples of malicious activity – for instance, strains of ransomware – and use these examples to generalize common indicators of maliciousness – such as the TTPs of multiple known ransomware strains – so that the models can identify similar attacks in the future. This approach is more effective than signature-based detection, since it isn’t tied to an individual byte sequence or file hash. However, supervised machine learning models can miss patterns or features outside the training data set. When adversarial behavior shifts, these systems can’t easily pivot.

Unsupervised machine learning, by contrast, can identify key patterns and trends in unlabeled data without human input. This enables it to classify information independently and detect anomalies without needing to be taught about past threats. Unsupervised learning can continuously learn about an environment and adapt in real time.

One key distinction between supervised and unsupervised machine learning is that supervised learning algorithms require periodic updating and re-training, whereas unsupervised machine learning trains itself while it works.

The question of trust

Even as AI moves into the mainstream, security professionals are eyeing it with a mix of enthusiasm and caution. Although 89% say they have good visibility into the reasoning behind AI-generated outputs, 74% are limiting AI’s ability to take autonomous action in their SOC until explainability improves. 86% do not allow AI to take even small remediation actions without human oversight.

This model, commonly known as “human in the loop,” is currently the norm across the industry. It seems like a best-of-both-worlds approach that allows teams to experience the benefits of AI-accelerated response without relinquishing control – or needing to trust an AI system.

Keeping humans somewhat in the loop is essential for getting the best out of AI. Analysts will always need to review alerts, make judgement calls, and set guardrails for AI's behavior. Their input helps AI models better understand what “normal” looks like, improving their accuracy over time.

However, relying on human confirmation has real costs – it delays response, increases the cognitive burden analysts must bear, and creates potential coverage gaps when security teams are overwhelmed or unavailable. The traditional model, in which humans monitor and act on every alert, is no longer workable at scale.

If organizations depend too heavily on in-the-loop humans, they risk recreating the very problem AI is meant to solve: backlogs of alerts waiting for analyst review. Removing the human from the loop can buy back valuable time, which analysts can then invest in building a proactive security posture. They can also focus more closely on the most critical incidents, where human attention is truly needed.

Allowing AI to operate autonomously requires trust in its decision-making. This trust can be built gradually over time, with autonomous operations expanding as trust grows. But it also requires knowledge and understanding of AI — what it is, how it works, and how best to deploy it at enterprise scale.

Looking for help in all the right places

To gain access to these capabilities in a way that’s efficient and scalable, growing numbers of security leaders are looking for outsourced support. In fact, 85% of security professionals prefer to obtain new SOC capabilities in the form of a managed service.

This makes sense: Managed Security Service Providers (MSSPs) can deliver deep, continuously available expertise without the cost and complexity of building an in-house team. Outsourcing also allows organizations to scale security coverage up or down as needs change, stay current with evolving threats and regulatory requirements, and leverage AI-native detection and response without needing to manage the AI tools themselves.

Preferences for MSSP-delivered security operations are particularly strong in the education, energy (87%), and healthcare sectors. This makes sense: all are high-value targets for threat actors, and all tend to have limited cybersecurity budgets, so the need for a partner who can deliver affordable access to expertise at scale is strong. Retailers also voiced a strong preference for MSSP-delivered services. These companies are tasked with managing large volumes of consumer personal and financial data, and with transforming an industry traditionally thought of as a late adopter to a vanguard of cyber defense. Technology companies, too, have a marked preference for SOC capabilities delivered by MSSPs. This may simply be because they understand the complexity of the threat landscape – and the advantages of specialized expertise — so well.

In order to help as many organizations as possible – from major enterprises to small and midmarket companies – benefit from enterprise-grade, AI-native security, Darktrace is making it easier for MSSPs to deliver its technology. The ActiveAI Security Portal introduces an alert dashboard designed to increase the speed and efficiency of alert triage, while a new AI-powered managed email security solution is giving MSSPs an edge in the never-ending fight against advanced phishing attacks – helping partners as well as organizations succeed on the frontlines of cyber defense.

Explore the full State of AI Cybersecurity 2026 report for deeper insights into how security leaders are responding to AI-driven risks.

Learn more about securing AI in your enterprise.

[related-resource]

Continue reading
About the author
The Darktrace Community

Blog

/

Network

/

May 19, 2026

When Open Source Is Weaponized: Analysis of a Trojanized 7 Zip Installer

7 zip installerDefault blog imageDefault blog image

Background of the malicious 7-Zip installer, and assessing its Impact

Early in 2026, external researchers disclosed a malicious distribution campaign leveraging a trojanized installer masquerading itself as a legitimate 7‑Zip utility. Evidence suggests the campaign was active as of January 2026, during which victims were served a fake installer from 7zip[.]com, a highly convincing typo-squatted domain impersonating the official 7‑Zip distribution site (7-zip[.]org).

Initial access is typically achieved through social engineering and search‑engine abuse, including YouTube tutorial content that explicitly referenced the impersonated domain as the download source. Notably, several reports observed the installer delivered a modified but functional build of 7‑Zip (7zfm.exe) to reduce suspicion and preserve expected user behavior.

However, the installer also dropped additional payloads, such as Uphero.exe, hero.exe, and hero.dll, which are not part of the legitimate 7‑Zip software package. Once installed and executed, these payloads allow the attacker to establish persistence and configure the infected host as a proxy node under their control. This facilitates malicious activities such as traffic relaying, anonymizing infrastructure, and the delivery of secondary payloads [1] [2].

Overall, this attack illustrates a proxyware-style attack that abuses implicit trust in widely deployed third‑party tools while exploiting unconventional delivery vectors such as instructional media. By closely imitating legitimate software behavior and branding, the threat actors significantly reduced user suspicion and increased the likelihood of widespread, undetected compromise.

Threat overview

Darktrace observed multiple customers affected by the malicious 7‑Zip installer between January 12 and January 22, impacting organizations across the Americas (AMS), Asia‑Pacific & Japan (APJ), and Europe, the Middle East, and Africa (EMEA) regions. The activity targeted customers across various sectors, including Human health and social work activities, Manufacturing, Education, and Information and communication.

The following use case highlights a device on one customer network making external connections associated with malicious 7-Zip update activity observed between  January 7 and January 18, 2026.  This behavior included connectivity to the malicious domain 7zip[.]com, followed by command-and control (C2) activity involving "smshero"-themed domains, as well as outbound proxy connections over ports 1000 and 1002.  

Initial Connectivity to 'update[.]7zip[.]com':

Initial Beaconing to Young Endpoint alert behavior, involving the known tunnel/proxy endpoint ‘79.127.221[.]47’.
Figure 1: Initial Beaconing to Young Endpoint alert behavior, involving the known tunnel/proxy endpoint ‘79.127.221[.]47’.

Starting on January 7, Darktrace / NETWORK detected the device making repeated beaconing connections to the endpoint 79.127.221[.]47 over the destination port 1000. The use of this port aligns with open-source intelligence (OSINT) reporting that hero[.]exe establishes outbound proxy connections via non-standard ports such as 1000 and 1002 [1].

Darktrace observed TLS beaconing alerts to the known trojanized installer, update[.]7zip[.]com · 98.96.229[.]19, over port 443 on January 7th.
Figure 2: Darktrace observed TLS beaconing alerts to the known trojanized installer, update[.]7zip[.]com · 98.96.229[.]19, over port 443 on January 7th.

Later the same day, the device initiated TLS beaconing to the endpoint update.7zip[.]com. This is more than likely a common source of compromise, where victims unknowingly installed a modified build of the tool alongside additional malicious components. The campaign then progressed into the next attack phase, marked by established connectivity to various C2 domains.

Beaconing Activity to "smshero"-themed domains

Darktrace subsequently observed the same infected device connecting to various C2 domains used to retrieve configuration data. As such, these external hostnames were themed around the string “smshero”, for example ‘smshero[.]co’.

On January 8th, Darktrace observed SSL beaconing to a rare destination which was attributed to a known ‘config/control domain’, nova[.]smshero[.]ai.
Figure 3: On January 8th, Darktrace observed SSL beaconing to a rare destination which was attributed to a known ‘config/control domain’, nova[.]smshero[.]ai.

The following day, on January 8, the device exhibited its first connectivity to a "smshero"-themed endpoint, which has since been identified as being associated with rotating C2 servers [1] [3]. Similar beaconing activity continued over the following days, with Darktrace identifying C2 connectivity to update[.]7zip[.]com over port 443, alongside additional connections to “smshero”‑themed endpoints such as zest.hero-sms[.]ai, flux.smshero[.]cc, and glide.smshero[.]cc between January 9 and January 15.

Darktrace later observed continued beaconing alerts over a 4-day interval to additional rare destinations attributed to a known ‘config/control domain’, zest[.]hero-sms[.]ai & glide[.]smshero[.]cc.
Figure 4: Darktrace later observed continued beaconing alerts over a 4-day interval to additional rare destinations attributed to a known ‘config/control domain’, zest[.]hero-sms[.]ai & glide[.]smshero[.]cc.

Proxied connectivity over destination ports

The primary objective of this campaign is believed to be proxyware, whereby third-party traffic is routed through victim devices to potentially obfuscate malicious activity. Devices were also observed communicating with rare external IPs hosted on Cloudflare and DataCamp Limited ASNs, establishing outbound proxy connections over the non-standard ports 1000 and 1002 [1].

OSINT sources also indicate that connections over these ports leveraged an XOR-encoded protocol (key 0x70) designed to obscure control messages. While the end goal of the campaign remains unclear, residential proxy networks can be abused to evade security rules and facilitate further unauthorized activities, including phishing and malware distribution [1][3].

Specifically, on January 8, Darktrace observed the device engaging in low-and-slow data exfiltration to the IP 79.127.221[.]47, which had first been observed the previous day, over port 1000. Proxyware typically installs an agent that routes third‑party traffic through an end-user’s device, effectively  turning it into a residential proxy exit node. This activity likely represents the system actively communicating outbound data to an entity that controls its behavior.

Figure 5: Darktrace later observed a ‘Low and Slow Exfiltration to IP’ alert, involving the known tunnel/proxy endpoint ‘79.127.221[.]47’.

Similar activity continued between January 10 and January 18, with Darktrace detecting threat actors attempting to exfiltrate significant volumes of data to 79.127.221[.]47 over destination port 1000.

Throughout the course of this incident, Darktrace’s Cyber AI Analyst launched several autonomous investigations, analyzing each anomalous event and ultimately painting a detailed picture of the attack timeline. These investigations correlated multiple incidents based on Darktrace detections observed between January 7 and January 19. Cyber AI Analyst identified anomalous variables such as repeated connections to unusual endpoints involving data uploads and downloads, with particular emphasis on HTTP and SSL connectivity.

Darktrace AI Analyst Coverage, showcasing multiple incident events that occurred on January 7th & 8th, highlighting associated malicious 7-zip behaviors.
Figure 6: Darktrace AI Analyst Coverage, showcasing multiple incident events that occurred on January 7th & 8th, highlighting associated malicious 7-zip behaviors.
Darktrace AI Analyst Endpoint Details from the given ‘Unusual Repeated Connections’ Incident Event, including the known tunnel/proxy endpoint.
Figure 7: Darktrace AI Analyst Endpoint Details from the given ‘Unusual Repeated Connections’ Incident Event, including the known tunnel/proxy endpoint.
 Darktrace AI Analyst Coverage, showcasing additional incident events that occurred on January 12th through 18th, highlighting malicious 7-zip behaviors and SSL connectivity.
Figure 8: Darktrace AI Analyst Coverage, showcasing additional incident events that occurred on January 12th through 18th, highlighting malicious 7-zip behaviors and SSL connectivity.

Darktrace’s Autonomous Response

At several stages throughout the attack, Darktrace implemented Autonomous Response actions to help contain the suspicious activity as soon as it was identified, providing the customer’s security team with additional time to investigate and remediate. Between January 7 and January 18, Darktrace blocked a wide range of malicious activity, including beaconing connections to unusual endpoints, small data exfiltration attempts, and larger egress efforts, ultimately preventing the attacker from progressing through multiple stages of the attack or achieving their objectives.

Darktrace Autonomous Response Action Coverage showcasing connection block connection events including various endpoints that occurred on January 7th.
Figure 9: Darktrace Autonomous Response Action Coverage showcasing connection block connection events including various endpoints that occurred on January 7th.
Darktrace Antigena (Autonomous Response) Model Alert Coverage, showcasing a Antigena Suspicious Activity Block alert occurred on January 10th as a result of the Low and Slow Exfiltration to IP model alert.
Figure 10: Darktrace Antigena (Autonomous Response) Model Alert Coverage, showcasing a Antigena Suspicious Activity Block alert occurred on January 10th as a result of the Low and Slow Exfiltration to IP model alert.
Figure 11: Additional Darktrace Antigena (Autonomous Response) Model Alert Coverage, showcasing a Antigena Large Data Volume Outbound Block alert occurred on January 18th as a result of the Uncommon 1 GiB Outbound model alert.

Conclusion

The malicious 7‑Zip installer underscores how attackers continue to weaponize trust in widely used, legitimate software to gain initial access while evading user suspicion. By exploiting familiar and commonly installed services, this type of attack demonstrates that even routine actions, such as installing compression software, can become high‑risk events when defenses or user awareness are insufficient.

This campaign further emphasizes the urgent need for strict software validation and continuous network monitoring. Modern threats no longer rely solely on obscure tools or overtly malicious behavior. Instead, they increasingly blend seamlessly into everyday operations, making detection more challenging.

In this case, Darktrace / NETWORK was able to identify the anomalous activity and Autonomous Response actions in a timely manner, enabling the customer to be quickly notified and providing crucial additional time to investigate further.

In summary, the abuse of a trojanized 7‑Zip installer highlights a concerning shift in modern threat tactics, where trusted and widely deployed tools can serve as primary delivery mechanisms for system compromise. This reality reinforces that proactive detection, continuous monitoring, and strong security awareness are not optional but essential.

Credit to Justin Torres, Senior Cyber Analyst, David Moreira da Silva, Cyber Analyst, Emma Foulger, Global Threat Research Operations Lead.

Edited by Ryan Traill (Content Manager)

Appendices

References

1. https://www.malwarebytes.com/blog/threat-intel/2026/02/fake-7-zip-downloads-are-turning-home-pcs-into-proxy-nodes

2. https://www.tomshardware.com/tech-industry/cyber-security/unofficial-7-zip-com-website-served-up-malware-for-10-days-files-turned-pcs-into-a-proxy-botnet

3. https://blog.lukeacha.com/2026/01/beware-of-fake-7zip-installer-upstage.html

4. https://www.bleepingcomputer.com/news/security/malicious-7-zip-site-distributes-installer-laced-with-proxy-tool/

5. https://customerportal.darktrace.com/guides/antigena-network-model-actions

Darktrace Model Detections

·      Anomalous Connection / Data Sent to Rare Domain

·      Anomalous Connection / Low and Slow Exfiltration to IP

·      Anomalous Connection / Multiple Failed Connections to Rare Endpoint

·      Anomalous Connection / Uncommon 1 GiB Outbound

·      Anomalous Server Activity / Rare External from Server

·      Compromise / Agent Beacon (Long Period)

·      Compromise / Beacon for 4 Days

·      Compromise / Beacon to Young Endpoint

·      Compromise / Beaconing Activity To External Rare

·      Compromise / High Volume of Connections with Beacon Score

·      Compromise / Large Number of Suspicious Failed Connections

·      Compromise / Large Number of Suspicious Successful Connections

·      Compromise / Repeating Connections Over 4 Days

·      Compromise / SSL Beaconing to Rare Destination

·      Compromise / Suspicious TLS Beaconing To Rare External

·      Device / Large Number of Model Alerts

·      Unusual Activity / Unusual External Activity

Cyber AI Analyst Coverage

·      Unusual Repeated Connections

·      Unusual Repeated Connections to Multiple Endpoints

·      Possible HTTP Command and Control

·      Possible HTTP Command and Control to Multiple Endpoints

·      Suspicious Remote Service Control Activity

·      Possible SSL Command and Control to Multiple Endpoints

Indicators of Compromise

IoC - Type - Description + Confidence

·      7zip[.]com – Hostname – C2 Endpoint

·      flux[.]smshero[.]co - Hostname - C2 Endpoint

·      neo[.]herosms[.]co - Hostname - C2 Endpoint

·      nova[.]smshero[.]ai - Hostname - C2 Endpoint

·      zest[.]hero-sms[.]ai -  Hostname - C2 Endpoint

·      soc[.]hero-sms[.]co - Hostname - C2 Endpoint

·      pulse[.]herosms[.]cc - Hostname - C2 Endpoint

·      glide[.]smshero[.]cc - Hostname - C2 Endpoint

·      prime[.]herosms[.]vip - Hostname - C2 Endpoint

·      172.96.115[.]226 - IP Address - C2 Endpoint

·      79.127.221[.]47:1002 – IP Address/Port - Proxy Endpoint

·      84.17.37[.]1:1002 - IP Address/Port - Proxy Endpoint

MITRE ATT&CK Mapping

Technique Name - Tactic - ID - Sub-Technique of

·      Exfiltration Over C2 Channel - EXFILTRATION - T1041

·      Scheduled Transfer - EXFILTRATION - T1029

·      Automated Exfiltration - EXFILTRATION - T1020

·      Data Transfer Size Limits - EXFILTRATION - T1030

·      External Proxy - COMMAND AND CONTROL - T1090.002 - T1090

·      Non-Application Layer Protocol - COMMAND AND CONTROL - T1095

·      Non-Standard Port - COMMAND AND CONTROL - T1571

·      Exfiltration to Cloud Storage - EXFILTRATION - T1567.002 - T1567

·      Exploit Public-Facing Application - INITIAL ACCESS - T1190

·      Web Protocols - COMMAND AND CONTROL - T1071.001 - T1071

·      Application Layer Protocol - COMMAND AND CONTROL - T1071

·      Man in the Browser - COLLECTION - T1185

·      Browser Extensions - PERSISTENCE - T1176

·      Encrypted Channel - COMMAND AND CONTROL - T1573

·      Fallback Channels - COMMAND AND CONTROL - T1008

·      Multi-Stage Channels - COMMAND AND CONTROL - T1104

·      Supply Chain Compromise - INITIAL ACCESS ICS - T0862

·      Commonly Used Port - COMMAND AND CONTROL ICS - T0885

Continue reading
About the author
Justin Torres
Cyber Analyst
Your data. Our AI.
Elevate your network security with Darktrace AI