ブログ
/
Email
/
August 7, 2023

Detection of an Evasive Credential Harvester | IPFS Phishing

Discover the emerging trend of malicious actors abusing the Interplanetary File System (IPFS) file storage protocol in phishing campaigns. Learn more here!
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
Lena Yu
Cyber Security Analyst
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
07
Aug 2023

IPFS Phishing Attacks

Phishing attacks continue to be one of the most common methods of infiltration utilized by threat actors and they represent a significant threat to an organization’s digital estate. As phishing campaigns typically leverage social engineering methods to evade security tools and manipulate users into following links, downloading files, or divulging confidential information. It is a relatively low effort but high-yield type of cyber-attack.

That said, in recent years security teams have become increasingly savvy to these efforts. Attackers are having to adapt and come up with novel ways to carry out their phishing campaigns. Recently, Darktrace has observed a rise in phishing attacks attempting to abuse the InterPlanetary File System (IPFS) in campaigns that are able to dynamically adapt depending on the target, making it extremely difficult for security vendors to detect and investigate.

What is a IPFS?

IPFS is a file storage protocol a peer-to-peer (P2P) network used for storing and sharing resources in a distributed file system [1]. It is also a file storage system similar in nature to other centralized file storage services like Dropbox and Google Drive.

File storage systems, like IPFS, are often abused by malicious actors, as they allow attackers to easily host their own content without maintaining infrastructure themselves. However, as these file storage systems often have legitimate usages, blocking everything related to file storages may cause unwanted problems and affect normal business operations. Thus, the challenge lies in differentiating between legitimate and malicious usage.

While centralized, web-based file storage services use a Client-Server model and typically deliver files over HTTP, IPFS uses a Peer-to-Peer model for storing and sharing files, as shown in Figure 1.

Figure 1: (a) shows the Client-Server model that centralized, web-based file storage services use. The resource is available on the server, and the clients access the resource from the server. (b) shows the Peer-to-Peer model that IPFS use. The resources are available on the peers.

To verify the authenticity and integrity of files, IPFS utilizes cryptographic hashes.

A cryptographic hash value is generated using a file’s content upon upload to IPFS. This is used to generate the Content Identifier (CID). IPFS uses Content Addressing as opposed to Location Addressing, and this CID is used to point to a resource in IPFS [4].

When a computer running IPFS requires a particular file, it asks the connected peers if they have the file with a specific hash. If a peer has the file with the matching hash, it will provide it to the requesting computer [1][6].

Taking down content on IPFS is much more difficult compared to centralized file storage hosts, as content is stored on several nodes without a centralized entity, as shown in Figure 2. To take down content from IPFS, it must be removed from all the nodes. Thus, IPFS is prone to being abused for malicious purposes.

Figure 2: When the resource is unavailable on the server for (a), all the clients are unable to access the resource. When the resource is unavailable on one of the peers for (b), the resources are still available on the other peers.

The domains used in these IPFS phishing links are gateways that enable an HTTPS URL to access resources within the distributed IPFS file system.

There are two types of IPFS links, the Path Gateway and Subdomain Gateway [1].

Path Gateways have a fixed domain/host and identifies the IPFS resource through a resource-identifying string in the path. The Path Gateway has the following structure:

•       https://<gateway-host>.tld/ipfs/<CID>/path/to/resource

•       https://<gateway-host>.tld/ipns/<dnslink/ipnsid>/path/to/resource

On the other hand, Subdomain Gateways have a resource-identifying string in the subdomain. Subdomain Gateways have the following structure:

•       https://<cidv1b32>.ipfs.<gateway-host>.tld/path/to/resource

One gateway domain serves the same role as any other, which means attackers can easily change the gateways that are used.

Thus, these link domains involved in these attacks can be much more variable than the ones in traditional file storage attacks, where a centralized service with a single domain is used (e.g., Dropbox, Google Docs), making detecting the malicious use of IPFS extremely challenging for traditional security vendors. Through its anomaly-based approach to threat detection, Darktrace/Email™ is consistently able to identify such tactics and respond to them, preventing malicious actors from abusing file storage systems life IPFS.

