Blog
/
/
January 30, 2025

Reimagining Your SOC: Overcoming Alert Fatigue with AI-Led Investigations  

Reimagining your SOC Part 2/3: This blog explores how the challenges facing the modern SOC can be addressed by transforming the investigation process, unlocking efficiency and scalability in SOC operations with AI.
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
Brittany Woodsmall
Product Marketing Manager, AI
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
30
Jan 2025

The efficiency of a Security Operations Center (SOC) hinges on its ability to detect, analyze and respond to threats effectively. With advancements in AI and automation, key early SOC team metrics such as Mean Time to Detect (MTTD) have seen significant improvements:

  • 96% of defenders believing AI-powered solutions significantly boost the speed and efficiency of prevention, detection, response, and recovery.
  • Organizations leveraging AI and automation can shorten their breach lifecycle by an average of 108 days compared to those without these technologies.

While tool advances have improved performance and effectiveness in the detection phase, this has not been as beneficial to the next step of the process where initial alerts are investigated further to determine their relevance and how they relate to other activities. This is often measured with the metric Mean Time to Analysis (MTTA), although some SOC teams operate a two-level process with teams for initial triage to filter out more obviously uninteresting alerts and for more detailed analysis of the remainder. SOC teams continue to grapple with alert fatigue, overwhelmed analysts, and inefficient triage processes, preventing them from achieving the operational efficiency necessary for a high-performing SOC.

Addressing this core inefficiency requires extending AI's capabilities beyond detection to streamline and optimize the following investigative workflows that underpin effective analysis.

Challenges with SOC alert investigation

Detecting cyber threats is only the beginning of a much broader challenge of SOC efficiency. The real bottleneck often lies in the investigation process.

Detection tools and techniques have evolved significantly with the use of machine learning methods, improving early threat detection. However, after a detection pops up, human analysts still typically step in to evaluate the alert, gather context, and determine whether it’s a true threat or a false alarm and why. If it is a threat, further investigation must be performed to understand the full scope of what may be a much larger problem. This phase, measured by the mean time to analysis, is critical for swift incident response.

Challenges with manual alert investigation:

  • Too many alerts
  • Alerts lack context
  • Cognitive load sits with analysts
  • Insufficient talent in the industry
  • Fierce competition for experienced analysts

For many organizations, investigation is where the struggle of efficiency intensifies. Analysts face overwhelming volumes of alerts, a lack of consolidated context, and the mental strain of juggling multiple systems. With a worldwide shortage of 4 million experienced level two and three SOC analysts, the cognitive burden placed on teams is immense, often leading to alert fatigue and missed threats.

Even with advanced systems in place not all potential detections are investigated. In many cases, only a quarter of initial alerts are triaged (or analyzed). However, the issue runs deeper. Triaging occurs after detection engineering and alert tuning, which often disable many alerts that could potentially reveal true threats but are not accurate enough to justify the time and effort of the security team. This means some potential threats slip through unnoticed.

Understanding alerts in the SOC: Stopping cyber incidents is hard

Let’s take a look at the cyber-attack lifecycle and the steps involved in detecting and stopping an attack:

First we need a trace of an attack…

The attack will produce some sort of digital trace. Novel attacks, insider threats, and attacker techniques such as living-off-the-land can make attacker activities extremely hard to distinguish.

A detection is created…

Then we have to detect the trace, for example some beaconing to a rare domain. Initial detection alerts being raised underpin the MTTD (mean time to detection). Reducing this initial unseen duration is where we have seen significant improvement with modern threat detection tools.

When it comes to threat detection, the possibilities are vast. Your initial lead could come from anything: an alert about unusual network activity, a potential known malware detection, or an odd email. Once that lead comes in, it’s up to your security team to investigate further and determine if this is this a legitimate threat or a false alarm and what the context is behind the alert.

Investigation begins…

It doesn’t just stop at a detection. Typically, humans also need to look at the alert, investigate, understand, analyze, and conclude whether this is a genuine threat that needs a response. We normally measure this as MTTA (mean time to analyze).

Conducting the investigation effectively requires a high degree of skill and efficiency, as every second counts in mitigating potential damage. Security teams must analyze the available data, correlate it across multiple sources, and piece together the timeline of events to understand the full scope of the incident. This process involves navigating through vast amounts of information, identifying patterns, and discerning relevant details. All while managing the pressure of minimizing downtime and preventing further escalation.

Containment begins…

Once we confirm something as a threat, and the human team determines a response is required and understand the scope, we need to contain the incident. That's normally the MTTC (mean time to containment) and can be further split into immediate and more permanent measures.

For more about how AI-led solutions can help in the containment stage read here: Autonomous Response: Streamlining Cybersecurity and Business Operations

