Breaking Down "ICES": An Umbrella Term With Wide Variety
Integrated Cloud Email Security (ICES) can be an effective email security solution, but Darktrace/Email's self-learning AI should be your solution of choice.
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
Dan Fein
VP, Product
Share
09
May 2023
While organizing email security solutions into categories can help security teams understand the types of products available, it can also lead to generalizations that overlook important differences within those categories and can become like comparing apples to oranges.
This is true for the Integrated Cloud Email Security (ICES) category. Among the products that qualify, there are important variations in approach that can mean the difference between stopping a novel phishing attack on the first encounter and catching it as many as 13 days later.
These distinctions highlight that not all ICES products and not all AI tools are made equal, and it’s critical to look deeper than the “ICES” label when examining an email security solution.
Gartner devised the term ICES in 2021 to describe an advanced email security that augments the native capabilities of email providers by using API access to analyze email content without requiring changing the MX record.
In other words, ICES solutions integrate with an organization’s cloud email provider to filter out malicious emails.
ICES has risen in popularity as more and more organizations shift to cloud-based or hybrid email servers, and encounter new, more sophisticated threats. Organizations pair ICES with improved native capabilities of email providers. For example, in the 2023 Market Guide for Email Security, Gartner acknowledged that “Microsoft, in particular, continues to make significant investments in improving protection effectiveness and providing better configuration guidance.”
Native capabilities can detect traditional indicators of compromise, while ICES products can detect nuanced attacks. They integrate directly with cloud-based email providers, meaning emails do not have to be rerouted for analysis, therefore reducing the time security teams would have to spend configuring and maintaining that connection or risking operational outage.
ICES protects against sophisticated attacks
Before the rise of ICES, the mainstream email security solutions were Secure Email Gateways (SEGs), which can be characterized as tools that rely on historic data to create rules and signatures. This purely reactive approach cannot contend with the current email threat landscape, which includes attacks that abuse legitimate services, originate from compromised known senders, or are entirely novel. They also struggle to detect multi-stage attacks and insider threats.
Instead, ICES products use natural language processing and natural language understanding to identify social engineering like business email compromises, spoofing, supply chain attacks, account takeovers, and more. However, although ICES products can detect more sophisticated threats than SEGs, not all of them can stop entirely unknown attacks.
Achieving bespoke security with AI that understands you
Even though several ICES products rely on machine learning to identify and stop malicious emails, not all AI is the same. Typically, other vendors’ AIs are trained on insights pulled from across their respective customer-bases and past attacks. However, this does not account for nuanced distinctions that arise from organizations’ sizes, industries, or even the individual employees working at each company.
Instead, Darktrace understands you. Self-Learning AI™ focuses on the organization it is installed in, instead of generalizing across a wider pool. Darktrace even learns on a granular level, building profiles of every individual employee by analyzing behaviors like how they typically communicate, where and when they log in, the tone and sentiment of their emails, file and link sharing patterns, and hundreds of other signals. This level of specificity ensures that the email security is tailored to each specific organization.
The ability to learn employee behavior allows Darktrace to detect what is not normal, therefore revealing sophisticated threats on the first encounter. It can detect all types of attacks, including BEC, account takeover, insider threat, compromised internal accounts, and even human error.
But it’s the ability to stop novel attacks upon the first encounter that sets it apart. Darktrace/Email™ can detect novel email attacks an average of 13 days earlier than email security tools that are trained on knowledge of historical threats.
Moreover, Darktrace can take precise action to respond to threats, beyond simply allowing or blocking a suspicious email. The AI makes micro-decisions to neutralize only the malicious components of emails. For example, it might flatten an attached PDF, rewrite a shared link, or file an email as junk.
Darktrace/Email goes further than other ICES by considering the employee experience. With an employee-AI feedback loop, the AI can fine-tune security based on the employees while also providing inline security awareness training in real-time and with real-life examples. By engaging down to the employee level, Darktrace AI can even leverage personalized insights for productivity gains, sorting out graymail based on how each user prefers to interact with it.
Putting the “I” in “ICES”
Many ICES vendors emphasize the “integrated” part of the acronym, however Darktrace excels at this. Since Darktrace can be installed anywhere a company has data, it can natively interact across the digital estate, saving the security team time and resources otherwise spent learning various dashboards and languages, correlating data across different areas, and manually monitoring daily activity. Darktrace/Email can also integrate with external tools, including SIEMs and SOARs, to further enhance workflows.
Moreover, since combining ICES solutions with native security email capabilities creates a hardened security posture, Darktrace/Email benefits from its strong, established integration with Microsoft.
Introducing flexibility to ICES deployments
Finally, the security and integration capabilities of Darktrace/Email deploy easily. In the 2023 Market Guide for Email Security, Gartner predicted that “by 2025, 20% of anti-phishing solutions will be delivered via API integration with the email platform, up from less than 5% today.” Darktrace/Email can be rolled out via API or API + Journaling in Microsoft 365, whichever better fits the organization’s needs.
While all ICES products are API-based, that does not mean they are AI-first, or are using the best AI approach. Even some SEGs can deploy via API. That means that the ability to deploy via API does not guarantee a level of security that can stop the most sophisticated threats. Security teams should look beyond deployment method and select the ICES and AI solutions that provide tailored, effective security.
Finding nuance as an ICES solution
Email security continues to advance in tandem with the threat landscape and organizations’ digital infrastructures. ICES solutions are supplanting SEGs as the mainstream email security solutions, however that broad category includes a range of tools with varying applications of AI. These differences make it critical to not put all ICES products in the same basket.
Darktrace/Email is the only ICES solution that uses Self-Learning AI to detect all types of email threats, including novel attacks, within seconds.
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.
Journey of a Threat: How Multi-Layered AI Works in Darktrace / EMAIL
Follow a malicious email as it moves through Darktrace / EMAIL’s multi-layered AI system, from raw data to final decision. Each layer works together to detect threats, understand intent, and take autonomous action.
How email-delivered prompt injection attacks can target enterprise AI – and why it matters
Prompt injection is a newly emerging threat, with only a handful of confirmed victims so far – targeting how AI systems use data rather than exploiting traditional software vulnerabilities. As agentic AI becomes embedded across enterprise environments, attackers may attempt to manipulate these systems through hidden instructions in everyday email content.
Darktrace Unites Human Behavior and Threat Detection Across Email, Slack, Teams, and Zoom
Introducing the adaptive era of email security: a unified platform that connects personalized coaching, collaboration tools, and user behavior into a self-improving defense system.
Hola VPN Abuse: From Proxy Traffic to Malware and Cryptomining
Introduction
In enterprise environments, non-compliant software traffic can introduce unexpected exposure by creating unmanaged paths for outbound connectivity. Hola VPN is a notable example because of its peer-to-peer design, which can effectively turn user devices into routing or exit nodes for other parties’ traffic, shifting the risk profile from that of a traditional virtual private network (VPN) to something closer to a distributed proxy.
As a result, the appearance of Hola-related activity, whether from prior installation or unintended background connections, should be treated with caution. Such activity may provide a foothold for malicious behavior, including lateral movement or command-and-control communication.
This blog explores how Hola-associated activity appeared as part of broader patterns of suspicious behavior observed across the Darktrace customer base.
The campaign
In February and March 2026, Darktrace observed similar anomalous activity across multiple customer environments, with affected devices showing consistent behavioral patterns. These included connections to multiple *.hola[.]org endpoints using Hola-related user agents, suggesting interaction with Hola infrastructure rather than isolated or incidental traffic.
Following these connections, affected customer environments showed downloads of suspicious executable files from rare external endpoints 188.241.219[.]55 and 184.241.218[.]111. Both endpoints have been flagged as potentially malicious by open-source intelligence (OSINT) [1][2].
These downloads were conducted using consistent user agents across impacted customers, specifically ‘Hola svc_js_win32/1.249.408’ and ‘Hola svc_js_win32/1.251.389’, suggesting a possible association with Hola-related activity.
Notably, this pattern aligns with recent reporting that, in some cases, Hola distributed an undeclared executable component, me[.]exe, which was later assessed to be a likely Monero-mining binary introduced via a compromised delivery pipeline [3].
Case Study 1
Darktrace first observed a new device on January 19, 2026, within a customer environment based in the Europe, Middle East, and Africa (EMEA) region. On the same day it appeared on the network, the device communicated with multiple pieces of Hola VPN-linked infrastructure before downloading a binary from a hola[.]org subdomain.
Figure 1: Cyber AI Analyst investigation highlighting Hola VPN service activity potentially associated with subsequent HTTP command-and-control (C2) connections.
Subsequent Darktrace telemetry revealed a recurring pattern of activity from the day the device was first observed through to March 4, 2026. During this period, the device repeatedly issued HTTP GET requests to the URI /bwfile?size=1048576, each returning a 200 OK response, indicating successful file retrieval.
This behavior was accompanied by a POST request to /bwfile, followed by an additional GET request for a significantly larger file at /bwfile?size=26214400, suggesting a deliberate and structured file transfer pattern.
Notably, the binary download activity was not tied to a single static host. Instead, it was observed across multiple URLs that changed over time while remaining within the same hola[.]org domain. This pattern suggests the use of rotating or distributed delivery infrastructure rather than a fixed endpoint.
Figure 2: Variation in URLs over time within the same hola[.]org domain, indicating the use of dynamically changing endpoints.
Across these events, the activity was consistently associated with the user agent Hola svc_js_win32/1.249.408, further linking the traffic to Hola-related service components. Amid these persistent and unusual connections, on February 22, Darktrace observed the device connecting to 188.241.219[.]55/proxy-peer-windows-amd64[.]exe, resulting in the download of an executable file.
Figure 3: File transfer event showing the download of an executable from the rare external endpoint 188.241.219[.]55.
Based on its file hash, the downloaded file was assessed as a likely Trojan downloader [4], with import hash (imphash) values showing similarities to samples linked to Vidar, Rhadamanthys, and Stealc according to OSINT [5]. Overall, this sequence of activity suggests that Hola-related connectivity may have been leveraged as part of a broader malware delivery chain.
Darktrace’s Autonomous Response
Due to the highly unusual activity observed, Darktrace Autonomous Response was triggered by the device’s behavior. However, as the customer deployment was configured in “Human Confirmation” mode, manual approval was required before any action could be taken.
Had the deployment been set to “Fully Autonomous” mode, Darktrace would have automatically:
Blocked connections to the associated ports and external endpoints
Prevented all outgoing network connections from the device
Enforced the device’s established ‘pattern of life’, allowing normal activity to continue while restricting any anomalous behavior
Figure 4: Example of a Darktrace Autonomous Response model highlighting the action that would have been taken, demonstrating how the system identifies anomalous behavior and applies targeted containment measures to restrict suspicious network activity.
Case Study 2
While the first case focused on anomalous activity from a newly observed device, Darktrace also identified cases in which devices had already been communicating with Hola-related endpoints prior to the suspected campaign. This may suggest pre-existing Hola usage within the environment, potentially increasing exposure and creating an avenue for subsequent suspicious activity.
One case involved three devices within a customer network based in the Americas (AMS). In this instance, a different payload was identified: me[.]exe, a potentially malicious cryptocurrency miner also referred to as HolaMonitorService[.]exe [6][7]. The downloads were observed from infrastructure similar to that seen in Case 1, including an IP address within the same 188.241.0.0/16 subnet.
Connections to *.hola[.]org, alongside the use of potential Hola-related user agents consistent with those in Case 1, were also identified, further suggesting a link between the observed activity and Hola-associated infrastructure.
Darktrace observed activity indicative of unusual VPN usage on the first affected device on February 2, followed by telemetry suggesting potential Tor usage. This was later followed by the download of me[.]exe on March 10 from 188.241.218[.]111. Notably, this device was the earliest among the three within the deployment to exhibit the presence of the suspicious executable.
Figure 5: Cyber AI Analyst detection highlighting the download of a suspicious executable from a similar external endpoint in a separate deployment.
On March 5, 2026, the second affected device exhibited a slightly different progression, initiating connections to http-test1[.]hola[.]org using the user agent ‘hola_get’. This activity was followed by the download of me[.]exe from the same endpoint on March 13, consistent with the broader pattern of Hola-related downloads observed across the environment.
Figure 6: Example of Hola VPN-related connectivity observed on the network prior to the suspected campaign, indicating pre-existing usage that may have contributed to subsequent activity.
The final affected device within this customer’s network demonstrated a more limited but related pattern, also downloading me[.]exe on March 17 using the same ‘hola_get’ user agent.
While the earlier Hola VPN usage observed across the deployment may not have been directly related to the suspected malware campaign, it may nonetheless have contributed to reduced visibility. The presence of pre-existing Hola-related traffic could have obscured malicious activity, making it more difficult to distinguish legitimate usage from attacker-driven behavior and, in turn, hindering the timely identification of the emerging compromise.
Darktrace’s Autonomous Response
For this deployment, the customer had their Autonomous Response capability configured in “Fully Autonomous” mode, allowing Darktrace to take action without human intervention. As a result, the system was able to autonomously disrupt the activity as soon as relevant events were identified through model detections.
Figure 7: Darktrace Autonomous Response actions taken against suspicious activity linked to Hola VPN.
Suspected cryptomining activity
As previously noted, some of the observed executable payloads appear to be linked to cryptomining malware. Across a subset of affected customer environments, this assessment was further supported by subsequent device activity consistent with Monero mining. Affected devices established follow-on connections to multiple external endpoints aligned with known mining infrastructure, indicating post-download execution.
Considering the broader sequence of activity, this pattern may point to a wider form of abuse in which legitimate VPN-related traffic is used to mask or facilitate malicious behavior following compromise.
On several devices, the download of executable files, including a newly observed peer[.]exe, was followed by alerts indicative of cryptocurrency mining activity. Mining-related credentials such as ‘x’ were observed using the Minergate protocol to communicate with endpoints within the 89.125.255.0/24 subnet and 188.241.218[.]111, the same endpoint involved in earlier download activity. Additional credentials appeared to reflect device-specific CPU identifiers, for example ‘12th Gen Intel(R) Core (TM) i5-1235U’.
Observed mining methods included login, submit, and job, consistent with active participation in a pool-based mining workflow rather than passive or incidental contact. The login method indicates that the host authenticated to the mining service as a worker, job reflects the assignment of computational tasks, and submit shows completed work being returned to the pool [8]. This sequence suggests that affected devices were actively contributing processing resources as part of an unauthorized distributed mining operation.
The presence of unauthorized cryptominers can lead to degraded system performance and reduced device stability. Beyond the immediate resource impact, such activity often serves as an indicator of a broader compromise rather than an isolated issue. This may increase the risk of further malware deployment, persistence mechanisms, and lateral movement, particularly in environments where the initial intrusion has not been fully contained.
Conclusion
Across affected environments, detections such as unusual VPN usage, connections to Hola infrastructure, anomalous HTTP activity, suspicious file downloads, and subsequent cryptomining behavior were linked into a single, evolving incident narrative. This aggregation provided a clearer view of attack progression, enabling security teams to understand not just isolated alerts, but the full sequence of compromise from initial contact through to post-exploitation.
Ultimately, these activities show that the risk posed by non-compliant software such as Hola VPN can extend far beyond simple policy violations. What began as traffic to Hola-related infrastructure was, in multiple cases, followed by behavior suggesting deliberate misuse, including suspicious executable downloads using Hola-related user agents and, in some instances, evidence of active cryptomining. These were not isolated anomalies, but elements of a broader pattern in which seemingly benign proxy or VPN-related communications may have created a pathway for malicious delivery and unauthorized resource exploitation.
The significance of this activity lies not only in the downloads or mining, but in what it reveals about an attacker’s ability to blend malicious operations into traffic associated with software that may already have a foothold in the environment. When unapproved software operates within an enterprise, it can reduce visibility, blur the distinction between legitimate and malicious traffic, and create opportunities to extend compromise in ways that are persistent and difficult to detect. Darktrace’s anomaly-based approach enables these behavioral distinctions to be identified, regardless of whether the device is new or long established within the network.
Credit to Min Kim (Associate Principal Analyst), Priya Thapa (Senior Cyber Analyst) Edited by Ryan Traill (Content Manager)
.jpg)
![Variation in URLs over time within the same hola[.]org domain, indicating the use of dynamically changing endpoints.](https://cdn.prod.website-files.com/626ff4d25aca2edf4325ff97/6a304bdeff111215c0436931_Screenshot%202026-06-15%20at%2012.00.43%E2%80%AFPM.png)
![File transfer event showing the download of an executable from the rare external endpoint 188.241.219[.]55.](https://cdn.prod.website-files.com/626ff4d25aca2edf4325ff97/6a304c2468d20aeff16a2721_Screenshot%202026-06-15%20at%2012.01.53%E2%80%AFPM.png)