IPFS Campaign Details

In several recent examples of IPFS abuse that Darktrace detected on a customer’s network, the apparent end goal was to harvest user credentials. Stolen credentials can be exploited by threat actors to further their attacks on organizations by escalating their privileges within the network, or even sold on the dark web.

Darktrace detected multiple IPFS links sent in malicious emails that contained the victim’s email address. Based on the domain in this email address, users would then be redirected to a fake login page that uses their organizations’ webpage visuals and branding to convince targets to enter their login details, unknowingly compromising their accounts in the process.

Figure 3: The credential harvester changes visuals depending on the victim’s email address specified in the URL.

These IPFS credential harvesting sites use various techniques to evade detection the detection of traditional security tools and prevent further analysis, such as obfuscation by Percent Encoding and Base64 Encoding the code.

There are also other mechanisms put into place to hinder investigation by security teams. For example, some IPFS credential harvester sites investigated by Darktrace did not allow right clicking and certain keystrokes, as a means to make post-attack analysis more difficult.

Figure 4: The code shows that it attempts to prevent certain keystrokes.

In the campaign highlighted in this blog, the following IPFS link was observed:

hxxps://ipfs[.]io/ipfs/QmfDDxLWoLiqFURX6dUZcsHxVBP1ZnM21H5jXGs1ffNxtP?filename=at ob.html#<EmailAddress>

This uses a Path Gateway, as it identifies the IPFS resource through a resource-identifying string in the path. The CID is QmfDDxLWoLiqFURX6dUZcsHxVBP1ZnM21H5jXGs1ffNxtP in this case.

It makes a GET request to image[.]thum[.]io and logo[.]clearbit[.]com as shown in Figure 5. The image[.]thum[.]io is a Free Website Screenshot Generator, that provides real-time screenshot of websites [2]. The logo[.]clearbit[.]com is used to lookup company logos using the domain [3]. These visuals are integrated into the credential harvester site. Figure 6 shows the domain name being extracted from the victim’s email address and used to obtain the visuals.

Figure 5: The GET requests to image[.]thum[.]io and logo[.]clearbit[.].
Figure 6: The code shows that it utilizes the domain name from the victim’s email address to obtain the visuals from logo.clearbit[.]com and image[.]thum.io.

The code reveals the credential POST endpoint as shown in Figure 16. When credentials are submitted, it makes a POST request to this endpoint as shown in Figure 7.

Figure 7: The credential POST endpoint can be seen inside the code.
Figure 8: The Outlook credential harvester will redirect to the real Outlook page when wrong credentials are submitted multiple times.

From the IPFS link alone, it is difficult to determine whether it leads to a malicious endpoint, however Darktrace has consistently identified emails containing these IPFS credential harvesting links as phishing attempts.

Darktrace Coverage

During one case of IPFS abuse detected by Darktrace in March 2023, a threat actor sent malicious emails with the subject “Renew Your E-mail Password” to 55 different recipients at. The sender appeared to be the organization’s administrator and used their internal domain.

Figure 9: Darktrace/Email’s detection of the “Renew Your E-mail Password” emails from “administrator”. These were all sent at 2023.03.21 02:39 UTC.

However, Darktrace recognized that the email did not pass Sender Policy Framework (SPF), and therefore it could not be validated as being sent from the organization’s domain. Darktrace also detected that the email contained a link to “ipfs.io, the official IPFS gateway. This was identified as a spoofing and phishing attempt by Darktrace/Email.

Figure 10: The Darktrace/Email overview tab shows the Anomaly Indicators, History, Association, and Validation information of this sender. It contained a link to “ipfs.io”, and did not pass SPF.