The challenge is not only in 1) detecting threats quickly, but also 2) triaging and investigating them rapidly and with precision, and 3) prioritizing the most critical findings to avoid missed opportunities. Effective investigation demands a combination of advanced tools, robust workflows, and the expertise to interpret and act on the insights they generate. Without these, organizations risk delaying critical containment and response efforts, leaving them vulnerable to greater impacts.

While there are further steps (remediation, and of course complete recovery) here we will focus on investigation.

Developing an AI analyst: How Darktrace replicates human investigation

Darktrace has been working on understanding the investigative process of a skilled analyst since 2017. By conducting internal research between Darktrace expert SOC analysts and machine learning engineers, we developed a formalized understanding of investigative processes. This understanding formed the basis of a multi-layered AI system that systematically investigates data, taking advantage of the speed and breadth afforded by machine systems.

With this research we found that the investigative process often revolves around iterating three key steps: hypothesis creation, data collection, and results evaluation.

All these details are crucial for an analyst to determine the nature of a potential threat. Similarly, they are integral components of our Cyber AI Analyst which is an integral component across our product suite. In doing so, Darktrace has been able to replicate the human-driven approach to investigating alerts using machine learning speed and scale.

Here’s how it works:

  • When an initial or third-party alert is triggered, the Cyber AI Analyst initiates a forensic investigation by building multiple hypotheses and gathering relevant data to confirm or refute the nature of suspicious activity, iterating as necessary, and continuously refining the original hypothesis as new data emerges throughout the investigation.
  • Using a combination of machine learning including supervised and unsupervised methods, NLP and graph theory to assess activity, this investigation engine conducts a deep analysis with incidents raised to the human team only when the behavior is deemed sufficiently concerning.
  • After classification, the incident information is organized and processed to generate the analysis summary, including the most important descriptive details, and priority classification, ensuring that critical alerts are prioritized for further action by the human-analyst team.
  • If the alert is deemed unimportant, the complete analysis process is made available to the human team so that they can see what investigation was performed and why this conclusion was drawn.
Darktrace cyber ai analyst workflow, how it works

To illustrate this via example, if a laptop is beaconing to a rare domain, the Cyber AI Analyst would create hypotheses including whether this could be command and control traffic, data exfiltration, or something else. The AI analyst then collects data, analyzes it, makes decisions, iterates, and ultimately raises a new high-level incident alert describing and detailing its findings for human analysts to review and follow up.

Learn more about Darktrace's Cyber AI Analyst

  • Cost savings: Equivalent to adding up to 30 full-time Level 2 analysts without increasing headcount
  • Minimize business risk: Takes on the busy work from human analysts and elevates a team’s overall decision making
  • Improve security outcomes: Identifies subtle, sophisticated threats through holistic investigations

Unlocking an efficient SOC

To create a mature and proactive SOC, addressing the inefficiencies in the alert investigation process is essential. By extending AI's capabilities beyond detection, SOC teams can streamline and optimize investigative workflows, reducing alert fatigue and enhancing analyst efficiency.

This holistic approach not only improves Mean Time to Analysis (MTTA) but also ensures that SOCs are well-equipped to handle the evolving threat landscape. Embracing AI augmentation and automation in every phase of threat management will pave the way for a more resilient and proactive security posture, ultimately leading to a high-performing SOC that can effectively safeguard organizational assets.

Every relevant alert is investigated

The Cyber AI Analyst is not a generative AI system, or an XDR or SEIM aggregator that simply prompts you on what to do next. It uses a multi-layered combination of many different specialized AI methods to investigate every relevant alert from across your enterprise, native, 3rd party, and manual triggers, operating at machine speed and scale. This also positively affects detection engineering and alert tuning, because it does not suffer from fatigue when presented with low accuracy but potentially valuable alerts.

Retain and improve analyst skills

Transferring most analysis processes to AI systems can risk team skills if they don't maintain or build them and if the AI doesn't explain its process. This can reduce the ability to challenge or build on AI results and cause issues if the AI is unavailable. The Cyber AI Analyst, by revealing its investigation process, data gathering, and decisions, promotes and improves these skills. Its deep understanding of cyber incidents can be used for skill training and incident response practice by simulating incidents for security teams to handle.

Create time for cyber risk reduction

Human cybersecurity professionals excel in areas that require critical thinking, strategic planning, and nuanced decision-making. With alert fatigue minimized and investigations streamlined, your analysts can avoid the tedious data collection and analysis stages and instead focus on critical decision-making tasks such as implementing recovery actions and performing threat hunting.

Stay tuned for part 3/3

Part 3/3 in the Reimagine your SOC series explores the preventative security solutions market and effective risk management strategies.

Coming soon!

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
Brittany Woodsmall
Product Marketing Manager, AI

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