Following the successful identification of the malicious emails, Darktrace RESPOND™ took immediate autonomous action to prevent them from leading to potentially damaging network compromise. For email-based threats, Darktrace RESPOND is able to carry out numerous actions to stop malicious emails and reduce the risk of compromise. In response to this specific incident, RESPOND took multiple preventative actions (as seen in Figure 11), including include lock link, an action that prevents access to URLs deemed as suspicious, send to junk, an action that automatically places emails in the recipient’s junk folder, and hold message, the most severe RESPOND action that prevents malicious emails from reaching the recipients inbox at all.

Figure 11: The Darktrace/Email model tab shows all the models that triggered on the email and the associated RESPOND actions.
Figure 12: The ipfs.io link used in this email contains the recipient’s email address, and has a CID of QmfDDxLWoLiqFURX6dUZcsHxVBP1ZnM21H5jXGs1ffNxtP. It has a Darktrace Domain Rarity Score of 100
Figure 13: The IPFS credential harvester that uses the organization’s website’s visuals.

Further investigation revealed that the IPFS link contained the recipients’ email address, and when clicked led to a credential harvester that utilized the same visuals and branding as the customer’s website.

Concluding Thoughts

Ultimately, despite the various tactics employed threat actors to evade the detection of traditional security tools, Darktrace was able to successfully detect and mitigate these often very fruitful phishing attacks that attempted to abuse the IPFS file storage system.

As file storage platforms like IPFS do have legitimate business uses, blocking traffic related to file storage is likely to negatively impact the day-to-day operations of an organization. The challenge security teams face is to differentiate between malicious and legitimate uses of such services, and only act on malicious cases. As such, it is more important than ever for organizations to have an effective anomaly detection tool in place that is able to identify emerging threats without relying on rules, signatures or previously observed indicators of compromise (IoC).

By leveraging its Self-Learning AI, Darktrace understands what represents expected activity on customer networks and can recognize subtle deviations from expected behavior, that may be indicative of compromise. Then, using its autonomous response capabilities, Darktrace RESPOND is able to instantly and autonomously take action against emerging threats to stop them at the earliest possible stage.

Credit to Ben Atkins, Senior Model Developer for their contribution to this blog.

Appendices

Example IOCs

Type: URL

IOC: hxxps://ipfs[.]io/ipfs/QmfDDxLWoLi qFURX6dUZcsHxVBP1ZnM21H5jXGs

1ffNxtP?filename=atob.html#<Email Address>

Description: Path Gateway link

Type: URL

IOC: hxxps://bafybeibisyerwlu46re6rxrfw doo2ubvucw7yu6zjcfjmn7rqbwcix2 mku.ipfs[.]dweb.link/webn cpmk.htm?bafybeigh77sqswniy74nzyklybstfpkxhsqhpf3qt26nwnh4wf2vv gbdaybafybeigh77sqswniy74nzyklybstfpkxhsqhpf3qt26nwnh4wf2vvgbda y#<EmailAddress>

Description: Subdomain Gateway link

Relevant Darktrace DETECT Models

•       Spoof / Internal Domain from Unexpected Source + New Unknown Link

•       Link / High Risk Link + Low Sender Association

•       Link / New Correspondent Classified Link

•       Link / Watched Link Type

•       Proximity / Phishing + New activity

•       Proximity / Phishing + New Address Known Domain

•       Spoof / Internal Domain from Unexpected Source + High Risk Link

References

[1]    https://docs.ipfs.tech/

[2]    https://www.thum.io/

[3]    https://clearbit.com/logo

[4]    https://filebase.com/blog/ipfs-content-addressing-explained/

[5]    https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/the-attack-of-the-chameleon-phishing-page/

[6]    https://wiki.ipfsblox.com/

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
Lena Yu
Cyber Security Analyst

More in this series

No items found.

Blog

/

AI

/

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

Default 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
あなたのデータ × DarktraceのAI
唯一無二のDarktrace AIで、ネットワークセキュリティを次の次元へ